Flight Freeze function

[CATIII]

Dear Pete,

I experience the following behaviour when writing a non-zero byte-value to offset 3541 (using FSInterrogate):

The first flight freeze works perfectly. After releasing the aircraft (writing 0) it continues flying. But when I write a non-zero value to 3541 again, the aircraft is put back to the exact position of the first(!) flight freeze. I can do the same game over and over - the aircraft always returns to the first position.

Am I doing something wrong or did I miss something? Thanks for enlighting me...

Bye,

CATIII

PS: Just to let you know: the new versions 3.45 and 6.45 work perfectly in our environment. Former versions had trouble when the data queue built up and crashed. Thank you for that! Our simulator is really stable now.

[Pete Dowson]

The first flight freeze works perfectly. After releasing the aircraft (writing 0) it continues flying. But when I write a non-zero value to 3541 again, the aircraft is put back to the exact position of the first(!) flight freeze. I can do the same game over and over - the aircraft always returns to the first position.

Good catch! The flag indicating whether the flight is already frozen or not (to avoid re-reading the position) isn't cleared in the correct place. it works fine using the added FSUIPC controls, but not the offset itself.

Sorry. It will be fixed in the next release. I will be posting an interim test update here soon, hopefully by the middle of the week.

Just to let you know: the new versions 3.45 and 6.45 work perfectly in our environment. Former versions had trouble when the data queue built up and crashed. Thank you for that! Our simulator is really stable now.

Good. Please try the interim WideFS update I shall be releasing mid-week (here too). The main change is that I've stopped using Windows timers for all the timings and I'm using my own timing thread now. This seems to tighten everything up a little, giving better responses. I suspect the Windows timer messages were bunching up on occasion. They are treated at very low priority by Windows. Also I think Windows merges multiple timer messages in the queue, so timings go atray as well at busy times.

Regards,

Pete