FS Recorder 2.18 alpha (Updated 19.08.2012)

[noisy]

The next alpha release 2.18 is now available for download (links below). Note that I had to rewrite large parts of code and I didn't have much time for testing, so some things might be broken! As I'll be on vacation for the next two weeks I decided to release it anyway. Please let me know if you find something not working and I'll fix it after my return.

Update 19.08.2012

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

Compatibility note

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).


Camera recording

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

[CUSTOMVAR.<nnn>]
VarName=<variable name>
Units=<unit name>
UIGroup=<group name>
DataType=<data type>
Indexed=<maximum index>
Interpolate=<interpolate>

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.

Examples:

Code: Select all

[CUSTOMVAR.001]
VarName=FSX:WATER RUDDER HANDLE POSITION
Units=Percentage
UIGroup=Water Rudder
DataType=float
Interpolate=0

[CUSTOMVAR.002]
VarName=L:GearLeverPos747
UIGroup=Boeing 747
DataType=byte
Interpolate=0


Engine parameters:

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.


FRC converter

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.


Download links

FS Recorder 2.181 alpha for FSX (updated 19.08.2012)
FS Recorder 2.18 alpha for FS2004

[mfastx]

Unfortunately I am having a problem with this version as well. All goes well for the recording part, but when I try to play back the flight, FSX just freezes when it is loading. I'll get to 85%, or 67%, or 43%, but it alwasy just freezes, it doesn't ever finish loading. I've let it sit for 30-45 minutes and nothing.

Here are my settings:

[PLAYBACK]
LoadFlight=0
LoadMarkers=1
ContFlags=63583
DiscFlags=1055
CustFlags=0
PlayCamera=0
[RECORDING]
Interval=1250
IntervalAI=10000
IntervalCamera=1250
RecordUser=1
RecordAI=1
RecordCamera=0
RecordPlayingTraffic=0
SaveFlight=0
ContFlags=63582
ContFlagsAI=31
DiscFlags=1052
DiscFlagsAI=23
CustFlags=0
CustFlagsAI=0
AutoStopMode=0
AutoStopTime=10
[SETTINGS]
EnableReplay=0
MaxReplaySize=10
Search1=0
Search2=0
Search3=0
JumpSize1=15
JumpSize2=60
JumpSize3=300
SearchSpeed1=5
SearchSpeed2=15
SearchSpeed3=50
LoadAircraft=1
UnpauseStartPlay=1
PauseEndPlay=1
RestoreAfterPlay=0
SetSimRate=1
SetSimRateSearch=0
LimitSimRate=0
EnableControls=1
EnableControlsAI=0
DisplayRecording=0
DisplayPlayback=0
ShowWindow=0
ShowDataWindow=0
PlayRecAI=1
DisableLiveAI=1
MaxAircraft=0
ShowRecDialog=1
ShowPlayDialog=0
FileDialog=1
FileDialogBefore=0
TempDirectory=C:\Program Files (x86)\FS Recorder for FSX
Speeds=0.1|0.2|0.3|0.5|1|2|3|5|10
DisableCameras=1
EnableAutoplay=0
[Dialogs]
FrcPath=C:\Users\Maurice\Documents\Flight Simulator X Files

And this is my log I believe, it's is extremely short and doesn't show much of a problem IMO:

FS Recorder for FSX Version 2.18 alpha (Built Jun 22 2012)
23.06.2012 16:22:07

Module Entry Point
FSX Version: 10.0.61637.0
DLL functions imported
Callbacks registered
Initialization finished

This is incredibly frustrating as every version I try to download has a problem with my computer for some reason.

Oh and also I still can't record the AI traffic extended controls options or else FSX crashes as soon as I hit record. I have to record the Flaps handle, gear handle, etc. in order for it not to crash on "record."

[mfastx]

Perhaps I can send you the FRC file I am trying to play?

[mfastx]

After doing more testing after turning off Active Sky 2012 I was able to load a recording, but it was full of graphical errors so it wasn't of any use.

[mfastx]

