Graphics card profiles: Difference between revisions

Jump to navigation Jump to search
Line 44: Line 44:
   }}</ref>
   }}</ref>


We can do that by settings /sim/rendering/* as required, i.e. loading pre-configured profiles from $FG_ROOT
We can do that by setting /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
  | url    = http://forum.flightgear.org/viewtopic.php?p=275310#p275310
  | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
  | author = <nowiki>Hooray</nowiki>
  | date  = Feb 7th, 2016
  | added  = Feb 7th, 2016
  | script_version = 0.25
  }}
</ref> :
 
[[File:Sigar-support.png|250px|[[Resource Tracking for FlightGear]]]]
 
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:
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:


Line 72: Line 60:
   }}
   }}
</ref>
</ref>
However, CPU/RAM and VRAM info is not currently available, but we have patches providing this sort of info <ref>{{cite web
  | url    = http://forum.flightgear.org/viewtopic.php?p=275310#p275310
  | title  = <nowiki>Re: Review of FG on reddit: xpost</nowiki>
  | author = <nowiki>Hooray</nowiki>
  | date  = Feb 7th, 2016
  | added  = Feb 7th, 2016
  | script_version = 0.25
  }}
</ref> :
[[File:Sigar-support.png|250px|[[Resource Tracking for FlightGear]]]]


<references/>
<references/>

Navigation menu