20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
m
→Minimal Startup Profile: https://gitorious.org/fg/fgdata/commit/67e625a81232b6282c7218418a6091a962567be8
m (cat: Howto) |
m (→Minimal Startup Profile: https://gitorious.org/fg/fgdata/commit/67e625a81232b6282c7218418a6091a962567be8) |
||
| Line 88: | Line 88: | ||
--prop:/sim/rendering/particles=0 | --prop:/sim/rendering/particles=0 | ||
</pre> | </pre> | ||
{{Note|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:/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 | |||
}} | |||
Using these settings, frame rates between 400-500 fps and a steady frame spacing (latency) of 3-11 ms, can be achieved on a notebook from 2007 (1024x768). Disabling wireframe mode lowers the framerate by about 50-80 fps. The window should be up and running (fully initialized) within 3-5 seconds, even on moderately old hardware (absent a navcache rebuild). | Using these settings, frame rates between 400-500 fps and a steady frame spacing (latency) of 3-11 ms, can be achieved on a notebook from 2007 (1024x768). Disabling wireframe mode lowers the framerate by about 50-80 fps. The window should be up and running (fully initialized) within 3-5 seconds, even on moderately old hardware (absent a navcache rebuild). | ||