motorized TQ and MCP/EFIS hardware stopped working with Latest FSUIPC version 7.5.0

[speedbird144]

Greetings 

I installed a new version yesterday and I noticed it was for both MS2020 and 2024. Once I installed my motorized TQ and MCP/EFIS hardware stopped working. I am not saying FSUIPC was the cause, I am just trying to figure out what went wrong. Everything was working before I installed a new version yesterday. Is there a way to roll back to previous version to check? 

[John Dowson]

Sorry but can you please five your topics a more appropriate title... I will update it...

8 minutes ago, speedbird144 said:

Is there a way to roll back to previous version to check? 

7.4.18 attached below - save and remove the .7418 extension...

John

 FSUIPC7.exe.7418

[speedbird144]

Thank you. 

[John Dowson]

If its ok with that version but not working with the latest release, could you send me/attach the log files from both as well as your FSUIPC7.ini and I will take a look.

John

[Hans K]

Hi,

I detected something with version 7.5.0 that's probably the same. I am using a program (EFB2) that is uses FSUIPC to interface with MSFS2020. I installed two separate versions of FSUIPC but since then I am getting messages from EFB2 that a wrong simulator is running (so not MSFS2020). However the program is working fine, only these messages (every 5 minutes) are annoying. 

Today I installed the version 7.4.18 for MSFS2020 and the messages are gone. The only thing now is that I am getting a message that a new version is available.

Hans

 

[John Dowson]

20 minutes ago, Hans K said:

I detected something with version 7.5.0 that's probably the same. I am using a program (EFB2) that is uses FSUIPC to interface with MSFS2020. I installed two separate versions of FSUIPC but since then I am getting messages from EFB2 that a wrong simulator is running (so not MSFS2020). However the program is working fine, only these messages (every 5 minutes) are annoying. 

Then it is EFB2 that needs updating. EFB2 is probably checking offset 0x3308 (or maybe offset 0x3124) for the simulator version. Previously that held 13 for MSFS2020 and was populated on FSUIPC7 start-up. Now it holds 13 for MSFS2020 and 14 for MSFS2024 and is only populated once connected to MSFS. You should check for an update to that for MSFS2024.

John

[Hans K]

OK John, that's clear. The problem is that support for EFB2 stopped some months ago although a lot of flightsimmers still use the program.

I am aware that a combination of EFB2 and MSFS2024 will not be possible but as long as I use MSFS2020 as my main simulator I like to use EFB2. With your info I did a test with version 7.5.0 and MSFS2020 and when I start EFB 2 after MSFS2020/FSUIPC is established there is no problem. SOLVED.

Hans

 

[speedbird144]

Hello again. So yes, The previous version works fine. For some reason the software for my TQ (from "Cockpit For You" manufacturer) does not recognize the simulator when I have the latest version installed. Once I roll back to the previous version it detects the sim right away and everything works normal. 

I have attached 4 files as request. I added "new" extensions to the latest version files. 

Thank you  

FSUIPC7.ini FSUIPC7.ini.new FSUIPC7.log FSUIPC7.log.new

[John Dowson]

11 hours ago, Hans K said:

With your info I did a test with version 7.5.0 and MSFS2020 and when I start EFB 2 after MSFS2020/FSUIPC is established there is no problem. SOLVED.

Presumably this is because offset 0x3308 is now only populated after FSUIPC has established a connection with the sim whereas previously it was populated on start-up (as it only ever used to connect t0 MSFS2020).

4 hours ago, speedbird144 said:

For some reason the software for my TQ (from "Cockpit For You" manufacturer) does not recognize the simulator when I have the latest version installed.

This is most probably due to the same reason. Does it connect if you start the software after FSUIPC has connected to MSFS (when offset 0x3308 is populated)? Have you checked with the software provider to see if an update will be provided for MSFS2024?
Also can you please always exit FSUIPC7 before attaching any log files.

[speedbird144]

In order to use this TQ I have to turn on the TQ power then open a TQ console (to start a software). After these two steps I start the simulator. If I start the console (software) when the sim is already running the TQ won’t work. This is how it was designed. However, I did try to start software after FSUIPC connection, and I saw the simulator was detected, but the throttle didn’t work. 
I will try to reach out the developer, but he is almost impossible to be reached. Everyone complains about his lack of support unfortunately. 

[John Dowson]

Can you try the attached version please to see if this helps. For this version, please add the following to the [General] section of your FSUIPC7.ini file:
      Init3308=13
You can use the value 14 if using MSFS2024, but if using software not updated for MSFS2024 best to stick to 13 regardless of the version of MSFS being used.
The value will be updated/overwritten with the correct version anyway once FSUIPC7 connects to MSFS.

This will initialize offset 0x3308 to that value (to whatever value is given) on start-up. This should then mimic the behavior in 7.4.18.

John

 FSUIPC7.exe

Edited December 10 by John Dowson
Further info added

[speedbird144]

Perfect. This file works with Init3308=13. I use MS2020, this TQ is not compatible yet for 2024 as no addon 737 yet. Everything is back to normal. 

If another update will brake my TQ again, should I just come here again or add that line to .ini file again?

Thank you for solving the problem.  

FSUIPC7.ini FSUIPC7.log

[John Dowson]

3 hours ago, speedbird144 said:

If another update will brake my TQ again, should I just come here again or add that line to .ini file again?

There is no point adding that line again if its already there, and that is to dix a specific problem - to fix issues with 3rd-party programs that are expecting a value in that offset even when FSUIPC is not connected to the FS (i.e. basically for software not yet updated for MSFS2024).
If you get any issues with a new release, you should always raise a new support topic.

John