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

After windows 11 up…
 
Notifications
Clear all

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

Posts: 173
Moderator
(@fsuipc-support)
Joined: 3 months ago

Note you also have a couple of invalid assignments in your ini file:

    7=U64,4,C0,0 -{Custom control: <0>}-
  15=P64,4,C0,0 -{Custom control: <0>}-

Maybe they were assigned to a preset that has either been removed or has changed name. You should correct or remove these assignments.


Reply
Posts: 5
Registered
Topic starter
(@fllightlevel8)
Joined: 2 months ago

I forgot to gave you my sioc script where we can see all the assignments.

 

I can see that all the 3 devices in Windows 11 config with green lights. In joy.cpl when I select IOCA card I can see interactions with axes for my throttles. But no button are active. I think it is normal, because the button I want to use is Virtual Joystick button like it is shown in my sioc script.

Example 

Var 0091, Link IOCARD_SW, Input 58, Type I // desangage autopilot
{
&FO_JoyStick64 = CHANGEBIT 5 ,V0091 // toggle bit 5 of joystick 64 desangage au

All my hardware are my own.  (Potentiometer, button, ect…) No official drivers, only SIOC and FSUIPC

JP


Reply
Posts: 173
Moderator
(@fsuipc-support)
Joined: 3 months ago

Posted by: @fllightlevel8

I forgot to gave you my sioc script where we can see all the assignments.

I don’t use, support or know much about SIOC. I only support FSUIPC.

Posted by: @fllightlevel8

I think it is normal, because the button I want to use is Virtual Joystick button like it is shown in my sioc script.

Ok, so 64 is your virtual joystick, and you are using offset area starting at 0x3340. The first think to check is if that offset is updating. Can you please add offset logging (log->Offsets…) for offset 0x3340 – log as U32 in hex. Then see if anything is logged when you press your virtual button. If nothing is logged, then your SIOC scripts are not updating the offsets and you probably need support from SIOC for this. If the offset is being updated, then it will be an FSUIPC7 issue.

What version of FSUIPC7 were you using before the windows upgrade?

Have you or did you use vJoyOffsets to connect your virtual device to offsets, or is this all done in SIOC?

Later: have you set-up your virtual device correctly? Are you using vJoy for this?

 

 


Reply
Posts: 5
Registered
Topic starter
(@fllightlevel8)
Joined: 2 months ago

Before upgrade to win 11 I used fsuipc 7 but don’t remember exact version…

I don’t know VjoyOffsets I never used this.

Here the log file …..  I dont’ know if this will be ok… when I tried to insert the offset in the field  0x3340 – log as U32 in hex there only 4 digit so I put 3340 U32 Hex

 

 

 


Reply
Posts: 173
Moderator
(@fsuipc-support)
Joined: 3 months ago

Why did you set logging for IPC Reads? This has filled the log with noise and makes it difficult to see anything in the log file. Please only activate the logging requested.

Your log file shows that the virtual button offset (from 0x3340) is not being updated, so no virtual button is triggered. This would indicate an issue with SIOC and the SIOC script that triggers this is not working correctly. Do you have any SIOC logs that show this script is actually being triggered? Or can you add logging to your SIOC scripts?

You could activate logging for IPC Writes to see if a write request for updating these offsets is being received, but as the offset isn’t updated I doubt this, but worth checking.

Posted by: @fllightlevel8

when I tried to insert the offset in the field  0x3340 – log as U32 in hex there only 4 digit so I put 3340 U32 Hex

That is correct. I always specify hex values preceded by ‘0x’, but in offset logging you give the hex number without this.


Reply
1 Reply
Registered
(@fllightlevel8)
Joined: 2 months ago

Posts: 5

@fsuipc-support 

 

Hi John…. sorry little bit late… to busy today….

I tried to adjust lo file….. I checked the log… I can see the result of using axes Flaps and spoilers… but no access to virtual joystick

So now I will investigate on the SIOC side to see if I can find something.

Thank you.

 


Reply
Page 2 / 3