some buttons not recognised

[Anguisette]

hi there,

i'm using FSUIPC7 (for now, with the "trial" license from the FAQ section) to see if i can make a couple of USB input devices work a bit better with MSFS.  in particular, i'm using a Winwing F/A-18C Combat Panel, which is a USB button box with 56 buttons.

so, i'm trying to add an assignment via "Assignments > Buttons & Switches", but i'm having a problem where FSUIPC won't detect some button presses.  for example, buttons 7, 8 and 9 (a 3-way toggle switch) are detected fine, but buttons 51, 52 and 53 (a rotary encoder with push) aren't detected.  in the Winwing software, i can see that the button presses are being registered, and i can bind these buttons directly in MSFS.

i understand some Windows applications have a limit of 32 buttons for joysticks / game controllers - does this apply to FSUIPC as well?  or is something else going on?

thanks!

[Pete Dowson]

6 hours ago, Anguisette said:

i understand some Windows applications have a limit of 32 buttons for joysticks / game controllers - does this apply to FSUIPC as well?

Yes, it does (and that restriction is documented). Folks needing more use a Lua plug-in to heal with the HID device instead. HidDemo.lua, supplied in the Examples, sends up to the max of 256 buttons for a device using Virutual Button offsets in FSUIPC for easy assignment.

Pete

 

[Anguisette]

thanks Pete.  i was planning to use Lua anyway, but i'd assumed (wrongly, as it turns out) that the same limitation would exist in Lua, which i can now see isn't the case.

i ran into one other issue, which is that the encoders on this device have a fairly short on/off cycle (about 10ms) and event.com() was missing a lot of the inputs.  i fixed that by changing ComReadLoopTime from 20 to 5, but i'm not sure if that's the right fix there?

aside from that, after a bit of fiddling around i've got the controls working a lot better than the MSFS defaults, so i'll be off to buy a license.

[Pete Dowson]

10 hours ago, Anguisette said:

the encoders on this device have a fairly short on/off cycle (about 10ms) and event.com() was missing a lot of the inputs

Strange. Most encoders make a contact (button push) on alternate 'clicks' with the "release" on the intermediate clicks. I wonder how yours pulses instead.  Is it perhaps related to the circuitry? (I assume there aren't 100 clicks every second whilst you are turning it).

10 hours ago, Anguisette said:

i fixed that by changing ComReadLoopTime from 20 to 5, but i'm not sure if that's the right fix there?

If it can go that fast, that's fine. The only damage it may do is cause performance issues because of the increased demand.

Pete