FSUIPC7 version 7.5.0-beta available for both MSFS2020 and MSFS2024

[John Dowson]

1 minute ago, BlackLiverieZ said:

I noticed the following. For ‘A Pilot's Life Chapter 2’ you need FSUIPC.

In MSFS 2020, everything works wonderfully.

But not so much with the beta in 2024.

The tool recognises the connection to the simulator, but the ‘Flight Stage’ point always remains red. Is there perhaps a solution for this?

I don't know and do not support 'A Pilot's Life'. You should contact them first - maybe that needs an update for MSFS2024? Otherwise, I would need to know what this app uses to determine the 'flight stage'. The image you attached also shows FLIGHT SIMULATOR DISCONNECTED, so its not surprising that the flight stage is not started.

[ValorV]

37 minutes ago, BlackLiverieZ said:

Hi all,

I noticed the following. For ‘A Pilot's Life Chapter 2’ you need FSUIPC.

In MSFS 2020, everything works wonderfully.

But not so much with the beta in 2024.

The tool recognises the connection to the simulator, but the ‘Flight Stage’ point always remains red. Is there perhaps a solution for this?

@BlackLiverieZ To help you out: The current BETA version of FSUIPC does not work with APL 2. You should use 7.4.18 stable version, and manually start FSUIPC when you are loaded in FS2024, and then start APL 2.

[BlackLiverieZ]

@John Dowson Okay, the picture was just to show what this bar looks like. Here is a picture that shows the correct result. APL2 is an external software that simply tracks flights like an ACARS. It doesn't matter which simulator is used. It works with X-Plane, P3D, etc. To do that, it uses the FSUIPC, XUIPC, etc.

@ValorV Version 7.4.18 is only intended for the MSFS 2020, isn't it?

[John Dowson]

1 minute ago, BlackLiverieZ said:

Okay, the picture was just to show what this bar looks like. Here is a picture that shows the correct result. APL2 is an external software that simply tracks flights like an ACARS. It doesn't matter which simulator is used. It works with X-Plane, P3D, etc. To do that, it uses the FSUIPC, XUIPC, etc.

I know what APL2 is, but I do not know how it uses FSUIPC. If there are issues with APL2, then report to them. If there is an issue with APL2 using this beta, then they should contact me to explain what this issue is. As I say, I can only support FSUIPC, not 3rd party programs that use FSUIPC.

[sabres431]

10 hours ago, BlackLiverieZ said:

@John Dowson Okay, the picture was just to show what this bar looks like. Here is a picture that shows the correct result. APL2 is an external software that simply tracks flights like an ACARS. It doesn't matter which simulator is used. It works with X-Plane, P3D, etc. To do that, it uses the FSUIPC, XUIPC, etc.

@ValorV Version 7.4.18 is only intended for the MSFS 2020, isn't it?

You should not be reporting APL issues here.  The current answers are in the discord.  Ovi will be contacting John himself.

[NovemberUniform]

If I read the log correctly, my WASM is crashing almost instantly, when loading the Fenix A320. I have tried multiple times with same result. I have applied the same ini settings as in MSFS2020, where there were no problems with WASM crashes afterwards (before with default ini, there were occasional crashes). See ini and log attached. Thanks.

FSUIPC_WASM.ini FSUIPC_WASM.log

[John Dowson]

7 minutes ago, NovemberUniform said:

I have applied the same ini settings as in MSFS2020, where there were no problems with WASM crashes afterwards (before with default ini, there were occasional crashes). See ini and log attached.

You have lvarScanFrequency set to -10, i.e scan every 10 seconds. To prevent the WASM crash, you need to disable lvar scanning by setting this to 0, and maybe also increase the lvarScanDelay parameter - but not necessary if any lvars that you are using directly (i.e. not via presets or calc. code) are found in the first scan, You only need to increase this is using lvars directly (adding to offsets, or in lua or macros) and they are not found in the initial scan. Please see the FAQ entry on this issue.

[NovemberUniform]

2 hours ago, John Dowson said:

You have lvarScanFrequency set to -10, i.e scan every 10 seconds. To prevent the WASM crash, you need to disable lvar scanning by setting this to 0, and maybe also increase the lvarScanDelay parameter - but not necessary if any lvars that you are using directly (i.e. not via presets or calc. code) are found in the first scan, You only need to increase this is using lvars directly (adding to offsets, or in lua or macros) and they are not found in the initial scan. Please see the FAQ entry on this issue.

Hi John, I can confirm it works this way. At least the two times I tried it a few mins ago. Wouldn't it be wise to make this the default setting?

[John Dowson]

1 minute ago, NovemberUniform said:

Wouldn't it be wise to make this the default setting?

I am considering this for the next release....

John

[kaha]

John, if I go back to main menu after a flight and then load my next flight, lua scripts from the [AUTO] section are not started. again. This works on the first flight after starting up the sim, but not for the next one. Please see the log file.

Karl 

FSUIPC7_log.zip

[John Dowson]

8 minutes ago, kaha said:

John, if I go back to main menu after a flight and then load my next flight, lua scripts from the [AUTO] section are not started. again. This works on the first flight after starting up the sim, but not for the next one. Please see the log file.

Ok, strange...I thought I had checked  that. Will take a look...

John

[John Dowson]

@kaha Can you please check to see if the WASM is crashing, and if so disable lvar scanning. See the FAQ section for details on this. The WASM seems to be crashing a lot more in MSFS2024 - I will disable continual lvar scanning for the next release.

Auto luas are only started once the lvars have been received (if the WAPI/WASM is installed and enabled). From your log, no lvars are being received when you restart, so it looks like the WASM has crashed.

Check that and if you still have issues please set Debug level logging in both the WAPI and WASM, and show me both the FSUIPC7.log and FSUIPC_WASM.log files.

 

[kaha]

Ok, I'll check it.

[kaha]

One thing I noticed:

The WASM log for 2024 is in this folder: ...../WASM/MSFS2020/......

Is there anything wrong with my installation?

Karl

Edited 13 hours ago by John Dowson
image deleted

[John Dowson]

55 minutes ago, kaha said:

The WASM log for 2024 is in this folder: ...../WASM/MSFS2020/......

Is there anything wrong with my installation?

No, that is where MSFS puts it. It seems that it detects that it is compiled with the MSFS2020 SDK it creates the persistent storage area in that folder, and presumably for WASMSs compiled with the MSFS2024 SDK it will use the MSFS2024 folder.

John