20,741
edits
Graphics card profiles: Difference between revisions
Jump to navigation
Jump to search
→Implementation
| Line 112: | Line 112: | ||
{{FGCquote | {{FGCquote | ||
|1= like you said already, this could work pretty much like the joystick support - i.e. we would maintain PropertyList XML files in $FG_ROOT/GraphicsProfiles/VENDOR, and then use the GL_* strings to load a matching default profile, with CLI arguments being processed afterwards, i.e. to take precedence, so that defaults can be overridden. | |1= like you said already, this could work pretty much like the joystick support - i.e. we would maintain PropertyList XML files in $FG_ROOT/GraphicsProfiles/VENDOR, and then use the GL_* strings to load a matching default profile, with CLI arguments being processed afterwards, i.e. to take precedence, so that defaults can be overridden. | ||
For instance, see $FG_SRC/Main/fg_init.cxx +466 fgInitConfig | For instance, see $FG_SRC/Main/fg_init.cxx +466 fgInitConfig(): | ||
<syntaxhighlight lang="cpp"> | |||
bool loadDefaults = options->shouldLoadDefaultConfig(); | |||
if (loadDefaults) { | |||
// Read global preferences from $FG_ROOT/preferences.xml | |||
SG_LOG(SG_INPUT, SG_INFO, "Reading global preferences"); | |||
fgLoadProps("preferences.xml", globals->get_props()); | |||
SG_LOG(SG_INPUT, SG_INFO, "Finished Reading global preferences"); | |||
</syntaxhighlight> | |||
This is one of the places, where we could also run another fgLoadPRops() call to load rendering settings that are overlaid onto /sim/rendering | This is one of the places, where we could also run another fgLoadPRops() call to load rendering settings that are overlaid onto /sim/rendering | ||