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 17:39, 22 November 2015
, 22 November 2015→Motivation
| Line 7: | Line 7: | ||
== Motivation == | == Motivation == | ||
We are seeing more and more complex aircraft/features developed by aircraft developers, with non-obvious impact on overall FlightGear performance. Many aircraft developers don't fully understand how to draw correct conclusions from interpreting their findings, i.e. if performance issues are related to the FDM, texturing/3D model complexity or other aspects like systems simulation (e.g. Nasal). | We are seeing more and more complex aircraft/features developed by aircraft developers, with non-obvious impact on overall FlightGear performance. Many aircraft developers don't fully understand how to draw correct conclusions from interpreting their findings, i.e. if performance issues are related to the FDM, texturing/3D model complexity or other aspects like systems simulation (e.g. Nasal). | ||
{{FGCquote | |||
|1= Someone who uses 4096x4096 texture sheets for aircraft usually knows pretty darn well that they cost lots of resources. He just thinks that that's how he wants to spend resources. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=200280#p200280 | |||
| title = <nowiki>Re: fg3.0rc1 memory usage</nowiki> | |||
| author = <nowiki>Thorsten</nowiki> | |||
| date = Feb 8th, 2014 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= most aircraft developers who are involved in 3D modeling and texturing, and not necessarily coders, i.e. they may not necessarily understand the impact on frame rate and frame spacing certain actions have - I have seen too many screenshots of highly detailed cockpits posted by aircraft developers, who seem to be also just getting 10-15 fps - so they apparently don't know how to solve the problem. Having a list of expensive resources (3D models, texture, scripts) would be useful to identify problematic components - I don't think most end-users would accept a 777 where it is obvious that 60% of the load is caused by heavy textures and 3D models with lots of vertices - likewise, Nasal scripts having 30-40% impact on frame spacing and latency would also not be accepted for very long. Ideally, this would be a part of a "review" process once aircraft are committed to fgdata, or at least if they are to be considered for inclusion into a release. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=200286#p200286 | |||
| title = <nowiki>Re: fg3.0rc1 memory usage</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Feb 8th, 2014 | |||
}} | |||
}} | |||
== Objective == | == Objective == | ||
Document the main steps to understand performance issues at the aircraft level, i.e. FDM, 3D modeling, texturing and Nasal scripting. | Document the main steps to understand performance issues at the aircraft level, i.e. FDM, 3D modeling, texturing and Nasal scripting. | ||