I updated the FSX version (download below), the following problems should be fixed now:
- Playback of recorded date and time could result in lockup during AI traffic loading.
- When recording AI traffic, objects other than aircraft (ground vehicles, etc.) were recorded as well (but not played back), which could result in an application crash.
- Cycling through AI aircraft with FS Recorder cameras did also include other objects like ground vehicles, which could lead to error messages or in some cases an application crash.
Changes since v2.17 alpha:
- recording of FS Recorder cameras
- custom data recording (FSX variables and LVars, see below)
- recording of engine parameters, fuel levels and payloads
- saving of .frc file after recording a long flight with short recording interval and/or lots of AI traffic should be faster now, progress is shown
- added keyboard shortcuts for FS Recorder cameras
- added reverse mouse panning options to camera settings
- added LVars for recording, playback and rendering state (see below)
- split "Extended Data" option into Control Surfaces, Flap Positions and Gear Position
Due to a format change "Extended Data" recorded with v2.17 is not available for playback in v2.18.
Due to a bug in v2.17 files recorded with v2.18 can not be played with v2.17 (playback with previous versions should work).
This feature records camera position, orientation and zoom factor.
Currently only FS Recorder cameras are recorded, for other cameras no data is recorded (playback reverts to manual camera control in that case).
There are currently some problems with recording cameras in automatic panning mode and spot cameras. In some cases (especially with longer recording intervals and if camera and aircraft recording intervals differ) you might see some jitter of camera position/panning. I'm still working on a solution for this.
FOR EXPERTS ONLY: Custom data
Additional variables can be configured for recording/playback by adding CUSTOMVAR sections to the FSRecorder.ini file.
Add-on aircraft often use so-called 'local variables' or 'LVars' for custom switches, animations, etc. If you know the name of an LVar used by an add-on, you can configure it for recording.
For the FSX version you can additionally configure recording of most variables listed in the FSX SDK.
For each variable a CUSTOMVAR section in the FSRecorder.ini file has to be added:
- Code: Select all
The Units, UIGroup, DataType, Indexed and Interpolate entries are optional.
<nnn>: A unique number in the range 000 to 255 (you have to use three digits, leading zeros are required!)
<variable name>: The name identifying the variable. For LVars this has to be 'L:' followed by the variable name. For FSX variables it has to be 'FSX:' followed by a variable name from the FSX SDK (without index for indexed variables).
<unit name>: FSX only! A unit name from the FSX SDK. If you do not specify a unit name, the native unit of the variable is used.
<group name>: The group name is shown in the FS Recorder data options. If no group name is specified, "Custom Data" is used.
<data type>: The data type used to store the variable in the .frc file. Can be one of float, double, int, short, byte. If not specified, float is used.
<maximum index>: Some FSX variables have an index (e.g. engine parameters need an index in the range 1-4 to identify the engine). This parameter specifies the maximum index to record.
<interpolate>: Specifies if the variable is interpolated between recorded samples during playback (1) or not (0). The default is 1 for data types float and double and 0 for integer data types.
If custom variables are specified in the FSRecorder.ini file, their group names are shown in the recording/playback settings data option lists, and have to be checked there to enable recording/playback.
- Code: Select all
VarName=FSX:WATER RUDDER HANDLE POSITION
Playback only available in FSX version! (In FS9 the respective variables are read-only.)
Depending on the type of engine the following engine parameters are recorded:
- N1, N2, EPR for jet and turboprop engines
- cowl flaps for piston engines
- propeller RPM for piston and turboprop engines
Recording, playback and rendering state LVars:
FS Recorder now sets the following LVars to indicate recording, playback and video rendering state:
L:FSRecorderIsRecording : non-zero if recording, otherwise zero
L:FSRecorderIsPlaying : non-zero if playing, otherwise zero
L:FSRecorderIsRendering : non-zero if rendering, otherwise zero
Add-on developers may use these variables to check FS Recorder recording/playback/rendering state.
The converter should support all of the new features. The format of text files has slightly changed, see the documentation. If you want to use it with text file from previous versions, you might have make a few changes.
FS Recorder 2.181 alpha for FSX (updated 19.08.2012)
FS Recorder 2.18 alpha for FS2004