Couatl64_P3D.exe craches when loading P3Dv4.5 scenario

[Windshear1]

Like many others I struggle with the latest GSX L2 update.
Since the last "FSDT Live Update", Couatl64_P3D.exe crashes when loading the default P3D scenario. 
No problems with previous updates. 
After consulting the forums I have taken the following actions, but without success :
- completely uninstall of GSX
- delete folders :
    %appdata%\Virtuali
    %programdata%\Virtuali
    C:\Program Files (x86)\Addon Manager
- add folder C:\Program Files (x86)\Addon Manager to exclusion list in Bitdefender
- disable Bitdefender Shield
- downloaded lastest setup from your website : gsx_p3d4_setup2.exe
- disconnect from internet
- run gsx_p3d4_setup2.exe
- connect to internet
- downloaded and installed FSDT Universal Installer
- Universal Installer -> update all
- rebooted PC
- P3D client re-installed

Crash in eventviewer : 
    Naam van toepassing met fout: Couatl64_P3D.exe, versie: 4.8.0.4800, tijdstempel: 0x62ff6845
   
Installed software :
    Windows 10 home : 10.0.19044
    Prepar3D_v4_Academic_4.5.14.34698
    Microsoft Flight Simulator SimConnect Client v10.0.61259.0
    Sode 1.7.1
    Couatl64_P3D.exe 4.8.0.4800
    Microsoft Flight Simulator SimConnect Client v10.0.61259.0
    Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.30501
    Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30501
    Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.32.31332
    Microsoft Visual C++ 2015-2022 Redistributable (x86) - 14.32.31332

No addons have been changed or added since the last successful update.
Any suggestions to solve my problem ?
Do I have to wait for an updated installer ?

[flaviossa]

Exactly my issue here too. I suggest that you wait a little longer and give some time to Umberto look over this. He already said that he´s working on this 

[gevan]

After having the same problem you two mentioned, I've reinstalled all he FSDT software and sceneries endless times, and even uninstalling my Avira antivirus and leaving only Windows Defender, I was able to solve it after seeing a comment on the forum (I don't remember the user but I'm glad lovely person you shared your solution that helped me), updating the P3Dv4.5 navigation database which I normally do with every AIRAC update called "World FSXP3D package" (created and constantly updated by Herve Sors, ​​thank you very much for your great work) and there was an error in the version 2208 update (August 11, 2022) that caused the crash of "Couatl64_P3D.exe" when loading the flights, GSX 1 and 2 could never work due to that error, so I downloaded and installed the new version of "World FSXP3D package AIRAC 2208-R2" and it fixed my problem, hallelujah!

If you use that nav database update for your P3Dv4.5, I recommend that you install the new corrected version and it should fix the problem.

If you have already done so and the problem persists, you may need to exclude more EXE files and folders from FSDT to avoid errors; In case your problem persists, it would remain for FSDT to correct in detail any errors you are getting with the latest version of GSX (which by the way I have not updated after reading the number of issues it has presented when launching GSX Pro) .

Good luck and regards.

[flaviossa]

If you use that nav database update for your P3Dv4.5, I recommend that you install the new corrected version and it should fix the problem.

If you have already done so and the problem persists, you may need to exclude more EXE files and folders from FSDT to avoid errors; In case your problem persists, it would remain for FSDT to correct in detail any errors you are getting with the latest version of GSX (which by the way I have not updated after reading the number of issues it has presented when launching GSX Pro) .

Good luck and regards.

Man..... i would give you a KISS if you were here 
Spot on! My GSX came back from the dead! Umberto need to know about this asap. Thankssssssssssss!

[virtuali]

Spot on! My GSX came back from the dead! Umberto need to know about this asap. Thankssssssssssss!

This was in fact already discussed some days ago:

http://www.fsdreamteam.com/forum/index.php/topic,26462.msg173084.html#msg173084

[flaviossa]

Spot on! My GSX came back from the dead! Umberto need to know about this asap. Thankssssssssssss!

This was in fact already discussed some days ago:

http://www.fsdreamteam.com/forum/index.php/topic,26462.msg173084.html#msg173084

Sorry, i missed that message. Anyway, im back to the game  (And i think other P3Dv4.5 users too)

[Windshear1]

Thank you gevan for your golden tip. 
After hours of try and error GSX is back up and running. 
I also missed the message from 14/8.
@FsDreamteam : it would be helpful to indicate in the log file
 which scenery file is corrupt.  This could lead us to the solution faster.

[virtuali]

@FsDreamteam : it would be helpful to indicate in the log file
 which scenery file is corrupt.  This could lead us to the solution faster.

The problem is, a corrupted file will make the program crash before it could log anything, and it's not easy to make out the difference between a completely corrupted file ( which can be eventually trapped using normal windows functions ) from a file that is perfectly fine from a filesystem point of view, but it might have the wrong .BGL record, or wrong pointers, etc. windows wouldn't know it, because from its point of view, the file might be ok.

[gevan]

Man..... i would give you a KISS if you were here 
Spot on! My GSX came back from the dead! Umberto need to know about this asap. Thankssssssssssss!

I'm glad I was able to help you solve your problem.

By the way, I would only let myself be kissed by Henry Cavill (he's beautiful), sorry about that XD.

Regards and keep enjoying this wonderful addon for P3D.

Man..... i would give you a KISS if you were here 
Spot on! My GSX came back from the dead! Umberto need to know about this asap. Thankssssssssssss!

[gevan]

Thank you gevan for your golden tip. 
After hours of try and error GSX is back up and running. 
I also missed the message from 14/8.
@FsDreamteam : it would be helpful to indicate in the log file
 which scenery file is corrupt.  This could lead us to the solution faster.

Nothing to thank, we are a community and we must support each other to continue enjoying this wonderful P3D complement.

Regards.

[gevan]

I don't know if there is already a FAQ section for the most common errors/issues Umberto, if so, you could add this solution that was already shared so that more people can follow a list of procedures before opening a new topic due that the forum has some repeated responses (such as folder exclusion in the antiviruses, etc.).

It's just a suggestion and it would take a lot of work off your shoulders in the most repetitive problems that are usually in the forum.

Regards.

[virtuali]

It would be enough it anybody opening a thread would give it a proper title.

"P3D issues after the last update"
"Nothing works"
"Another problem with the update"
"The update is a disaster"


These are useless titles that makes very hard to track issues, because other users with various problems feel their need to jump in, just because the title is so generic.


"Calling Boarding crashes with an error", followed by a precise description of the airport, the airplane, the gate and the actual error log, that's something I can use, and can stay there to track issues.