- Messages
- 731
- Country
I know - who is still messing with this old sim in 2024? OK, guilty as charged.
But I wanted to share this, as I was unable to find anything on it here or anywhere online.
When making your P3D scenarios in XML, there is a slightly different code for referencing the playback file - changes in bold.
<AirplanePlaybackAI>
<Playing>True</Playing>
<RecordingFilename>FA18LAUNCH29</RecordingFilename>
<TimeStamp>0.500</TimeStamp>
</AirplanePlaybackAI>
In FSX this would have been as follows:
<AirplanePlaybackAI>
<Playing>True</Playing>
<Filename>FA18LAUNCH29.FSR</Filename>
<TimeStamp>0.500</TimeStamp>
</AirplanePlaybackAI>
In comparing the FSX missions with the Tampa Tour example in the P3D sdk, I came across this.
What was happening was the AI aircraft was spawning just taking off, displaying whatever erratic behavior, but the recording was not being referenced at all.
Adding or removing the .FSR seems to not really make a difference, but changing the XML code from <Filename> to <RecordingFilename> did the trick immediately.
Sharing this for future notes - maybe somebody will find this in a search someday.
But I wanted to share this, as I was unable to find anything on it here or anywhere online.
When making your P3D scenarios in XML, there is a slightly different code for referencing the playback file - changes in bold.
<AirplanePlaybackAI>
<Playing>True</Playing>
<RecordingFilename>FA18LAUNCH29</RecordingFilename>
<TimeStamp>0.500</TimeStamp>
</AirplanePlaybackAI>
In FSX this would have been as follows:
<AirplanePlaybackAI>
<Playing>True</Playing>
<Filename>FA18LAUNCH29.FSR</Filename>
<TimeStamp>0.500</TimeStamp>
</AirplanePlaybackAI>
In comparing the FSX missions with the Tampa Tour example in the P3D sdk, I came across this.
What was happening was the AI aircraft was spawning just taking off, displaying whatever erratic behavior, but the recording was not being referenced at all.
Adding or removing the .FSR seems to not really make a difference, but changing the XML code from <Filename> to <RecordingFilename> did the trick immediately.
Sharing this for future notes - maybe somebody will find this in a search someday.