Replays of helicopter flights look weird: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
No edit summary
m (+- Minor cleanup; cat: Howto)
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{infobox KB
<!--{{infobox KB
|fgversion = 2.6 and later
|fgversion = 2.6 and later
}}
}}-->
 
 
 
== Problem ==
When recording and replaying helicopter flights with the new flight recorder, the replay looks weird. The flight path appears to seem edgy and the helicopter performs maneuvers which are physically impossible.
When recording and replaying helicopter flights with the new flight recorder, the replay looks weird. The flight path appears to seem edgy and the helicopter performs maneuvers which are physically impossible.


== Reason ==
== Reason ==
The new flight recorder in it's default configuration only records the last 60 seconds of the flight in full data resolution. Everything older is stored in a compressed format and interpolated during replay, which leads to unnatural motion patterns of helicopters in the replay before the last 60 seconds.
The new flight recorder in it's default configuration only records the last 60 seconds of the flight in full data resolution. Everything older is stored in a compressed format and interpolated during replay, which leads to unnatural motion patterns of helicopters in the replay before the last 60 seconds.


== Solution ==
== Solution ==
Change the configuration of the flight recorder in preferences.xml to keep a bigger amount of data uncompressed.
Change the configuration of the flight recorder in preferences.xml to keep a bigger amount of data uncompressed.


== Caveats ==
== Caveats ==
Uncompressed data takes more memory than compressed data. As an example, the BK117 requires about 1MB per minute of uncompressed data recording.
Uncompressed data takes more memory than compressed data. As an example, the BK117 requires about 1MB per minute of uncompressed data recording.


== Example ==
== Example ==
This example extends the uncompressed recording time to 10 minutes and the medium compression time to 30 minutes.
This example extends the uncompressed recording time to 10 minutes and the medium compression time to 30 minutes.
<nowiki>
<syntaxhighlight lang="xml">
<replay>
<replay>
<duration type="double">90</duration>
<duration type="double">90</duration>
Line 44: Line 32:
</buffer>
</buffer>
</replay>
</replay>
</nowiki>
</syntaxhighlight>
 
== Related content ==
=== Wiki articles ===
* [[Instant Replay]]
 
=== Readme files ===
* {{readme file|flightrecorder}}
 
[[Category:Howto]]

Latest revision as of 11:23, 20 August 2019

When recording and replaying helicopter flights with the new flight recorder, the replay looks weird. The flight path appears to seem edgy and the helicopter performs maneuvers which are physically impossible.

Reason

The new flight recorder in it's default configuration only records the last 60 seconds of the flight in full data resolution. Everything older is stored in a compressed format and interpolated during replay, which leads to unnatural motion patterns of helicopters in the replay before the last 60 seconds.

Solution

Change the configuration of the flight recorder in preferences.xml to keep a bigger amount of data uncompressed.

Caveats

Uncompressed data takes more memory than compressed data. As an example, the BK117 requires about 1MB per minute of uncompressed data recording.

Example

This example extends the uncompressed recording time to 10 minutes and the medium compression time to 30 minutes.

		<replay>
			<duration type="double">90</duration>
			<view type="int">1</view>
			<looped type="bool" userarchive="y">true</looped>
			<buffer> <!-- replay buffer configuration -->
				<!-- 1st buffer level: short term -->
				<high-res-time type="double">600</high-res-time> <!-- 60 seconds -->
				<!-- short term sample rate is as every frame (fixed) -->
				<!-- 2nd buffer level: medium term -->
				<medium-res-sample-dt type="double">0.5</medium-res-sample-dt>
				<medium-res-time type="double">1800</medium-res-time><!-- 10 mins -->
				<!-- 3rd buffer level: long term -->
				<low-res-sample-dt type="double">5.0</low-res-sample-dt>
				<low-res-time type="double">3600.0</low-res-time><!-- 1 h -->
			</buffer>
		</replay>

Related content

Wiki articles

Readme files