20,741
edits
m (→The system monitor: + messy quotes that should be merged/rewritten into a single message probably) |
|||
Line 3: | Line 3: | ||
== Profiling == | == Profiling == | ||
For developers, and people building from source, FlightGear versions >= 2.9 provide real profiling support using Google PerfTools, for details please see [[Built-in Profiler]]. | For developers, and people building from source, FlightGear versions >= 2.9 provide real profiling support using Google PerfTools, for details please see [[Built-in Profiler]]. | ||
== Terms == | |||
{{FGCquote | |||
|1= those systems are not "processes", but just "loops" - i.e. whatever the thing is called in the list, you should append "update-loop" to it - and some names are still misleading (events=Nasal). | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=264426#p264426 | |||
| title = <nowiki>Re: Su-15</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Nov 13th, 2015 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= FG is basically using cooperative multi-tasking-imagine it like a team of people (15+), all of whom need to finish their work and hand it over to the next person, so that a single frame can be produced - with some people (subsystems) being allowed to redo/check their work several times in a row (fdm, autopilot), while others will only get a single opportunity to update their internal state. | |||
Finally, it is this "team of people" that will produce a single frame - so whenever "someone" is too slow, it will end up causing stuttering. No matter the reason, scenery/terrain, Nasal etc - at some point, another subsystem will have to wait, which means fewer frames created per second. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=264313#p264313 | |||
| title = <nowiki>Re: Su-15</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Nov 13th, 2015 | |||
}} | |||
}} | |||
== The system monitor == | == The system monitor == |