Annoying after switching to new display

[BrzI]

Hi folks,

have been running GSX Pro in latest official MSFS2024 without issues.

After leaving my trusted IPS 8-bit 60 Hz monitor for a glorious new LG C5 and turning HDR on I started seeing the annoying message attached.

Note that GSX Pro seems to work well otherwise.

I have done a memory check and sfc check. No issues. Trying different combinations of HDR/Dolby Vision and 10 or 12 bpc colour did not resolve anything.

Would anybody have any suggestions short of a full GSX reinstall under Dolby Vision on PC ?

Running AMD adrenaline on an RX 7900 XTX.

Here is an excerpt form the application log:

Application: couatl64_MSFS2024.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF81277657C (00007FF812770000) with exit code 80131506.


Thanks

[BrzI]

I figured it out...

As I am now using a TV as a monitor I was looking for a way to bypass the inability of TVs to accurately parse PC power events.
An app that helps with this is LGTV (LG TV companion) that installed an x64 version of the MS Visual C++ 2015-2022 Redistributable.

This collided with x86 version.

Removing the x64 version did the trick. No more errors.

Hope this helps someone.

[virtuali]

An app that helps with this is LGTV (LG TV companion) that installed an x64 version of the MS Visual C++ 2015-2022 Redistributable.

That's precisely what the Couatl for MSFS 2024 requires, which is a 64 bit native app.

This collided with x86 version.

So maybe the app installed a wrong/outdated version of the runtime, which simply corrupted the correct one but the 64 bit version of the Couatl engine shouldn't be affected by the x86 version, because it doesn't use it. It can't, because it's a 64 app, only the FSX version (Couatl.exe) use it.

Removing the x64 version did the trick. No more errors.

The Couatl engine won't work without a 64 bit version of the runtimes. So, what really happened, is that removing the outdated version installed by that app might have fixed a more updated version that comes with Windows that might have been "shadowed" (if not corrupted altogether) by the outdated version.