FSUPIC Not Recognizing Joystick & Throttle Buttons

[Yoda967]

I'm running Win10, FSX:SE, a registered copy of FSUIPC 4.966c, and a Saitek X55 stick & throttle combo. I've followed the registry change procedure in the FAQs, which helped get my throttle axes working properly, but when I attempt to enter any buttons in the "Buttons & Keys", FSUPIC doesn't recognize the joystick or throttle unit button presses.

I am seeing the buttons for both in the Windows Calibrate window, and I can assign buttons to various functions within the FSX Controls GUI, so I know that FSX is seeing them. 

Anyone got an idea what might be causing this?

 

Best Regards,

Kurt

Edited April 22, 2017 by Yoda967

[Pete Dowson]

1 hour ago, Yoda967 said:

I've followed the registry change procedure in the FAQs

Sorry, what are they? Are you referring to some action documented in case of problem, relating to Joystick IDs, which actually isn't needed now and involved a program called JoyIDs? Or do you mean the resistry fixes to the bad install Saitek does? Have they not even fixed that yet?

1 hour ago, Yoda967 said:

... which helped get my throttle axes working properly, but when I attempt to enter any buttons in the "Buttons & Keys", FSUPIC doesn't recognize the joystick or throttle unit button presses.

That is extremely strange, because both axis values and buttons are read at the same time, in the same actual operation. They are indivisible.

You are now the third person here with outstanding X-55 problems, and all three of you have different problems but ALL with the X-55 (and all on Win10 which may also be relevant). One has neither stick nor throttle seen, another has stick but no throttle inputs, and now you with axes okay but no buttons.

The X-55 is a nightmare.

Can you please refer to the other two threads and supply the same data, so I can compare it? They are by "OldPop" and 2Kegs1953". Best go to the last few exchanges or you'll get very confused. it even confuses me.

I'm going to try to get someone with a working X-55 set to supply similar data for a comparison with what it should look like.

Pete

 

 

 

[Yoda967]

Thanks for the prompt reply, Pete. 

Here's the log.

Before posting, I went through both of the threads you recommended, hoping to find something I could use without having to ask. Sadly, I agree with you -- the X55 is turning out to be a nightmare.

 

Best Regards,

Kurt

 

FSUIPC4.zip

Edited April 22, 2017 by Yoda967

[Pete Dowson]

The log shows some axis activity, though by the look of it from "zero2 being received from the units. Was that with the X55 units, and they are returning just zeroes, as in the case of Kegs1953?

    22360 ***  AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET
    22360 ***  AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
    22360 ***  AXIS: Cntrl= 66387 (0x00010353), Param= -8736 (0xffffdde0) AXIS_LEFT_BRAKE_SET
    22360 ***  AXIS: Cntrl= 66388 (0x00010354), Param= -8840 (0xffffdd78) AXIS_RIGHT_BRAKE_SET
    22360 ***  AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET
    22547 C:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\VRS_FA-18E\FA-18E-6.8_SE.air
    22547 Weather Mode now = Global
    22547 c:\users\kurt\documents\flight simulator x files\FA-18E at Miramar.FLT
    24485 ***  AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET
    24485 ***  AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET
    24485 ***  AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET
    26125 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    26203 User Aircraft ID 1 supplied, now being used
    26266 Aircraft loaded: running normally now ...
    26344 ***  AXIS: Cntrl= 66420 (0x00010374), Param= -16384 (0xffffc000) AXIS_THROTTLE1_SET
    26344 ***  AXIS: Cntrl= 66423 (0x00010377), Param= -16384 (0xffffc000) AXIS_THROTTLE2_SET

 

[Pete Dowson]

I have a Lua plug-in to try. this is just to give me some information. I'm considering offering an alternative more for reading such devices, but if the alternative gives the same then I'm likely to point to faulty harware, or firmware unsuited to use with Win10.

I read some of the reviews of the X56, the new one replacing the X-55, and that was apparently released with old firmware. Maybe X-55 users need to see if they are up to date?