Completely wiped my hard drive and reinstalled FSX + Acceleration (on Windows Professional 64 bit) and the same exact problems are still there with the alpha versions, and I am even having problems with the "stable" version, which is 2.1.

I'm sure there is some setting I need to adjust on my OS or some edit I need to make on my fsx.cfg because there is no way that I can be the only one with this problem. I've followed all of the normal troubleshooting steps and they haven't worked.

The only version I can run without FSX either crashing or freezing upon loading is 1.331 and 1.3. Anything after 2.1 does not work on my system. With version 2.1, I can playback a recording fine, but when I end the recording, FSX freezes when loading at 14%. In 2.16a, textuers load just fine unless I am rendering. If I am rendering, ground textures do not load. They do load during normal playback. However I still experience crashes when loading FSX after playback is finished.

In 2.17 and 2.18, I cannot playback a file because FSX hangs on the initial load. And I cannot check too many boxes on the AI traffic recording settings, or else FSX simply crashes when I hit "record." I cannot record anything but the most basic AI traffic functions, like control inputs, flap handle, etc.

I am really dissapointed that my computer will not handle the newer versions of FS Recorder, and I will gladly test slightly modified files and such to get it working on my system.

If I can solve this problem I will gladly become a donor of this great product.

[mfastx]

Sorry for completely bombarding this thread with posts, but I have done some tests and I think that version 2.18 works fine as long as I do not record/playback the Date and Time option. I think that is what's messing up my sim is trying to playback the date/time.

So I guess that would be something you could focus on fixing and/or trying to recreate that problem.

[noisy]

Hi,

I was about to ask you if you have date/time playback enabled. Good to know that this is part of the problems, I'll look into that soon. Does playback of date/time work in version 2.1, and if so, do you still get the crash after playback ends when you turn it off?

Regarding AI traffic recording options, could you try to test them one by one (only enable one option at a time), to identify the problematic ones? Do you have AI add-ons installed?

I currently have no idea about the cause of the texture problem during rendering. Does it occur in 2.17 and 2.18 as well?

[mfastx]

Hi,

I was about to ask you if you have date/time playback enabled. Good to know that this is part of the problems, I'll look into that soon. Does playback of date/time work in version 2.1, and if so, do you still get the crash after playback ends when you turn it off?

Regarding AI traffic recording options, could you try to test them one by one (only enable one option at a time), to identify the problematic ones? Do you have AI add-ons installed?

I currently have no idea about the cause of the texture problem during rendering. Does it occur in 2.17 and 2.18 as well?

In version 2.1, I believe the problem is the date/time playback as I have been using that the whole time when testing. This is the confusing part: sometimes I get the "crash" (it's not really a crash, it's just that FSX hangs on initial loading on playback, it gets stuck at a certain percentage) when I start playback, and sometimes I get the crash when I finish playback and return to standard simulation.

But it is definitely the date/time that is causing the loading problems in versions 2.1 and above.

In version 2.18, I do not have the texture loading problem strangely enough. So that is no longer an issue for me. I'm guessing that you modified the rendering code a bit for 2.18 and that seems to have fixed the problem.

As for AI traffic, I do have MyTraffic X 5.4 installed, that could be causing the problem. However I have noticed that whenever I check the boxes related to "extended controls" (control surfaces, flap/gear position, engine parameters, etc.) then the crash occurs. I will do some more testing to try to determine which specific option(s) cause the crash when I have time.

As these extended controls options aren't very important to me regarding AI traffic (I mainly just want to use them to record the user aircraft), I am perfectly fine with leaving these options unchecked.

[spokes2112]

Matthias,

