FSUIPC Buttons + Switches accept no keys

[Guido]

Hi

After installing A2A's C182 and assigning via FSUIPC some buttons and keys to GoFlight HW some days later I could not add new key codes to buttons. Even rolling back to the older FSUIPC.ini  file version does not help. All buttons are inactive or blanked (attachment)  independent if specific is tagged or not.

Also changing to other airplanes has no effect.

 

Compared to the FSX.cfg version without C182 the differences are the following lines:

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.rbcratezqkteollihqcneubobuntnccbtbnelcnc=1

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\A2A_Accusim.DLL.ihanbthaiabztoluzunklboizqttkazwciqrlbhh=2

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_C182\panel\C182.DLL.hekhcekicobbeznctihozwrunzwtilhoiqqazlho=2

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_C182\panel\C182_Illumination.DLL.aiqzikzhoanearrwbqerwwarlkanihahzitwkilw=2

C:\Program Files (x86)\GoFlight\GFDevFSX.exe.uzbqceeqtnqokbittcwwtlzrzahhanzkkkqqnhuw=1

 

I wonder what could block FSUIPC to accept new key/button inputs.
Many thanks for the help.

Rgds
Guido

FSUIPCBS.pdf

[Pete Dowson]

After installing A2A's C182 and assigning via FSUIPC some buttons and keys to GoFlight HW some days later I could not add new key codes to buttons. Even rolling back to the older FSUIPC.ini  file version does not help. All buttons are inactive or blanked (attachment)  independent if specific is tagged or not.

Also changing to other airplanes has no effect.

 

...

I wonder what could block FSUIPC to accept new key/button inputs.

 

 

 

I found it very VERY difficult reading your miniscule script, so did not manage all of it, but you mention A2A. Have you seen this thread?

 

http://forum.simflight.com/topic/78888-sudden-lose-of-assignments

 

I think there must be something you've installed, probably with A2A, which is preventing any recognition of buttons using the normal DirectInput functions used by FSUIPC -- and, for that matter, fS itself. Have you checked to see if that detects buttons?

 

Pete

[Gypsy Baron]

FWIW, I have ALL my A2A aircraft configured to use the buttons and switches on my Saitek X-45 and Saitek Pro dual throttle quadrants assigned via FSUIPC4. I have never had an instance where I could not assign FSX controls to buttons or swtiches via FSUIPC4, and I have some SERIOUS assignments (My FSUIPC4.ini file is over 2000 lines long!)

 

The only time I see any options "greyed out" are when I have multiple controls assigned to a button/switch using compound programming via INI file edits. If assignments are 'one on one' I never see geryed out options.

 

Paul

[Guido]

Thanks for feedback and hints. And I am sorry for the miniscule script.

To answer first the question: Yes, I did read the A2A forum topic.

Triggered by Paul’s comment I did the following steps which solved the problem
- Replacing the RealityXP(RXPGNS.ini) with the original empty file
- Deleting the lately added two A2A assignments (via input configurator)
- Starting FSX. Now FSUIPC and FSX accepted key commands
- Shut down FSX
- Entering the same 2 assignments again using the input configurator of A2A
- Renaming the RealityXP ini files to get the former status
- Restarting FSX and things work

Difficult to say what it was but at least I could assign ruder trim to the buttons :) 

 

Again thanks for the help.

Guido