my FSUIPC doesn't correctly restore my Key press programming

[MichaelDay]

Hi Peter

This FSUIPC utility is great, but some strange reason it isn't properly maintaining my Key press programming assignments between simulation sessions. I can go in and make some key press programming assignments, and it will work OK during that session, but when I use it again after I've exited FS9, the key press programming doesn't work.

Going into FSUIPC the 2nd time you can review all the key press selections that are missing the control + parameter assignments.

To debug this problem I looked at the fsuipc.ini file and noticed that after I assign some key press programming it would have entries like:

[Keys]

0=40,8,,65913,0

then after exiting the FS9 session and looking at the fsuipc.ini file it would now have juggled the order of the key press program values like:

[Keys]

0=40,8,,0,65913

Why would it be doing this?

Help !! Please

Cheers!

Mike Day

[Pete Dowson]

This FSUIPC utility is great, but some strange reason it isn't properly maintaining my Key press programming assignments between simulation sessions.

Yes, sorry. I discovered this two days ago and I am fixing it now. It only applies since 3.14, but it is annoying.

The only way around it at present is to correct the INI file BEFORE re-loading FS, after any Key re-programming.

[Keys]

0=40,8,,65913,0

then after exiting the FS9 session and looking at the fsuipc.ini file it would now have juggled the order of the key press program values like:

[Keys]

0=40,8,,0,65913

The error in 3.14 is the inclusion of the extra comma. If that is removed BEFORE reloading FS then all is well. However, if you don't, then edit the keys again, the lines are made even worse, and so on ...

The reason for this is that FSUIPC is reading:

,,65913,0

as

,0,65913

(the omission of a number looks the same as a 0). So when it gets written back it LOOKs like it has the control and parameter reversed. In fact it is not the parameter 0, but another 0.

If you want a fix urgently then email me at petedowson@btconnect.com and I will send you the fixed interim version (it is a little too big to upload here). Otherwise it will be fixed in the next release, probably middle or end of next week (there are some other things to test and document too).

Apologies for the inconvenience!

Regards,

Pete