Graphics card profiles: Difference between revisions

Jump to navigation Jump to search
m
Line 114: Line 114:
</ref>
</ref>


<references/>
== Implementation ==
== Implementation ==
{{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.
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">
<syntaxhighlight lang="cpp">
Line 129: Line 132:
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


Technically, we are already using this approach to suport translations, which are also read/overlaid into the tree
Technically, we are already using this approach to suport translations, which are also read/overlaid into the tree<ref>{{cite web
|2= {{cite web
   | url    = http://forum.flightgear.org/viewtopic.php?p=275452#p275452
   | url    = http://forum.flightgear.org/viewtopic.php?p=275452#p275452
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
Line 138: Line 140:
   | script_version = 0.25
   | script_version = 0.25
   }}
   }}
}}
</ref>
 
 
<references/>

Navigation menu