SCS Tupolev Tu-134 & FSUIPC for FS9

[avsim]

 After reassigning some keys in FS9 or FSUIPC the elevator trim stops reacting to key inputs the next time the flight simulator is loaded as well as some sounds disappear - switches etc.

Overwriting backupped fs9.CFG and FSUIPC.ini, as well as Previous flight.FLT and Previous flight.WX helps to get it alive.

Maybe there's just a simple solution to the problem. Any help would be greatly appreciated!

 

[Pete Dowson]

10 hours ago, avsim said:

After reassigning some keys in FS9 or FSUIPC the elevator trim stops reacting to key inputs the next time the flight simulator is loaded as well as some sounds disappear - switches etc.

Overwriting backupped fs9.CFG and FSUIPC.ini, as well as Previous flight.FLT and Previous flight.WX helps to get it alive.

Just reassigning some keys won't make such differences. Sounds like your device IDs got messed up.

10 hours ago, avsim said:

Maybe there's just a simple solution to the problem.

You appear to have just stated that you solved it.

Pete

 

[avsim]

2 hours ago, Pete Dowson said:

Just reassigning some keys won't make such differences. Sounds like your device IDs got messed up. 

Any idea where to look at?
 

2 hours ago, Pete Dowson said:

You appear to have just stated that you solved it. 

Nope. Unable to change anything. Works only with old backup. And the problem is only with SCS Tupolev Tu-134.

[Pete Dowson]

24 minutes ago, avsim said:

Any idea where to look at?

Well ALL your FSUIPC settings are in the FSUIPC INI file, in the Modules folder.

25 minutes ago, avsim said:

Nope. Unable to change anything. Works only with old backup. And the problem is only with SCS Tupolev Tu-134.

So, which of those things you restored -- FS9,CFG, FSUIPC.INI  -- does the trick?

It does sound like a corrupt FS9.CFG file. FSUIPC doesn't care which aircraft. Or maybe you need to uninstall and reinstall the aircraft?

You can show me your FSUIPC INI file and I can see if anything is wrong, or at least, odd.

Pete

 

[avsim]

Pete. thanks for your prompt reply!

Looks like it's solved now. It was a registry problem. Somehow one of the installed addons changed the FS9 path in the registry. I changed it back and now it works perfectly.