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
FSUIPC6 does not acquire identified joystick device
Hi All,
My cockpit sim runs with P3Dv5, Prosim 3.15, SIOC 6.0B8, and FSUIPC 6.2.2.
All peripheral controllers, such as PoKeys57U Controllers, Bodnar BU0836 Interfaces etc. are correctly started, listed, and calibrated in Windows 11.
The controller of interest is a BU0836X Controller.
When FSUIPC is starting, it does a device scan. All controllers of interest are listed, and among them is "Product= BU0836X Interface", but then it is not acquired for use,
hence I'm not able to define axes and buttons in FSUIPC in the P3D (need to assign SIOC offsets).
(I attached the FSUIPC6.ini, and .log files).
In Prosim all axes and buttons/switches of that controller are fully functional.
This setup has worked for quite a few years now, then I replaced the processor and motherboard, and I'm rebuilding the whole setup "from scratch".
Hope someone can help me and has an idea what I could do to have that controller included!
Regards
Peter
This is probably due to conflicting joystick ids in your registry:
1062 WARNING: Joystick ID 7 is duplicated in Registry 1109 WARNING: Joystick ID 5 is duplicated in Registry
The solution is to disconnect the conflicting device, remove the registry entries, reboot and then reconnect the device.
To remove the registry entries for the BU0836X, download and run (i.e. double-click) the attached .reg file (disconnect it first!). You may also want to run regedit first and take a backup of your registry,
If you have any issues after that, please attach your latest ini and log files, and also your FSUIPC7.JoyScan.csv file.
Unfortunately this didn't help!
Here are the latest ini and log files, the .csv, and the HidScanner.log.
Thank you.
Sorry, there was a typo in that .reg file in the first entry (a missing '&') which means that the required entries weren't removed. Also, now I can see your JoyScan file, the problem is also with the reg entries for your JoyWarrior device, and your virtual joysticks also have conflicting entries (but we'll leave these for now)..
Can you repeat the same process as before, but also disconnect the JoyWarrior device, run the attached .reg file, reboot and then re-attach both devices.
Again, please show me / attach the files again after you have done this - no need for the HidScanner.log file though. It is the JoyScan file that is the important one here, as well as log and ini.
@peterd Is you issue solved?
First of all my apologies for that long "silence". Yes, it is solved, that is, it "solved itself".
I started from the very beginning, i.e. I started the PC with just one HID. But before starting P3D, I started Prosim only, just to verify that it is listed in the device list. Then Prosim off, P3D on, SIOC on, Prosim on, and in FSUIPC I could correctly assign axes or switches etc.
I repeated that same procedure, one after the other, for all 9 HID/PoKeys devices. And all are working like a charm, and BU0836X was always recognized!
I'm happy, and not satisfied at the same time, because I very much like to know, what the cause was for this problem!
I add the newest .log and .ini, and HIDScanner.log anyway, and a photo of my cockpit to give you an idea of what's behind that story.
Thank you so much for your support, I give you 5 * !
Greetings from Switzerland,
Peter