[NEED TRACK REPLAY]Track File Does Not Reproduce TGP Movements Correctly

[sidekick65]

The issue was noted while flying a mission in which I did the following.

 

- Located a desired target and slewed to it's location with the TGP.

- Created a mark point

- Repeated the steps for a second target

- Later - came back and selected the first mark point on the HUD

- Set it as SPI

- Slaved a maverick to the mark point

- The maverick identified the target, locked on and was launched and hit the target

- Repeated the same procedure for the second mark point.

- Mission was ended and a track was saved.

 

Later the track file was replayed

- No changes - other than activation of video capture

- The TGP did not slew to the original target point

- The Mark point was therefore designated incorrectly.

- The same effect was evident for the second mark point

- Neither mark point ended up near where they were designated in the as-flown mission

- When the Maverick was slaved to the mark point as SPI it did not lock the target and generated the "no targer lock error" and did not launch.

 

Clearly, this makes it impossible to use the recorded track to review the mission or generate any kind of tutorial video.

 

The behaviour was reproduced two different times with two different track files.

 

Each track was replayed more than once to ensure that it was not a random departure as occasionally happens. The error in TGP slew "appeared" to be consistent but that could not be verified.

 

The same OpenBeta release was used to record the track files and play them back.

 

I have the track files if that would be helpful.

[BIGNEWY]

Hi please always include the track replays when reporting.

 

Track replays are known to be difficult sometimes.

 

thanks

[sidekick65]

Here are two track files in which I encountered the problem.

 

Yes, I understand (and regularly experience) the issues with track files. Usually, the artifacts can be worked around - often they just seem to be statistical anomalies and a second run through resolves the issue.

 

This seems to be a bit different in that the behaviour of not reproducing the as-flown results was consistent. And to be fair, I think that if the option of recording a track file exists it would seem reasonable to expect that it recreate the as-flown experience (at least with some fidelity) MOST of the time.

 

Thanks for looking in to it.

 

Let me know if it would be helpful to have a video recording of a replay as well.

a10range1.trk

[sidekick65]

Hmmm... it seems the second file is just slightly too large to upload (5.32Mb). Let me know if there is another way that I can transfer it to you.