Products Support > GSX Support MSFS

Couatl starts manually, but not automatically with the simulator

<< < (11/15) > >>

CVJ:
I solved the problem by starting COUATL as an Administrator BEFORE starting the simulator. That works like a charm on my setup, provided I use the GSX "Taskbar button inside cockpit to start the app.
My setup is Windows 10 and the Microsoft Store version of the flight sim.

Ankh:
So, due to my switch from a 8700K to a 13600K I took the plunge and re-installed Windows and MSFS. Then, as reports suggest better scheduler in Windows 11, I also performed a brand new install of Windows 11. Afterwards, I put all my addons back into MSFS, re-installed GSX Pro and guess what? Not a single issue with this nasty content.xml stuff, Couatl started each and everytime I fired up my sim. With the exact same number of addons I had before.

BUT: due to Couatl crashing when arriving at the gate, I modified the Couatl64.exe by ticking the "start as administrator" checkbox and the last update also automatically set "use Windows 8 compatibility mode". And guess what? Now this annoying little .exe does NOT start up with the sim anymore. What a bummer.

I will now remove those two checkboxes again and test. But honestly, I am so sick of this testing around, why this thing cant just run as expected?

virtuali:

--- Quote from: Ankh on February 23, 2023, 09:30:40 am ---BUT: due to Couatl crashing when arriving at the gate, I modified the Couatl64.exe by ticking the "start as administrator" checkbox and the last update also automatically set "use Windows 8 compatibility mode". And guess what? Now this annoying little .exe does NOT start up with the sim anymore. What a bummer.

I will now remove those two checkboxes again and test. But honestly, I am so sick of this testing around, why this thing cant just run as expected?

--- End quote ---

As explained so many times already, we were never, ever, able to replicate the crash in flight. The only data we had is reports from users, and the only choice we have is to trust users that a solution worked for them, if they said so.

Since in the past weeks, we got overwhelming confirmations from multiple user that setting Windows 8 Compatibility mode totally fixed the crash in flight we could never replicate, we set it by default with the installer.

You are the one and only reporting that option is preventing the program to start. Of course, I cannot replicate that either because, before deciding to make the Windows 8 compatibility set as default, I tested it for at least a couple of weeks and, while I couldn't see ANY difference ( it didn't crash before, it doesn't crash now ), but at least I know it doesn't do any harm so, why should I doubt users that *had* the crash, all reporting Windows 8 Compatibility fixed the problem for them ?

If it doesn't work for you, you are the first one saying that so, just turn it off. And best not turn off "both" options at the same time, otherwise you'll never know which one works and which one doesn't.

Ankh:

--- Quote from: virtuali on February 23, 2023, 11:31:53 am ---If it doesn't work for you, you are the first one saying that so, just turn it off.
--- End quote ---

I did, took the checkmark off the "use Windows 8 compatibility mode" and guess what, couatl starts again without hickup together with the sim. So in my case, using the Windows 8 compatibility mode does no good. BTW, I am on a brand new Windows 11 installation, might be that this is the reason and for Windows 10 users, the Windows 8 compatibility helps. Who knows...

virtuali:

--- Quote from: Ankh on February 27, 2023, 08:54:54 am ---I am on a brand new Windows 11 installation, might be that this is the reason and for Windows 10 users, the Windows 8 compatibility helps. Who knows...
--- End quote ---

Most users that confirmed the Windows 8 compatibility flag helped were using Windows 11, and some Windows 10.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version