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

FlightIllusion not …
 
Notifications
Clear all

[Solved] FlightIllusion not connecting to FSUIPC/MSFS 2024

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

Posted by: @skythelimit

tried opening FI sw as administrator

Ok, but be aware that if running FI as administrator, you also need to run FSUIPC7 as admin, which you are.

Your log file shows that it is reading offset 3308, as well as 3304 (which is the FSUIPC version number).

I think the issue is probably still the FS version number in 0x3308. Even though you initialise this with the value 13, as soon as FSUIPC7 connects to MSFS2024, this will get updated to 14. So, you need to do one of two things:

  1. start the FI sw before FSUIPC7 connects to MSFS2024. Have you tried this?

   2.  update offset 0x3308 back to 13 once FSUIPC7 has connected. You can do this by using an ipcInit.lua script (create this file) with the line:

      ipc.writeUW(0x3308, 13)

May be a good idea to add logging for offset 3308 as U16 (using FSUIPC’s offset logging facility) so we can see the value in the log file when it is being read. The log file you attached shows that this is currently 14 (0E 00) when being read:

16125 READ0[12340] 3308, 4 bytes: 0E 00 DE FA ….


Reply
Posts: 19
Registered
Topic starter
(@skythelimit)
Joined: 3 weeks ago

Hi John, you are a genius!  I did your step 1 above and it works, although see the pic below, it says “not connected”  (maybe this would be resolved if I do your step 2, I’ll try that) but it is reading the offsets perfectly.  I have already configured the flap gauge on the MIP, by assigning it to the offset x660C in the PMDG 737 offset list.

This will be huge for FI/PMDG users as it is a simple alternative to using Air Manager, which doesn’t have all the gauges available and working, so it would need some work with LUA scripts, I have no idea what this is like, but unnecessary as this works with fsuipc.

I’ll do your step 2 and set the x3308 logging as you suggested

Huge thanks!

Charles


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

Posted by: @skythelimit

I did your step 1 above and it works,

Ok – that would indicate that it is the FS version, held in offset 0x3308, that is preventing the FI sw from connecting.

Posted by: @skythelimit

although see the pic below, it says “not connected”

I think / presume that this is because FSUIPC7 was not connected to the FS / MSFS2024. If you now start MSFS2024, does it work?

When FSUIPC7 connects to MSFS, then offset 0x3308 will be updated to the correct value. But you can then change this back if needed, best done via an ipcInit.lua script as suggested. But, this is only needed if either:

   – the FI sw checks this offset again after connection to the FS

   – you start the FS sw software after FSUIPC7 gets a connection to MSFS

So you have two options:

1. Always start the FI sw before FSUIPC7 is connected to MSFS

2. Update offset 0x3308 again after FSUIPC7 has connected to MSFS (best done via an ipcInit.lua script as suggested).

John


Reply
Posts: 19
Registered
Topic starter
(@skythelimit)
Joined: 3 weeks ago

1. Always start the FI sw before FSUIPC7 is connected to MSFS

2. Update offset 0x3308 again after FSUIPC7 has connected to MSFS (best done via an ipcInit.lua script as suggested).

Thx John, I am doing steps 1 and 2 for good sake, and all seems to be working great and I have checked the offset is being set back to 13, I have set up most of the gauges already, looking very good


Reply
Posts: 1
Registered
(@hans-k)
Joined: 2 months ago

John and Charles,

Thanks for this solution! It was the last part of my home cockpit that didn’t work. I knew that it was offset 0x3308 but I needed the trick with the Lua file.

It makes my weekend.

Regards,

Hans


Reply
Page 2 / 2