20,741
edits
Canvas troubleshooting: Difference between revisions
Jump to navigation
Jump to search
m
→Adding draw masks for Canvas: http://forum.flightgear.org/viewtopic.php?f=42&t=24728&p=225846&hilit=masks#p225846
m (→Adding draw masks for Canvas: http://forum.flightgear.org/viewtopic.php?f=42&t=24728&p=225846&hilit=masks#p225846) |
|||
| Line 234: | Line 234: | ||
=== Adding draw masks for Canvas === | === Adding draw masks for Canvas === | ||
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). | |||
The following patch is intended to help determine the rendering overhead of Canvas by adding optional draw-masks for disabling rendering of Canvas textures via their corresponding placements (aircraft, scenery and GUI): | The following patch is intended to help determine the rendering overhead of Canvas by adding optional draw-masks for disabling rendering of Canvas textures via their corresponding placements (aircraft, scenery and GUI): | ||
| Line 240: | Line 245: | ||
Under the hood, the corresponding Nasal/C++ code updating Canvas textures would obviously still be running - it would just be rendering that is explicitly disabled here. | Under the hood, the corresponding Nasal/C++ code updating Canvas textures would obviously still be running - it would just be rendering that is explicitly disabled here. | ||
=== Hooking up Canvas to the Osg Stats === | === Hooking up Canvas to the Osg Stats === | ||
<syntaxhighlight lang="diff"> | <syntaxhighlight lang="diff"> | ||