Anyway, here's the Lua plug-in. I have no idea if it will do exactly what I want it to do, but I'll be able to tell from the FSUIPC log. Please remove those extra logging lines in the INI and turn off Axis and Button logging because that will cloud the issue. Then place this Lua in the Modules folder, run the sim, then in the Keypress tab, assign an otherwise un-needed keypress (or combo) to "Lua Hidx55". Back in flight mode, press the assigned key or combo, and just move the sticks, press the buttons, operate the hats, on both devices. close the sim and sohw me the log.

Thanks.
Pete

 

HidX55.lua

[Yoda967]

Pete,

What I did for the test was to cycle the stick and throttles and then press several buttons on each of them to try to capture a good picture for you. 

I'll try the LUA and get back to you ASAP.

Thanks,

Kurt

Edited April 22, 2017 by Yoda967

[Yoda967]

Pete,

Test complete. I cycled all axes, and pressed each button during this run.

FSUIPC4.log

[Pete Dowson]

12 hours ago, Yoda967 said:

Test complete. I cycled all axes, and pressed each button during this run.

Thanks. Unfortunately the Lua did nothing because it couldn't even open the devices:

   128968 LUA.2: Could not open HID Vendor 0738 Product 2215

I'll make another small modification to it to try again. If it still doesn't work, I'm stumped.

Please replace it and try again. Same method.

 

 

HidX55.lua

[Yoda967]

Pete,

That definitely gave a different result. 

FSUIPC4.log

[Yoda967]

Pete,

All appears to be working now. Thank you! 

[Pete Dowson]

2 hours ago, Yoda967 said:

That definitely gave a different result. 

Well, the Lua I provided is working, but it simply returned the initial values for one of the X55 units (all zeroes) then, a few seconds later you closed the session. did you "Test complete. I cycled all axes, and pressed each button during this run." within the 44 seconds it was running? If so none are logged, they still aren't being seen.

If this is the case, and you definitely did your bit, then there's nothing else I can do -- the Lua is reading the USB data directly, not via DirectInput, but RAW. Something else is wrong with those units.

I notice you are trying to run another Lua plug-in which has an error:

   291125 *** LUA Error: SuperScript_VRS.lua:22: attempt to concatenate global 'ACTIVE_SCRIPT' (a nil value)

1 hour ago, Yoda967 said:

All appears to be working now. Thank you! 

Sorry, what do you mean? Has FSUIPC suddenly and magically recognised and is handling your X-55 units like it does more most (not all) folks? If so what did you change? I need to know to help two or three other folks -- and to relieve me of the work I've been doing to try and find another way, spending more than full time for all of ths last week , including all day today till now! 

(I'm flaking out now ...)

Pete

 

[Yoda967]

Pete,

I did cycle all axes and press all buttons. At that point, I noted that several buttons had assignments that hadn't existed on prior tests. (Following the installation instructions for the VRS FA-18E, I'd deleted all joystick button assignments from the FSX:SE Controls GUI.) I the closed the sim and sent you the log.

After posting that log, I brought the sim back up, and noted that FSUIPC was now recognizing controller buttons, and I was able to assign keys to them per your documentation. If that wasn't a result of the HidX55 LUA, then I don't know what caused it. Apart from that, I haven't done anything outside of following your instructions as closely as I could.

The SuperScript_VRS LUA is from hornetpits.org, intended to help cockpit builders work with all the peripheral things they use. Before contacting you here, I'd seen a recommendation at the VRS forum that SuperScript would simplify the task of assigning buttons...and it didn't work. I hadn't removed it, and probably should have.  

Attached is the log from a full flight I just completed, during which all the mapped buttons appeared to work. 

Assuming you're in the UK, it's got to be getting on towards Sunday evening for you. I've got leave for work soon, but if you'd like me to try anything you might thing will be helpful, I can get to it fairly early in the morning tomorrow, Pacific time.

FSUIPC4.log