I modified the .ini file to:

Code: Select all

[CUSTOMVAR.001]
VarName=FSX:Rotation Velocity Body X
Units=degree per second
UIGroup=Rotation Velocity

[CUSTOMVAR.002]
VarName=FSX:Rotation Velocity Body Y
Units=degree per second
UIGroup=Rotation Velocity

[CUSTOMVAR.003]
VarName=FSX:Rotation Velocity Body Z
Units=degree per second
UIGroup=Rotation Velocity

[RECORDING]
Interval=312
IntervalAI=20000
IntervalCamera=312
RecordUser=1
RecordAI=0
RecordCamera=0
RecordPlayingTraffic=0
SaveFlight=1
ContFlags=61459
ContFlagsAI=19
DiscFlags=31
DiscFlagsAI=23
CustFlags=1
CustFlagsAI=0
AutoStopMode=0
AutoStopTime=10
[Dialogs]
FrcPath=J:\My Documents\FS Recorder Flights

I was able to select the Rotation Velocity group in FS Recorder and successfully record a flight. However, my SimConnect client application does not show data for these variables during playback. What am I doing wrong?

Hi
When is the next update is coming?

Hi Mathias

A succesful 2013 to you and your loved ones.

I've just discovered this. On both my desktop and my laptop, with 2.181alpha, when I select and use a mission, I get a crash to dekstop. I don't use the missions much and I was demonstrating them to a friend when this happened on my laptop, a two year old Compaq - Windows 7 Pro 64bit, Intel Mobile Core 2 Solo 2.2GHZ, 6GB DDR2 and Mobile Intel 4 series graphics. I can use FSX for all other flying, and can go through the missions right up to the point of loading it. The scroll bar completes to 100% and as the kneeboard for the mission (only the frame, no content) appears, there is a black screen, and a message pops up that FSX has failed and is looking for a solution. Closing this crashes FSX to dekstop.

This is likewise on my dekstop when I tested this too, after seeing it happen on my laptop - Windows 7 Ultimate 64bit, Intel Core 2 Duo 3GHZ, 6GB DDR3, ATI Radeon HD 5770. As I said I can use FSX for all other functions and have had no other issues with FSRecorder, just the above. If I uninstall this version from both computers the missions work fine. I have not yet tried a beta or the official release version yet to see if it is only an issue with the Alpha version. I will be doing that in the next day or so, and will come back with my test results.

Regards

Hi Matthias,

today I hit on a weird problem in combination with my software CumulusX!. At airport Wanaka in New Zealand, at a particular time, disconnecting my software from the SimConnect interface lets FSX hang with FSRECORDER 2.181. The problem apparently only occurs at that particular airport, and only with the alpha release. Version 2.1 is not affected.
I tried a couple of things to isolate the problem (deactivating add-on scenery, choosing other aircraft, deactivating other add-on DLLs), but the problem is definitely related to the alpha in combination with a "Close Simconnect" message from my software.
AI traffic was not active.
I can send you a saved FLT-file as reference.

best regards,
Peter

Update: AI ships

This might be a specialty of Holger Sandmanns BC Victoria scenery, as I just discovered that a couple of AI ships and boats appear even in the "Airtraffic" list view of FSX itself.
FSR hooks only to those, but not to the much larger number of the well-known water traffic items.

best regards,
Peter

Hi Matthias,

I didn't do any specific FSR testing in the meantime, but had 2.181 doing instant recording in the background as usual. No crashes anymore so far. Camera switching leaves out my helper and cloud objects now and hooks to to AI aircraft but also to AI ships (but no road traffic).

best regards,
Peter

OK, the update for the FSX version is here: http://www.fs-recorder.net/download/dow ... sxrec2181a

mfastx wrote:Noisy, thanks so much. I will see how it works when you upload the fix.

OK.

The other problem (crash when enabling recording of extended data for AI traffic) seems to be related to what Funky discovered, that the latest alpha versions also record some other object types (like ground vehicles), which they shouldn't do. I'm already working on that, so that should be fixed as well in the next release.

Funky,

you're right, I just checked that and can confirm your observation. When I enabled airport ground traffic (which I have usually disabled) it was recorded as well, which should not happen. As I removed all SimConnect dependencies in version 2.17a, I now have to use a hack to get a list of all AI aircraft. Obviously that hack returns also other AI objects than aircraft, I have to find a fix for that.

Update to my prevvious post:

There seems to be a problem with the generation of clouds and helper objects of my CumulusX! software. I gave 2.18a another try in Instant Recording, everything enabled on the user aircraft, except date&time. On AI evertying enabled up and including Smoke Effects and then Main Exit and Airspeed. Record AI was flagged in Instant Recording (usually for the tow plane).
When I started my CumulusX! software, while FSR was in Instant Recording, FSX immediately crashed.
I think there might be something in recording this type of objects, which are "Simple Objects" wich confuses FSX or FSR, e.g. by not providing requested data. Simple Objects do not respond to most aircraft data request and have only a very limited subset (e.g. position, altitude, speed, orientation), but no engine or flight instrumentation data.

best regards,
Peter