About 50% of my TMII flights have a strange tendency to revert back to the old behavior of having to use "CTRL+." to release the parking brakes. When this happens I invariably cannot use F6 or F7 (or anything else other than alternate flaps)for flaps, either. I have never found a "common denominator" in these instances but, if I have saved the flight before parking brake release and pushback, and then restart FS9 and reload the flight...it will always be the same. IOW, the "bad behavior" seems to be saved with the flight. The only way to stop this is to reboot, start FS9 and create a new flight identical to the one I originally created. This works about 90% of the time but I have had a few instances when the 2nd created flight exhibited the same behavior and had to try a third time. My TM2 start up procedures do not vary between normal and problematic flights, AFAICT. The annoying part is that, by the time I've hit the "." key to release brakes, I've spent 20 to 30 minutes on the flight already...only to know, immediately, it was a waste of time and I have to start from scratch.

About 50% of my TMII flights have a strange tendency to revert back to the old behavior of having to use "CTRL+." to release the parking brakes. When this happens I invariably cannot use F6 or F7 (or anything else other than alternate flaps)for flaps, either. I have never found a "common denominator" in these instances but, if I have saved the flight before parking brake release and pushback, and then restart FS9 and reload the flight...it will always be the same. IOW, the "bad behavior" seems to be saved with the flight. The only way to stop this is to reboot, start FS9 and create a new flight identical to the one I originally created. This works about 90% of the time but I have had a few instances when the 2nd created flight exhibited the same behavior and had to try a third time. My TM2 start up procedures do not vary between normal and problematic flights, AFAICT. The annoying part is that, by the time I've hit the "." key to release brakes, I've spent 20 to 30 minutes on the flight already...only to know, immediately, it was a waste of time and I have to start from scratch.

This probably means FSUIPC is no longer seeing the programmed hotkeys--the ".", F6, and F7 keys are all hard programmed in the panel via FSUIPC as dedicated hotkeys.You might check to see that your registration for FSUIPC is still valid. Deleting and rebuilding the FSUIPC.ini file may help as well. And as always, make sure your default start-up flight is a default MS multiengine plane...load it first and then switch to the 'mouse.Alternatively, you can program other keys or joystick buttons via FSUIPC to set the appropriate values in offset 6D11 as described in the readme docs, and bypass the hotkey programming entirely.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

This problem is very intermittent, Bob. I just ran into it again today and had not had the issue in many weeks? I can create a flight straight from the TM2 90% of the time...why would it be a problem the other 10%? I'm certainly not arguing your points, my friend...only trying to give info. All things FSUIPC are in order. I'm beginning to wonder if it is ".MDL" related, as in some aircraft using a certain model will cause it? But, either way, I will add the TM2 to the list of aircraft needing to be started with either the default Cessna or, in this case, a multi-engine default. Although this is recommended for any addon, I have had severe problems using it with PMDG, PSS, Level-D and others, so I generally avoid it when I can.I really hate it when problems don't cooperate and show up every time! :( Vic