20,741
edits
Howto:Troubleshooting Aircraft Performance Issues: Difference between revisions
Jump to navigation
Jump to search
Howto:Troubleshooting Aircraft Performance Issues (view source)
Revision as of 12:13, 13 November 2015
, 13 November 2015→Approach
| Line 24: | Line 24: | ||
And once we load the same aircraft in fgviewer, we can look at it without Nasal playing any role. | And once we load the same aircraft in fgviewer, we can look at it without Nasal playing any role. | ||
{{FGCquote|1= We do have some fairly heavy/complex models, some unnecessarily so - i.e. in areas that add little to the overall realism (e.g. 777 or extra500).To see for yourself, you could dump the scene graph to a file using the debug menu, and inspect the whole thing in osgviewer. Which is also a good way to see how much of this is due to FlightGear itself.To see the impact of your model in relation to scenery/terrain etc, you can use the draw masks /sim/rendering/draw-masks and the minimal startup profile: [[Troubleshooting crashes#Minimal startup profile]]To see the impact of enabling/disabling Rembrandt, you would obviously have to re-do the test accordingly.But overall, this should give you a fairly good idea for your hardware, especially in conjunction with using the osg stats: [[Howto:Use the system monitor#Interpreting the OSG on screen stats]]|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=260111#p260111 | title = <nowiki>Re: Polygon Limits</nowiki> | author = <nowiki>Hooray</nowiki> | date = Oct 9th, 2015 }}}} | |||
== Metrics == | == Metrics == | ||