Graphics card profiles: Difference between revisions

Jump to navigation Jump to search
m
trying a different form of quoting via instant-cquotes ...
No edit summary
m (trying a different form of quoting via instant-cquotes ...)
Line 2: Line 2:


== Idea ==
== Idea ==
{{DeQuote}}
{{FGCquote
|1= The only thing I want to do is detect the video card and based on the GL renderer name turn on ALS (or not), turn on water shader (or not), turn on the 3d city shader (or not), etc.
The default would not be touched but based on the detected video card certain options would get enabled, making the first impression much more pleasant (for first time users).




|2= {{cite web
This idea dates back to early 2016 when a few FlightGear contributors were discussing a reddit review of FlightGear which highlighted that FlightGear's default graphics settings didn't seem to fit/match the graphics hardware available.
 
FlightGear core deveoper Erik Hofman came up with the idea to preselect more appropriate default settings based on parsing various GL_* strings (in particular GL_VENDOR), i.e. detect the video card and based on the GL renderer name turn on [[ALS]] (or not), turn on water shader (or not), turn on the 3d city shader (or not), etc.
 
The defaults would not be touched but based on the detected video card certain options would get enabled, making the first impression much more pleasant (for first time users). <ref>{{cite web
   | url    = http://forum.flightgear.org/viewtopic.php?p=275302#p275302
   | url    = http://forum.flightgear.org/viewtopic.php?p=275302#p275302
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
Line 15: Line 15:
   | added  = Feb 7th, 2016
   | added  = Feb 7th, 2016
   | script_version = 0.25
   | script_version = 0.25
   }}
   }}</ref>
}}


{{FGCquote
Furthermore, suggesting that it could be a good idea to make sure the configuration has at least 20fps at KSFO.
|1= It could be a good idea to make sure the configuration has at least 20fps at KSFO.
Also it would be a one time configuration for after a (re)install. The settings would be written to a local configuration afterwards so users could still tweak for their own liking.<ref>{{cite web
 
Also it would be a one time configuration for after a (re)install. The settings would be written to a local configuration afterwards so users could still tweak for their own liking.
 
 
|2= {{cite web
   | url    = http://forum.flightgear.org/viewtopic.php?p=275411#p275411
   | url    = http://forum.flightgear.org/viewtopic.php?p=275411#p275411
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
Line 32: Line 26:
   | script_version = 0.25
   | script_version = 0.25
   }}
   }}
}}
</ref>


{{FGCquote
Other contributors, like Thorsten mentioned, that it does not seem to be a technical problem - to query a string from the property tree is easy, to write a routine which sets other properties based on what the string says is equally easy.
|1= It does not seem to be a technical problem - to query a string from the property tree is easy, to write a routine which sets other properties based on what the string says is equally easy.
The problem is the meat of it - someone has to know what settings are likely to run on what graphics cards. And someone has to write the routine that does it. Then it's done. <ref>{{cite web
The problem is the meat of it - someone has to know what settings are likely to run on what graphics cards. And someone has to write the routine that does it. Then it's done.  
|2= {{cite web
   | url    = http://forum.flightgear.org/viewtopic.php?p=275312#p275312
   | url    = http://forum.flightgear.org/viewtopic.php?p=275312#p275312
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
Line 44: Line 36:
   | added  = Feb 7th, 2016
   | added  = Feb 7th, 2016
   | script_version = 0.25
   | script_version = 0.25
   }}
   }}</ref>
}}


{{FGCquote
We can do that by settings /sim/rendering/* as required, i.e. loading pre-configured profiles from $FG_ROOT
|1= You can do that by settings /sim/rendering/* as required, i.e. loading pre-configured profiles from $FG_ROOT
CPU/RAM and VRAM info is not currently available, but we have patches providing this sort of info <ref>{{cite web
CPU/RAM and VRAM info is not currently available, but we have patches providing this sort of info:
[[Resource Tracking for FlightGear]]
 
[[File:Sigar-support.png|250px]]
|2= {{cite web
   | url    = http://forum.flightgear.org/viewtopic.php?p=275310#p275310
   | url    = http://forum.flightgear.org/viewtopic.php?p=275310#p275310
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
Line 61: Line 47:
   | script_version = 0.25
   | script_version = 0.25
   }}
   }}
}}
</ref> :
 
[[Resource Tracking for FlightGear]] [[File:Sigar-support.png|250px]]


{{FGCquote
For example, $FG_ROOT/gui/dialogs/about.xml and rendering.xml are already accessing some of the GL* data via properties, e.g. to display the Intel warning, but also the GPU vendor info:
|1= $FG_ROOT/gui/dialogs/about.xml and rendering.xml are already accessing some of the GL* data via properties, e.g. to display the Intel warning, but also the GPU vendor info:
[[About dialog]] [[File:About dialog 2.10.png|250px]]
[[About dialog]]


[[File:About dialog 2.10.png|250px]]
Thus, we would ideally introduce 3-4 "vendor"-specific folders and then introduce a PropertyList XML file where the RENDERER string is used to select a certain default configuration.
Thus, we would ideally introduce 3-4 "vendor"-specific folders and then introduce a PropertyList XML file where the RENDERER string is used to select a certain default configuration.
For testing purposes, we could promote this features on the forum/website/IRC and facebook to get people involved with testing, and to provide feedback - so that we know what settings work well enough, using Nasal's http APIs, such feedback could even be gathered online.
For testing purposes, we could promote this features on the forum/website/IRC and facebook to get people involved with testing, and to provide feedback - so that we know what settings work well enough, using Nasal's http APIs, such feedback could even be gathered online.
|2= {{cite web
<ref>{{cite web
   | url    = http://forum.flightgear.org/viewtopic.php?p=275498#p275498
   | url    = http://forum.flightgear.org/viewtopic.php?p=275498#p275498
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
   | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
Line 78: Line 64:
   | script_version = 0.25
   | script_version = 0.25
   }}
   }}
}}
</ref>
 
<references/>


== Approach ==
== Approach ==
{{DeQuote}}
{{FGCquote
{{FGCquote
|1= that's basically a form of feature-scaling: [[Feature Scaling]]
|1= that's basically a form of feature-scaling: [[Feature Scaling]]

Navigation menu