Draw masks: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 3: Line 3:


[[File:Property-browser-with-draw-masks-shown.png|thumb|Property browser with draw masks shown]]
[[File:Property-browser-with-draw-masks-shown.png|thumb|Property browser with draw masks shown]]
{{FGCquote
|1= Another goal is to add more node bits (and a GUI dialog to control them) so various categories of objects can be disabled during the update pass. This will mean the direct hit of, say, AI models vs particles vs random trees can be measured. Of course it won't account for resources (memory, textures) burned by such things, but would still help different people identify slowness on their setups.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/29564161/
  | title  = <nowiki>Re: [Flightgear-devel] Rendering passes question</nowiki>
  | author = <nowiki>James Turner</nowiki>
  | date  = Jul 19th, 2012
  }}
}}


{{FGCquote|1= There's so called "draw-masks" which are property-controlled switches for enabling/disabling rendering of certain scene details, including 1) scenery/terrain, 2) aircraft, 3) models, 4) clouds.This can be used for troubleshooting performance issues - you can basically toggle individual scene graphs on/off, to see if/how performance is affected.For example, if performance improves dramatically by disabling the terrain, you are mainly affected scenery complexity.Equally, disabling the (main) aircraft, will tell you if it's the complexity of the 777 3D model (cockpit). |2= {{cite web  | url    = http://forum.flightgear.org/viewtopic.php?p=225846#p225846  | title  = <nowiki>Re: FlightGear 3.2 with B777 running extremely slow</nowiki>  | author = <nowiki>Hooray</nowiki>  | date  = Nov 29th, 2014  }}}}
{{FGCquote|1= There's so called "draw-masks" which are property-controlled switches for enabling/disabling rendering of certain scene details, including 1) scenery/terrain, 2) aircraft, 3) models, 4) clouds.This can be used for troubleshooting performance issues - you can basically toggle individual scene graphs on/off, to see if/how performance is affected.For example, if performance improves dramatically by disabling the terrain, you are mainly affected scenery complexity.Equally, disabling the (main) aircraft, will tell you if it's the complexity of the 777 3D model (cockpit). |2= {{cite web  | url    = http://forum.flightgear.org/viewtopic.php?p=225846#p225846  | title  = <nowiki>Re: FlightGear 3.2 with B777 running extremely slow</nowiki>  | author = <nowiki>Hooray</nowiki>  | date  = Nov 29th, 2014  }}}}

Revision as of 12:05, 15 November 2015

This article is a stub. You can help the wiki by expanding it.
Note  In its current form, this section/article is largely based on quotes collected from various related discussions/channels (devel list, forum etc) using the Instant-Cquotes script. Wiki users and other contributors are encouraged to help rewrite/edit contents accordingly to help get rid of unnecessary quoting (i.e. while the wiki is not intended to be a collection of quotes, quotes are sometimes the best/easiest way to bootstrap new articles, while also providing a good way to link back to related discussions in the archives).

While rewriting usually only entails changing first person speech to 3rd person. However, please try to retain references/links to the original discussion whenever possible.

Property browser with draw masks shown
Cquote1.png Another goal is to add more node bits (and a GUI dialog to control them) so various categories of objects can be disabled during the update pass. This will mean the direct hit of, say, AI models vs particles vs random trees can be measured. Of course it won't account for resources (memory, textures) burned by such things, but would still help different people identify slowness on their setups.
— James Turner (Jul 19th, 2012). Re: [Flightgear-devel] Rendering passes question.
(powered by Instant-Cquotes)
Cquote2.png
Cquote1.png There's so called "draw-masks" which are property-controlled switches for enabling/disabling rendering of certain scene details, including 1) scenery/terrain, 2) aircraft, 3) models, 4) clouds.This can be used for troubleshooting performance issues - you can basically toggle individual scene graphs on/off, to see if/how performance is affected.For example, if performance improves dramatically by disabling the terrain, you are mainly affected scenery complexity.Equally, disabling the (main) aircraft, will tell you if it's the complexity of the 777 3D model (cockpit).
— Hooray (Nov 29th, 2014). Re: FlightGear 3.2 with B777 running extremely slow.
(powered by Instant-Cquotes)
Cquote2.png
Cquote1.png Beginning with FlightGear 3.1+, you can also toggle individual scenegraph traversal masks on/off (these can be changed at runtime using the Property browser:--prop:browser=/sim/rendering/draw-mask--prop:/sim/rendering/draw-mask/terrain=0--prop:/sim/rendering/draw-mask/aircraft=0--prop:/sim/rendering/draw-mask/models=0--prop:/sim/rendering/draw-mask/clouds=0
— Hooray (Nov 29th, 2014). Re: FlightGear 3.2 with B777 running extremely slow.
(powered by Instant-Cquotes)
Cquote2.png
Cquote1.png Those draw masks will not prevent stuff from being loaded (=consuming RAM/memory), it will merely disable updates to the already loaded data. Which also applies to other stuff like aircraft.Which is why heavy aircraft like the 777-200 or the extra500 will still perform much worse than comparatively lightweight aircraft like the ufo, ogeL, santa or the default c172p (especially the 2D version is fairly lightweight).
— Hooray (Jul 5th, 2014). Re: Flatland.
(powered by Instant-Cquotes)
Cquote2.png


To open a property browser with the corresponding properties, use --prop:browser=/sim/rendering/draw-mask (can be also added to your fgfsrc file)