These are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
Fsuipc doesn't recognise axis or buttons on joystick
G'day everyone,
I'm having a hell of a time trying to get all my USB devices to play happy. The usual stuff has been done, selective suspension/USB power management turned off.
Windows 10 recognises about half my flight controllers. No problem, p3d v4.5 recognises all and I'm able to assign buttons/axis through there. My preferred option is of course fsuipc, which according to joyscan all devices are there, but in sim fsuipc won't recognise some controllers axis and buttons. Others are fine.
I'd love some help, really tearing my hair out here.
You have registry issues which are causing devices not to be recognised, and it looks as if the GUIDs of your devices have also changed a some point, which is also confusing FSUIPC. You are also not using the JoyLetters facility, which could also be an issue and may make it difficult to correct your current assignments. The very first thing to do is to use JoyLetters, by setting
AutoAssignLetters=Yes
in the [JoyNames] section fo your FSUIPC6.ini file. Do this, run P3D/FSUIPC6 once, then exit.
Then you need to disconnect / unplug all of your devices, except maybe your AGRONN B737 Yoke which looks to be the only device you have correctly registered.
Once you have disconnected your devices, run the windows regedit program and take a backup of your registry.
Then download and run the attach .reg file (by double-clicking it in Windows Explorer) which will remove the registry entries for your devices.
Then reboot and reconnect your devices.
Run P3D/FSUIPC6 and show me your files again, and check if all devices recognised or not. Please do not attach photographs or images unless explicitly asked for.
Which devices are not recognised by Windows? As they are all in your joyscan file, I would have thought that they would also be seenas game controllers.
Thanks for the reply! Done as you instructed this morning after a lot of further troubleshooting last night.
Same issue unfortunately. Windows does not recogniuse (as of present computer power up, I think it changes from time to time) six controllers, PEDALS CAP, Joystick - HOTAS Warthog, Cat3Design Airbus Tiller, Cat3Design Airbus Tiller, Cat3Design Boeing Tiller, Rudder Cockpitturk. These devices fail to appear in the 'usb game controllers' menu but do appear in 'control panel-devices and printers.'
P3d has no probem recognising, reading, and assigning axis/buttons to all 11 devices, and no problem when I swap throttles to another unit. When switched to raw input it only recognises what the windows 'usb game controllers' menu does.
Seems something is very fuddled up in the way winbdows asssigns GUID's that I am guessing leads to a confused joyscan.
Posted by: @xela744Seems something is very fuddled up in the way winbdows asssigns GUID's that I am guessing leads to a confused joyscan.
Yes - it looks like something very strange us going on in your system... this is what the HID scanning reports:
N, x00, x0079, x0006, , -1, -1, 0, {NULL}, {NULL}, {8C0B9BB0-6005-11F1-8001-444553540000}, Y, N
N, x00, x3432, x8032, , -1, -1, 0, {NULL}, {NULL}, {8C0E0CB0-6005-11F1-8002-444553540000}, Y, N
N, x00, x2341, x8036, , -1, -1, 0, {NULL}, {NULL}, {8C0E0CB0-6005-11F1-8003-444553540000}, Y, N
N, x00, x16D0, x0745, , -1, -1, 0, {NULL}, {NULL}, {8C0E0CB0-6005-11F1-8004-444553540000}, Y, N
N, x00, x294B, x1901, , -1, -1, 0, {NULL}, {NULL}, {8C107DB0-6005-11F1-8005-444553540000}, Y, N
N, x00, xFFD8, xF30F, , -1, -1, 0, {NULL}, {NULL}, {F0A72CE0-3FBE-11F1-8001-444553540000}, Y, N
N, x00, x27DC, x16C0, , -1, -1, 0, {NULL}, {NULL}, {8C0B9BB0-6005-11F1-8001-444553540000}, Y, N
N, x00, x27DC, x16C1, , -1, -1, 0, {NULL}, {NULL}, {8C0B9BB0-6005-11F1-8001-444553540000}, Y, N
N, x00, x04D8, x00F0, , -1, -1, 0, {NULL}, {NULL}, {8C0B9BB0-6005-11F1-8001-444553540000}, Y, N
N, x00, x044F, x0402, , -1, -1, 0, {NULL}, {NULL}, {8C0B9BB0-6005-11F1-8001-444553540000}, Y, N
N, x00, x1DD2, x2760, , -1, -1, 0, {NULL}, {NULL}, {8C0B9BB0-6005-11F1-8001-444553540000}, Y, NSix of your devices are being allocated (by windows) the same GUID, and also another 3 with the same but a different GUID.
Posted by: @xela744These devices fail to appear in the 'usb game controllers' menu but do appear in 'control panel-devices and printers.'
This would also indicate a windows issue.
It is also strange that your previous joyscan was a lot better, but still had 3 devices with the same GUIDs:
N, x00, xFFD8, xF30F, , -1, -1, 0, {NULL}, {NULL}, {F0A72CE0-3FBE-11F1-8001-444553540000}, Y, N
N, x00, x27DC, x16C0, , -1, -1, 0, {NULL}, {NULL}, {AF739CF0-38E2-11F1-800A-444553540000}, Y, N
N, x00, x044F, x0402, , -1, -1, 0, {NULL}, {NULL}, {AF760DF0-38E2-11F1-8012-444553540000}, Y, N
N, x00, x0079, x0006, , -1, -1, 0, {NULL}, {NULL}, {2D03C730-38E3-11F1-8002-444553540000}, Y, N
N, x00, x3432, x8032, , -1, -1, 0, {NULL}, {NULL}, {AD55A830-3CC2-11F1-8001-444553540000}, Y, N
N, x00, x1DD2, x2760, , -1, -1, 0, {NULL}, {NULL}, {BABB16F0-956A-11EF-8001-444553540000}, Y, N
N, x00, x04D8, x00F0, , -1, -1, 0, {NULL}, {NULL}, {4E1B5B10-8CCE-11EC-8009-444553540000}, Y, N
N, x00, x27DC, x16C1, , -1, -1, 0, {NULL}, {NULL}, {51A80B20-3CC4-11F1-8001-444553540000}, Y, N
N, x00, x2341, x8036, , -1, -1, 0, {NULL}, {NULL}, {6528B7C0-B799-11ED-8005-444553540000}, Y, N
N, x00, x16D0, x0745, , -1, -1, 0, {NULL}, {NULL}, {F0A72CE0-3FBE-11F1-8001-444553540000}, Y, N
N, x00, x294B, x1901, , -1, -1, 0, {NULL}, {NULL}, {F0A72CE0-3FBE-11F1-8001-444553540000}, Y, NSorry, but I am not sure what to advise - I think you need to look into checking and repairing your windows installation before we can sort out the FSUIPC issues. Also maybe check that any USB hubs are correctly powered, and try to use usb2 ports for usb 2 devices and usb 3 ports for usb 3 devices (where possible). Maybe try switching ports if you have more available.
I will see if I can investigate further tomorrow as to what could cause such issues, but I'm perplexed at the moment...
After quite a lot of faffing about, here's what I've come up with;
First I disabled the restart option in windows. Restarts seemed to cause the USB devices to re-enumerate themselves (poorly).
Next I unplugged, removed in software (using USBDview), found inactive entries and removed them (using some tool I don't recall), used USBOblivion to clean up the registry, and some other tool I don't recall to remove all driver packages that weren't boot critical.
On the physical side of things, I moved most my controllers to a single USB hub (throttles on another because of their location, with all touchscreens /keyboards/mice etc on other hubs), which lead to more controllers being recognised more often and more consistently...but not all controllers...I suspect simultaneous windows recognition of USB hubs caused some enumeration issues.
Then it was a game of whack-a-usb where I'd unplug one, shutdown/boot up, replug and see where it enumerates. Repeat about 15 times and I've finally got them all enumerating consistently (for today) and fsuipc functions normally. The next goal will be to plug a different throttle in and see where it enumerates. I think this will have to be done while the PC is booted up, so the 'new' throttle doesn't get recognised before the current devices and bugger up the enumeration.
On a side note I got awful noise through a few joystick axis through this process. I've had a grounding problem for ages, but after the great USB shuffle it appears to have settled down.
PS at one point in all this fsuipc was reporting USB joysticks as far as the letter Z. Strange that p3d the whole time had no problem recognising and playing well with what was actually plugged in, unlike windows and (as a consequence) fsuipc.
With all my devices connected it still has conflicts, which I seem unable to resolve no matter the amount of usb-jockeying I do. Of course what works and doesn't changes from time to time with windows boot. I've repeated my registry and usb device clearing steps to no consistent avail.
Something is for sure stuck in the registry and refuses to move out, leading to 'usb game controllers' not reporting all devices, fuddling up fsuipc, despite them all being present in 'devices and printers' as well as p3d.
The attached files named old are with every device I use connected to the system at once, trying to foirce a 'good' GIUD assignment.