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

Notifications

Clear all

FSUIPC6 does not acquire identified joystick device

PeterD · 2026-03-11T17:00:54Z

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! RegardsPeter

Page 2 / 2 Prev

Posts: 225

FSUIPC Support

Moderator

March 22, 2026 6:12 pm

(@fsuipc-support)

Joined: 5 months ago

Ok. But you still have device issues due to conflicting registry entries, and your ini still shows problems with 2 devices. The first is the JoyWarrior A8-16, which has a new ID. I have corrected this in the attached ini if you can try this. Bu this may also prevent other devices being acquired, so tread carefully. If that happens, follow the advice in my last post.
The second issue is assignemts to device E, which no longer exists. I do not know what this device was, so cannot correct this. You should review your assignments to this device - if you know which one it is, it can be corrected. Otherwise remove/delete the assignments to this device.

Posted by: @peterd
↑
First of all my apologies for that long "silence". Yes, it is solved, that is, it "solved itself".

No problem, was just wondering why this went quiet....!

Posted by: @peterd
↑
Thank you so much for your support, I give you 5 * !

Thanks 😀

Attachment : FSUIPC6.ini

This post was modified 2 weeks ago 2 times by FSUIPC Support

Page 2 / 2 Prev