Fgtape: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (http://forum.flightgear.org/search.php?st=0&sk=t&sd=d&sr=posts&keywords=fgtape) |
||
| Line 3: | Line 3: | ||
{{main article|Instant Replay}} | {{main article|Instant Replay}} | ||
So called [[Fgtape]] files are [[PropertyList XML File|PropertyList-encoded XML files]] created by the [[FlightGear]] [[Instant Replay|flight recorder]] subsystem, they contain serialized [[Property|FlightGear properties]] for replaying flight data/flights. | So called [[Fgtape]][http://forum.flightgear.org/search.php?st=0&sk=t&sd=d&sr=posts&keywords=fgtape] files are [[PropertyList XML File|PropertyList-encoded XML files]] created by the [[FlightGear]] [[Instant Replay|flight recorder]] subsystem, they contain serialized [[Property|FlightGear properties]] for replaying flight data/flights. | ||
The whole system is [[XML]]-configurable, so that custom/[[Aircraft properties reference|aircraft-specific properties]] can be easily supported, while generic/common properties are typically included from a shared location in $FG_ROOT. | The whole system is [[XML]]-configurable, so that custom/[[Aircraft properties reference|aircraft-specific properties]] can be easily supported, while generic/common properties are typically included from a shared location in $FG_ROOT. | ||
{{FGCquote|1= fgtape = $FG_ROOT/Docs/README.flightrecorder: http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.flightrecorder(what used to be the old "instant replay" system, but ended up getting generalied by ThorstenB to become a generic "Property Recorder" subsystem.The system could be useful for doing both 1) creating repeatable benchmark situations that override end-user configuration, but also for 2) sharing end-user created flights for reproducing certain issues.The case we've been discussing here is to use the flight recorder subsystem (fgtape) to create/save a "benchmark flight" into $FG_ROOT, so that end-users can use that to "play" the flight, while a few lines of Nasal would sample a handful of properties to determine the impact on frame rate/spacing.The alternative would have been to use Nasal for creating the situation/flight in a scripted fashion, but that is probably not such a good idea, especially because Nasal may very well add to the CPU overhead anywayRight now, fgtapes are all about aircraft-specific properties: http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Aircraft/Generic/flightrecorder/|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=258516#p258516 | title = <nowiki>Re: How to tell if you are CPU or GPU limited (split)</nowiki> | author = <nowiki>Hooray</nowiki> | date = Sep 22nd, 2015 }}}} | {{FGCquote|1= fgtape = $FG_ROOT/Docs/README.flightrecorder: http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.flightrecorder(what used to be the old "instant replay" system, but ended up getting generalied by ThorstenB to become a generic "Property Recorder" subsystem.The system could be useful for doing both 1) creating repeatable benchmark situations that override end-user configuration, but also for 2) sharing end-user created flights for reproducing certain issues.The case we've been discussing here is to use the flight recorder subsystem (fgtape) to create/save a "benchmark flight" into $FG_ROOT, so that end-users can use that to "play" the flight, while a few lines of Nasal would sample a handful of properties to determine the impact on frame rate/spacing.The alternative would have been to use Nasal for creating the situation/flight in a scripted fashion, but that is probably not such a good idea, especially because Nasal may very well add to the CPU overhead anywayRight now, fgtapes are all about aircraft-specific properties: http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Aircraft/Generic/flightrecorder/|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=258516#p258516 | title = <nowiki>Re: How to tell if you are CPU or GPU limited (split)</nowiki> | author = <nowiki>Hooray</nowiki> | date = Sep 22nd, 2015 }}}} | ||
Revision as of 06:45, 23 September 2015
| This article is a stub. You can help the wiki by expanding it. |
|
|
So called Fgtape[1] files are PropertyList-encoded XML files created by the FlightGear flight recorder subsystem, they contain serialized FlightGear properties for replaying flight data/flights.
The whole system is XML-configurable, so that custom/aircraft-specific properties can be easily supported, while generic/common properties are typically included from a shared location in $FG_ROOT.
|
fgtape = $FG_ROOT/Docs/README.flightrecorder: http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Docs/README.flightrecorder(what used to be the old "instant replay" system, but ended up getting generalied by ThorstenB to become a generic "Property Recorder" subsystem.The system could be useful for doing both 1) creating repeatable benchmark situations that override end-user configuration, but also for 2) sharing end-user created flights for reproducing certain issues.The case we've been discussing here is to use the flight recorder subsystem (fgtape) to create/save a "benchmark flight" into $FG_ROOT, so that end-users can use that to "play" the flight, while a few lines of Nasal would sample a handful of properties to determine the impact on frame rate/spacing.The alternative would have been to use Nasal for creating the situation/flight in a scripted fashion, but that is probably not such a good idea, especially because Nasal may very well add to the CPU overhead anywayRight now, fgtapes are all about aircraft-specific properties: http://sourceforge.net/p/flightgear/fgdata/ci/next/tree/Aircraft/Generic/flightrecorder/ — Hooray (Sep 22nd, 2015). Re: How to tell if you are CPU or GPU limited (split).
(powered by Instant-Cquotes) |
|