FSUIPC_WAPI and ExecuteCalclatorCode Issue

[John Dowson]

38 minutes ago, John Dowson said:

I haven't released this update yet though - I will do some further testing first.

I have released this now - the beta release (available in the Announcements page) has been updated to include this change.
I plan to make this the official release at the weekend.

John

[Flex45]

On 2/21/2023 at 3:10 PM, John Dowson said:

I have released this now - the beta release (available in the Announcements page) has been updated to include this change.

Great! Many Thanks!

Regards,

 

[Flex45]

Hi John,

Using FSUIPC_WAPI v1.0.0 and 1.0.1, I am unable to use getLvar() as it used to work with v0.9.1.

I guess that's caused by the delay introduced in the recent versions and the requirement to get the callback before but, the getLvar/setLvar etc, since they are called on demand and not using callbacks, can't they be excluded from these changes in loading of variables and work like they used to work?

Regards, 

[Flex45]

Hi again, 

Disregard the above post, it was totally my bad. I used the new WAPI versions but didn't update the libraries from the new package. I am however facing a different issue now.

Using the new version libraries I can only build in debug mode with the debug library but not in release mode. In release mode with release library I get the following error during build:

Any ideas John?

I get the same behavior using library from WAPI package v 1.0.0 and 1.0.1.

Also I confirm as well what another user reported, (at least in debug mode that I can build) v1.0.0 is causing exceptions and crashes, v1.0.1 looks more stable.

 

Regards,

[John Dowson]

2 hours ago, Flex45 said:

Using the new version libraries I can only build in debug mode with the debug library but not in release mode. In release mode with release library I get the following error during build:

Any ideas John?

What version of VS are you using and which toolset? This seems to occur when using libraries built with a different VS toolset - see https://learn.microsoft.com/en-us/answers/questions/1130957/link-fatal-error-c1007-unrecognized-flag-zc-nrvo-i

If not using VS2022 then try with that using windows SDK 10.0. 19041,0, which is what the FSUIPC_WAPI.lib is built with.

2 hours ago, Flex45 said:

Also I confirm as well what another user reported, (at least in debug mode that I can build) v1.0.0 is causing exceptions and crashes, v1.0.1 looks more stable.

Not sure what exceptions you are referring to, but there should have only been an issue/crash when calling SimConnectEnd(). There was an issue in this function in v1.0.0, corrected in v1.0.1, due to trying to drop/clear the lvar/hvar name CDA definitions which are now dropped/cleared directly after being read.

Regards,

John

Later: it may be the MSVC toolset, not the SDK,  which is v143 for VS2022.  I have noticed that there is also a later SDK, v10.0.20348.0, although I am not using this yet. I may update for the next release, but I will add a README.txt and specify the toolset and SDK versions used om the next release.

Edited March 8, 2023 by John Dowson
Later added

[Flex45]

3 hours ago, John Dowson said:

If not using VS2022 then try with that using windows SDK 10.0. 19041,0, which is what the FSUIPC_WAPI.lib is built with.

I was on VS2022, MSVC v143 and tried SDK 10.0.19041,0 but was failing in the same way. I did a complete VS2022 update and that fixed the issue, so I don't know what it was exactly but at least the issue is now resolved! 

3 hours ago, John Dowson said:

Not sure what exceptions you are referring to, but there should have only been an issue/crash when calling SimConnectEnd(). There was an issue in this function in v1.0.0, corrected in v1.0.1, due to trying to drop/clear the lvar/hvar name CDA definitions which are now dropped/cleared directly after being read.

Not sure either, just trying to set an Lvar with v1.0.0 libraries, Lvar was set and then an exception was thrown. I didn't investigate further though as with v1.0.1 libraries there was no issue.

fsuipc-lvar-module version in community folder, was in both cases v1.0.0.

Thanks for the help once more

Regards,

[John Dowson]

43 minutes ago, Flex45 said:

I was on VS2022, MSVC v143 and tried SDK 10.0.19041,0 but was failing in the same way. I did a complete VS2022 update and that fixed the issue, so I don't know what it was exactly but at least the issue is now resolved! 

Hmm, strange...but glad this is now resolved.

44 minutes ago, Flex45 said:

Not sure either, just trying to set an Lvar with v1.0.0 libraries, Lvar was set and then an exception was thrown. I didn't investigate further though as with v1.0.1 libraries there was no issue.

This is also strange - the current release of FSUIPC7 is still using the WAPI v1.0.0 seemingly without issues.

46 minutes ago, Flex45 said:

Thanks for the help once more

No problem!