1st off, I would like to give you a gracious "Thank You" ! ( Been a user since the FS9 beta's in 2004 ) Anyhow, there seems & 'confirmed' a [smoke] system that can run up to 99 individual controlled effects.. The logic is rather "wacky" though..

I am glad that in version 2.18a that there is now a way to include indexes but I may have found something that I hope can be implemented. I think the built in smoke monitoring facilities may interfere w/ what I would like to accomplish. If I use the "I" key (smoke toggle) while the built in smoke facilities are on I believe the module is recording (smoke toggle) as the command wich will turn on all smokes until the built in logic of the panel controls whats should be on/off. If I use my custom var entry in the .INI none of the smoke seems to get recorded. The water rudder works fine.

[CUSTOMVAR.001]
VarName=FSX:SMOKE ENABLE
Units=bool
UIGroup=SHRS F-111
Indexed=23
Interpolate=0
[CUSTOMVAR.002]
VarName=FSX:WATER RUDDER HANDLE POSITION
Units=Percentage
UIGroup=SHRS F-111
DataType=float
Interpolate=0


FSX ONLY
Ref - http://www.fsdeveloper.com/forum/showth ... t=SMOKE_ON

In a simple set of terms the following is an excerpt from the aircraft.cfg I am working with..

[SMOKESYSTEM]

// smoke.0 - cannot be assigned as the smoke command above .1 count will NOT work
// smoke.1 = at least 1 variable is available to monitor via (A:SMOKE ENABLE, bool) <-- Only smoke.0 & smoke.1 are monitored without an index.

smoke.1 = 0.00, 0.00, 0.00, fx_navwhi // DUMMY FX.... DO NOT USE THIS ASSIGNMENT !!
smoke.2 = -26, -2.60, 0.0, SHRS_F-111_BURN_PT.fx
smoke.3 = -26, 2.60, 0.0, SHRS_F-111_BURN_STB.fx
smoke.4 = -11, -2.60, 0.2, SHRS_F-111_STG2.fx
smoke.5 = -11, 2.60, 0.15, SHRS_F-111_STG2.fx
smoke.6 = -14, -2.52, 0.58, SHRS_F-111_STG3.fx
smoke.7 = -14, 2.52, 0.58, SHRS_F-111_STG3.fx
smoke.8 = -50.00, 0.00, 0.0, SHRS_F-111_DUMP.fx
smoke.9 = 24.00, 0, 1.58, SHRS_F-111_VCW_1.fx
smoke.10 = 24.00, 0, 1.58, SHRS_F-111_VCW_2.fx
smoke.11 = 24.00, 0, 1.58, SHRS_F-111_VCW_3.fx
smoke.12 = 24.00, 0, 1.58, SHRS_F-111_VCW_4.fx
// this continues to smoke.22

Commands & Reads Ex..
13 (&gt;K:SMOKE_ON) 13 (&gt;K:SMOKE_OFF) (A:SMOKE ENABLE:13, bool)
22 (&gt;K:SMOKE_ON) 22 (&gt;K:SMOKE_OFF) (A:SMOKE ENABLE:22, bool)
4 (&gt;K:SMOKE_ON) 4 (&gt;K:SMOKE_OFF) (A:SMOKE ENABLE:4, bool)
Etc...


Thank You very much,
Regards,
Roman

[noisy]

In version 2.1, I believe the problem is the date/time playback as I have been using that the whole time when testing. This is the confusing part: sometimes I get the "crash" (it's not really a crash, it's just that FSX hangs on initial loading on playback, it gets stuck at a certain percentage) when I start playback, and sometimes I get the crash when I finish playback and return to standard simulation.

But it is definitely the date/time that is causing the loading problems in versions 2.1 and above.

OK, so I'll look into date/time playback, hope I can fix it.

In version 2.18, I do not have the texture loading problem strangely enough. So that is no longer an issue for me. I'm guessing that you modified the rendering code a bit for 2.18 and that seems to have fixed the problem.

Yes, in version 2.17 I made changes and added options to improve scenery loading.

As for AI traffic, I do have MyTraffic X 5.4 installed, that could be causing the problem. However I have noticed that whenever I check the boxes related to "extended controls" (control surfaces, flap/gear position, engine parameters, etc.) then the crash occurs.

Maybe the problem occurs only with specific AI aircraft models, as I can't reproduce it here (with only default FSX traffic).

I will do some more testing to try to determine which specific option(s) cause the crash when I have time.

That would be helpful.