Run-time error 9 : Subscript out of range

[Jim Supersym]

Hi, when I launch G-Step (from flight illusion) to run my FFB yoke, I get this error message : Run-time error 9 : Subscript out of range with FSUIPC 7.5, in MSFS 2024.

But it's running without error with the 7.48...

An idea ?

thanks 

[John Dowson]

1 hour ago, Jim Supersym said:

Hi, when I launch G-Step (from flight illusion) to run my FFB yoke, I get this error message : Run-time error 9 : Subscript out of range with FSUIPC 7.5, in MSFS 2024.

But it's running without error with the 7.48...

An idea ?

No, no idea - have you tried support from G-Step?

There is a change in 7.5.0 that could affect 3rd party software. If such software is reading the FS version at offset 0x3308, then this offset is no longer populated until FSUIPC has connected to the FS, whereas in previous versions this offset was initialised to 13 (the value for MSFS2020). There is a new version available that has a fix for this, available in this post: 

John

 

[Jim Supersym]

Sorry, but no change...

 

[Jim Supersym]

curiously,it's seems working if I launch FSUIPC in mode administrator 

[John Dowson]

12 minutes ago, Jim Supersym said:

curiously,it's seems working if I launch FSUIPC in mode administrator 

Then the G-Step software must be running as admin. All client applications must run at the same privilege level as FSUIPC.  

[Jim Supersym]

Ok, thanks.

[Jim Supersym]

in fact does'nt work...

[John Dowson]

Are you using the 7.5.1a version, and did you add
    Init3308=13
to the [General] section of your FSUIPC7.ini file?

But if its the G-Step software that isn't working, you should contact their support. I cannot help with that.

John

[Jim Supersym]

I can ask them, but they don't support anymore this yoke and this software. But I asked you firts because it's running normaly with the 7.48 and not with the 7.5.

If there is no solution I will remain with the 7.48. 

By the way, in this case, is that possible to shunt the window saying  that a new version of FSUIPC is avalaible ?

[John Dowson]

6 minutes ago, Jim Supersym said:

it's running normaly with the 7.48 and not with the 7.5.

Presume you mean 7.4.18... id you show me the logs from both versions I can take a quick look to see if there are any issues.
But if you want me to help you, you have to answer my questions:

31 minutes ago, John Dowson said:

Are you using the 7.5.1a version, and did you add
    Init3308=13
to the [General] section of your FSUIPC7.ini file?

?

8 minutes ago, Jim Supersym said:

By the way, in this case, is that possible to shunt the window saying  that a new version of FSUIPC is avalaible ?

If you do not want notification when a new version is available, you can set:
    OpenOnStart=Never
See the Advanced User guide for details.

John 
 

[Jim Supersym]

2 minutes ago, John Dowson said:

Presume you mean 7.4.18... id you show me the logs from both versions I can take a quick look to see if there are any issues.
But if you want me to help you, you have to answer my questions:

?

If you do not want notification when a new version is available, you can set:
    OpenOnStart=Never
See the Advanced User guide for details.

John 
 

yes I mean 7.4.18, sorry. I always do the mistake !

And yes I tried to run the fsuipc.exe attached in the topic you show me, after adding Init3308=13. and also Init3308=14 to try.

My answer "Sorry, but no change..." was not clear enough.

[Jim Supersym]

