This are the (new) 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, and are still available (until the end of the year) for read-only here.

At the moment these new forums are quite empty – I will be updating the FAQ section and copying across the User Contributions from the old forums in the next few months.

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

[Solved] After windows 11 upgrade I lost interaction between FSUIPC and my SIOC scripts

Page 1 / 3 Next

Posts: 5

fllightlevel8

Registered

Topic starter

November 25, 2025 3:18 am

(@fllightlevel8)

Joined: 2 months ago

Hi, i was in windows 10 with ms2020. I used Opencockpit SIOC script to drive many buttons in my cockpit. (Var 0002, name FO_JoyStick64, Link FSUIPC_OUT, Offset $3340, Length 4) etc…. every thing worked fine.

I upgraded to windows 11. After this i lost all my buttons in my cockpit.

When I access the front panel in FSUIPC it is written

Welcome to FSUIPC7, version 7.5.5
Using the General assignments only (no aircraft-specific profile currently in use)

SIOC seems to work ok. I can go in SIOC monitor and i can interact with all button and I can light all my lights.

If I go in FSUIPC assignments buttons & switches when i push any button to configure FSUIPC show nothing…

Nothing works in my cockpit. I spent many hours to understand what’s wrong…. without success…

Any idea ?

Attachment : InstallFSUIPC7.log

Attachment : FSUIPC7.log

11 Replies

Posts: 173

FSUIPC Support

Moderator

November 25, 2025 10:23 am

(@fsuipc-support)

Joined: 3 months ago

The log file you attached ends after half a second and shows that FSUIPC7 was still running (and was manually started). Please show me a full log file showing your issue, with logging for Buttons & Keys activated, and always exit FSUIPC7 before attaching files. Please also show me / attach your FSUIPC7.ini file.

Posts: 173

FSUIPC Support

Moderator

November 25, 2025 12:26 pm

(@fsuipc-support)

Joined: 3 months ago

Posted by: @fllightlevel8
↑
If I go in FSUIPC assignments buttons & switches when i push any button to configure FSUIPC show nothing…

Do you mean the button isn’t registered, or that the assignment to the button is missing? I expect it is the latter, and this is due to your devices GUIDs changing due to the Windows update. If this is the case, it canbe fixed with a simple edit of your FSUIPC7.ini file, by replacing the GUIDs of the original letters assigned with the new GUIDs and removing the new letter entries generated with these GUIDs. If you attach your FSUIPC7.ini, I can also do this for you.

John

Posts: 5

fllightlevel8

Registered

Topic starter

November 25, 2025 2:59 pm

(@fllightlevel8)

Joined: 2 months ago

Hi John,

Here the new log file and prtscreen…

Attachment : FSUIPC7.ini

Attachment : FSUIPC7.log

Thank you

JP Tremblay

Montreal, QC

Attachment : Capture d’écran (3).png

Attachment : Capture d’écran (2).png

Attachment : Capture d’écran (1).png

For example, when I try to push the button for release autopilot in this panel, I cans see nothing…

Posts: 173

FSUIPC Support

Moderator

November 25, 2025 3:22 pm

(@fsuipc-support)

Joined: 3 months ago

There don’t seem to be any issues in your log or ini. FSUIPC recognises the following 3 devices:
– 4-axis,4button joystick (A)
– IOCa (B)
– USBAXEPLUS V3 (C)

Are you sating that button presses on these devices are not recognised? What about axes (you have axes assigned to each of these devices)?
If button presses are not being recognised on these devices, then I think you must have a windows (or driver) issue. Can you see these devices in the windows Game Controllers?

Almost all of your button assignments are assigned to device ’64’. Do you know what device this is? e.g. is it a GoFlight, PFC, VTInsight device or something else? If it is this device that you cannot see, you probably need to install an additonal driver/dll, such as the ones we provide for GoFlight and PFC.

This post was modified 2 months ago by FSUIPC Support

Page 1 / 3 Next