Howto:Troubleshooting Aircraft Performance Issues: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
{{Stub}}
{{Stub}}
[[File:Su15-complexity-osg-stats.jpeg|right|thumb|http://forum.flightgear.org/viewtopic.php?f=4&t=25961&start=135]]


== Objective ==
== Objective ==

Revision as of 10:15, 13 November 2015

This article is a stub. You can help the wiki by expanding it.

Objective

Document the main steps to understand performance issues at the aircraft level, i.e. FDM, 3D modeling, texturing and Nasal scripting.

Approach

We will be testing different components, and features, of each aircraft in isolation, to exclude certain factors and determine if/how performance is affected by certain features.

For instance, when loading an aircraft in osgviewer, we can basically determine the maximal theoretical rendering speed that can be obtained (flightgear using osgviewer internally), without adding any flightgear specific subsystems/overhead.

Equally, when running a FDM in standalone mode, we can look at the FDM overhead without graphics and/or scripting playing any role.

And once we load the same aircraft in fgviewer, we can look at it without Nasal playing any role.

Metrics

The main metrics will be osg-stats (link) and frame rate/frame spacing when in FG, as well as ogging performance monitor metrics (link)

Use Cases

We will be using aircraft that were tested on the forum, especially:

  • Su-15 vs. F15
  • extra500
  • 777-2000

standalone FDM

osgviewer

fgviewer

Disabling Nasal

Minimal startup profile

Using draw masks