And I will sent the 2 log  files this evening, for me, in France 😀 (I'm at work at this moment).

 

[John Dowson]

Is it working when running as admin or not?  You said it was but later 'in fact doesn't work...' - why did you think it was initially working?

There are no changes from 7.4.18 that should affect add-ons really, except for the change in offset 0x3308 which is what that latest beta version is addressing.
Can you activate logging for IPC Reads and IPC Writes and show me the FSUIPC7.log file from both versions and I will take a look. Try and keep the logs as short as possible, i.e. start your software and when it fails or connects, exit FSUIPC7 and attach the logs here. Also any log files from the G-Step software showing the error may be useful.

1 minute ago, Jim Supersym said:

And I will sent the 2 log  files this evening, for me, in France 😀 (I'm at work at this moment).

Ok.

John

[Jim Supersym]

I tried fist on my Laptop at work, and it was working in adminsitrator mode for fsuipc, not in normal mode. 

But for my pc of game, it isn't working neither in administrator mode or not, for fsuipc and/or GSTEP.

[John Dowson]

17 minutes ago, Jim Supersym said:

I tried fist on my Laptop at work, and it was working in adminsitrator mode for fsuipc, not in normal mode. 

But for my pc of game, it isn't working neither in administrator mode or not, for fsuipc and/or GSTEP.

If its working on one PC but not on another, then I would have thought that this implies there is some difference between the PCs that needs to be looked at, not with the software itself...

[Jim Supersym]

of course all the PC in the world are not the same ! 

[Jim Supersym]

HI the answer from Flight Illusion :

 

 

Hi,

The Force Feedback Yoke is a long time out of our delivery program and a long time no longer supoorted.

I can't tell you what to do, i am sorry.

Best regards,

Flight Illusion B.V.

Matthijs Thijssen

 

 

At 2k euros the piece this kind of answer is very disappointing !

Next time I will go at Brunner !

[John Dowson]

1 hour ago, Jim Supersym said:

I can't tell you what to do, i am sorry.

I don't expect you to tell me what to do!
I need to see your log files....and also attach your FSUIPC7.ini file.

[Jim Supersym]

no ! 

it was the answer form Flight illusion 

[John Dowson]

5 minutes ago, Jim Supersym said:

no ! 

it was the answer form Flight illusion 

Ah, sorry...misread that!

[Jim Supersym]

No worries

[Jim Supersym]

Hi !

 

here are the 3 files 

 

7418 : ok

75ok (zip because too big) : no errors, I launched MSFS2024  just after installing FSUIPC 7.5; I launch GSTEP and no error  and I quit FSUIPC

75 failed : I launch FSUIPC  a second time and error when I launch GSTEP

 

 

 

FSUIPC75failed.log FSUIPC7418.log FSUIPC75ok.zip

[John Dowson]

20 hours ago, Jim Supersym said:

7418 : ok

But the 7418 log shows that FSUIPC7 hadn't even connected to MSFS before it exited....

20 hours ago, Jim Supersym said:

75ok (zip because too big) : no errors, I launched MSFS2024  just after installing FSUIPC 7.5; I launch GSTEP and no error  and I quit FSUIPC

So it is working ok in 7.5.0? Was this with the Init3308 ini parameter added? I don't think so as you are using 7.5.0 - please try with the 7.5.1a version and use that - this ini parameter won't do anythung in 7.5.0, so you need to use the later version...

20 hours ago, Jim Supersym said:

75 failed : I launch FSUIPC  a second time and error when I launch GSTEP

This log file shows that when it is failing, the software is reading 0E (14) from 0x3308:

Quote

    23906  READ0[5216]  3304,   4 bytes: 00 00 00 75                                      ...u
    23906  READ0[5216]  3308,   4 bytes: 0E 00 DE FA                                      ....
    23906 WRITE0[5216]  330A,   2 bytes: 00 00                                            ..

The value 14 signifies MSFS20245. From the 750k version it is reading 0 (i.e. not yet populated):

Quote

   155906  READ0[28004]  3304,   4 bytes: 00 00 00 75                                      ...u
   155906  READ0[28004]  3308,   4 bytes: 00 00 DE FA                                      ....
   155906 WRITE0[28004]  330A,   2 bytes: 00 00                                            ..

So it looks like it is the new value of 14 in offset 0x3308 that is causing this 'subscript out of range' issue.
Really, the software needs updating to recognize this new number for MSFS2024. Failing that, you will have to manually set/change this number to 13 when set to 14.
This offset is set as soon as FSUIPC establishes a connection to MSFS. So what you need to do is to change this value to 13 once 14 is written to that offset.
It is not possible to update offset 0x3308 in the current version, so please try the attached version below, 7.5.1b, where it is possible to update this offset. To do this, create a lua script called ipcInit.lua and add the following:

ipc.writeUW(0x3308, 13)

If you do this, 14 will be written to offset 0x3308 when FSUIPC connects to MSFS2024, then the lua script will run automatically and change this value to 13. If the GSTEP software is started after the value has changed to 13, you should be ok.

John

FSUIPC7.exe 

[John Dowson]

Your log files also show an issue with one of your lua scripts that needs investigating:

Quote

   160250 LUA.2: Crash C0000094 at 7FF690CC43B7: "G:\FSUIPC7\HIDMulti.lua"

John

[Jim Supersym]

Hi thanks a lot for your help !

Seems to work !

I've deleted the HIDMulti.lua, because I hav'nt the multipanel, only the switch and the radio.*

one more things  : 

I'm unable to use the virtual joystick's buttom. The Flight Illusion joystick (GSTEP) use the virtual device "64" to assign buttom I use for the trim.  But I can't attrib them in FSUICP. 

Could you help me ?

Thanks again