With SU10 Navdata API option on, I must restart couatl after landing every time

[whiggy]

I notcied, If I'm using the SU10 Navdata API option on, Couatl seems to be crashing before landing. This occurs every flight.
If I want to have GSX after landing, I must restart couatl manually.

I'm using Couatl64_MSFS.exe file version from 16.12.2022 (version 4.8.0.5105)

[SuperSixBravo]

Same problem,

But at least it still works.

[IMatAMS]

Indeed, this has been an issue since the SU10 beta option I think, up until the current version. The SU10 beta option works better in that it avoids issues with AFCADs, but it does require a restart for use on arrival.. Hope this gets fixed so the SU10 option can be switched on all the time.

[virtuali]

We are still trying to produce the problem and, as requested in all other threads about this issue, it would be helpful getting more data about your installation, especially:

- a list of all 3rd party add-ons that might possibly use Simconnect, like AI traffic utilities or modules that loads with the sim.

- if you are using 3rd party Navdata

- your starting and destination airports, possibly with the route taken, so we might try to replicate the flight, to check if the problem is possibly caused by some unexpected data coming from the Navdata API, like nearby airports, etc.

[whiggy]

Addons which are using simconnect?
Hmm so far I can say it's only Volanta.
All my other addons are using FSUIPC.

Yes I'm using Navigraph Navdata for MSFS and my addons.

I notice this problem on every flight with navdata api. Can not isolate to any airports.

[IMatAMS]

1. Axis and ohs, Volanta, vpilot(?)
1a. modules that load with exe.xml:  Nool aero, Axis and Ohs, Fenix bootstrapper, Logitech plugin (for radio panel) , aerosoft VDGS module, FSUIPC7

ACARS VA clients but they all use FSUIPC I believe

2. Navigraph data

3. any route. Consistent behaviour, all flights when SU10 option is enabled.

[whiggy]

<?xml version="1.0" encoding="utf-8"?>
<SimBase.Document Type="Launch" version="1,0">
   <Descr>Launch</Descr>
   <Filename>exe.xml</Filename>
   <Disabled>False</Disabled>
   <Launch.ManualLoad>False</Launch.ManualLoad>
   <Launch.Addon>
      <Name>AFCBridge</Name>
      <Path>D:\MSFS_Content\community\AFC_Bridge\bin\AFC_Bridge.exe</Path>
      <Disabled>True</Disabled>
   </Launch.Addon>
   <Launch.Addon>
      <Name>Aerosoft VDGS Driver</Name>
      <Path>D:\MSFS_Content\Community\aerosoft-vdgs-driver\aerosoft-vdgs-driver.exe</Path>
      <Disabled>False</Disabled>
   </Launch.Addon>
   <Launch.Addon>
      <Name>noolaero-module-vdgs</Name>
      <Path>D:\MSFS_Addons\Mods Freeware\Nool MSFS VDGS 3.3.0\noolaero-module-vdgs\Binaries\vdgs-util.exe</Path>
      <Disabled>False</Disabled>
   </Launch.Addon>
   <Launch.Addon>
      <Name>Couatl</Name>
      <Disabled>False</Disabled>
      <Path>D:\FSTools\Addon Manager\couatl64\couatl64_MSFS.exe</Path>
   </Launch.Addon>
   <Launch.Addon>
      <Name>FenixA320</Name>
      <Disabled>False</Disabled>
      <Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path>
   </Launch.Addon>
   <Launch.Addon>
      <Disabled>False</Disabled>
      <ManualLoad>False</ManualLoad>
      <Name>FSUIPC7</Name>
      <Path>D:\FSTools\FSUIPC7\FSUIPC7.exe</Path>
      <CommandLine>-auto</CommandLine>
      <NewConsole>False</NewConsole>
   </Launch.Addon>
     <Launch.Addon>
        <Name>MDClient</Name>
          <Disabled>True</Disabled>
          <Path>C:\Users\whiggy\Documents\Maddog X Files\MSFS 2020\MDClient\MDClient.exe</Path>
     </Launch.Addon>
</SimBase.Document>


Axis and Oh's : No
vpilot: yes
Navigraphdata: yes



Windows Event-Manager Log entry:


Name der fehlerhaften Anwendung: Couatl64_MSFS.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00007ffe2b832e70
ID des fehlerhaften Prozesses: 0x0x1724
Startzeit der fehlerhaften Anwendung: 0x0x1D920B49460BB99
Pfad der fehlerhaften Anwendung: D:\FSTools\Addon Manager\couatl64\Couatl64_MSFS.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: ef69b63c-9d63-40ce-b5a9-259435284d47
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

[virtuali]

1. Axis and ohs, Volanta, vpilot(?)
1a. modules that load with exe.xml:  Nool aero, Axis and Ohs, Fenix bootstrapper, Logitech plugin (for radio panel) , aerosoft VDGS module, FSUIPC7

ACARS VA clients but they all use FSUIPC I believe

2. Navigraph data

3. any route. Consistent behaviour, all flights when SU10 option is enabled.

First thing to check, is trying with all those add-on modules AND Navigraph data disabled ( everything disabled, except GSX ), and do the same route. If these addons are linked to the Community, for example using the Addon Linker, it should be very easy to disable all of them and try again.

If you don't get the crash with everything Disabled, the best 2nd step would be enabling ONLY Navigraph data and test again.

[whiggy]

So, I found the problem.
All what I need todo is remove "afcad_path =" from the airport config.
I made 5 flights today without the crashing problem.

It seems to be a problem if an afcad_path is in the config when you using Navdata API option.

 

[virtuali]

It seems to be a problem if an afcad_path is in the config when you using Navdata API option.

Weird, considering that line is completely ignored when using the Navdata API, but we'll have a look at it.

[whiggy]

I'm really sad because today couatl crash again on an flight . Maybe the last few flights was happenstance where it has worked. I don't know.
   

[virtuali]

Found this tip on GSX profile creators channel on Discord:

1. Open Windows Security - type "Windows Security" in your Start menu

2. Click App & browser control

3. Click Exploit protection

4. Click Program settings

5. Click Add program to customize

6. Browse to \Addon Manager\Couatl64\Couatl64_MSFS.exe click Ok

7. Scroll down to Data Execution Prevention (DEP)

8. Check Override system settings

9. Toggle switch to Off

10. Click Apply (Save)

[Copper]

7. Scroll down to Data Execution Prevention (DEP)

8. Check Override system settings

9. Toggle switch to Off

Guys, please don't do that. Better do manual restarts of Couatl than disabling security settings that are important to have on.

[virtuali]

Guys, please don't do that. Better do manual restarts of Couatl than disabling security settings that are important to have on.

That procedure disables DEP JUST for the Couatl64_MSFS.exe, not the whole system, and won't cause any security problems, unless you think the Couatl engine is really a threat/virus, but if you do, you'd better not using GSX to begin with.

[ACSoft]

Found this tip on GSX profile creators channel on Discord:

1. Open Windows Security - type "Windows Security" in your Start menu

... etc ...

Uberto, for your information, with "use SU10 Navdata API" ON and this tip added, I tested my flight LFML>LSGG where Couatl engine systematically cash before landing and this tip didn't solved nothing, almost in my case.

Hope this might help.