|
Post by dirknl on Jan 4, 2023 12:23:15 GMT
After doing the 2213 update my GSX did not work anymore. The Couatl engine aborts at startup so there is no longer GSX avaiable. Setting my system back to the 2212 update solved the problem.
Don't know what exactly caused this problem, but Humberto or his staff (fsdreamteam) will know.
Dirk
|
|
|
Post by Herve Sors on Jan 4, 2023 21:55:15 GMT
Hello Dirk,
As previously mentioned, could you send me the GSX log that was created following this load failure Please attach it to a mail sent to aero(at)sors.fr
You will have to enable logging. Here are the instructions from the GSX forum
- open the Notepad and type the following on a new blank file: logFile=couatl.log (please note logFile is written beginning with a lower case L and a capital F )
- Save the file as couatl.ini in the %APPDATA%\Virtuali folder
- Run the sim, then exit after the error appears.
- Check your %APPDATA%\Virtuali folder for the Couatl.LOG file there
Hervé
|
|
|
Post by romeowhiskey on Jan 5, 2023 0:58:29 GMT
Greetings. I am also experiencing this problem. I got a fresh install of P3D, and just downloaded the 2213 cycle update. And I too experience GSX crash. I tried to uninstall cycle 2213 and GSX worked fine. But I would have default navaid cycle. I don't know my options but is there a way for me to get the 2212 cycle update?
|
|
|
Post by romeowhiskey on Jan 5, 2023 1:00:40 GMT
The log file also indicates nothing of note. No error or anything, no crash or anything.
|
|
|
Post by Herve Sors on Jan 5, 2023 6:08:35 GMT
Hi Romeowhiskey,
Indeed, there have been several reports of GSX crash after updating to 2213 cycle. One report indicates it does not occur with the previous 2212 cycle I carefully analyzed the changes that were done to airport APX files in 2213 cycle (127 files) and couldn't detect any problem in file structure according to MS/P3D SDK. With the exception of a few invalid duplicate COM frequencies that already exist in 2212 cycle (now corrected), all files decompile and recompile successfully using the available tools and the MS/P3D compiler. Also, there is no problem at all in the simulator. Consequently, I cannot identify by now the cause of the problem and provide a solution. For that, I would need to know where and why GSX fails in its analytical process and, at least, it provides the necessary details in its "crash" log (pointing out file and BGL section/subsection responsible for this failure). Without that, it's just looking for a needle in a haystack. I do not say there is no problem at all in the updated files (although they appear OK as regard their structure and content). I only need some more details that can only be provided by the GSX analytical process log. One way to partly tackle the problem could be to identify first the installed "region" that caused the crash. For that, you will have to fully uninstall the FSX/P3D update and reinstall regions one by one. However, each region involves several files and it may not provide a definitive answer, but it may help.
Hervé
|
|
|
Post by romeowhiskey on Jan 5, 2023 9:23:34 GMT
Good day. Here's a report on my end.
I have managed to make 2213 work with GSX on P3D with all regions installed except America North. I have installed the regions one by one with firing up the sim after each to check if GSX would work. GSX works until I install America North. Right now, I have installed 2213 update with only America North Region not installed.
|
|
|
Post by romeowhiskey on Jan 5, 2023 9:24:52 GMT
Here's the last few lines from the couatl log.
using "C:\Program Files (x86)\Addon Manager\FsDreamTeam\Exclude\scenery" (layer 135) using "C:\Users\patri\AppData\Roaming\Virtuali\GSX" (layer 2147483647) airportCacheOptimizeSearch enabled, excluding files larger than 20000000 bytes Airport cache not valid: file meta.txt not found or malformed Regenerating airport cache, looking for scenery files under "D:\Lockheed Martin\Prepar3D v4" Worker thread started
|
|
|
Post by Herve Sors on Jan 5, 2023 16:03:50 GMT
Ok.Thanks Romeowhiskey. It restricts search for a solution to North America files (unfortunately there's quite a lot). I doubt a more comprehensive couatl.log will ever become available. May I ask you to perform some additional tests? If you agree I will contact you on your registred email for this forum
Regards
Hervé
|
|
|
Post by alcuntor on Jan 5, 2023 19:26:23 GMT
I can confirm that instaling AIRAC 2213 except North America North and South GSX works OK
|
|
|
Post by Herve Sors on Jan 5, 2023 22:14:18 GMT
Alcuntor,
According to RomeoWhiskey, only NorthAmerica region makes GSX to fail but SouthAmerica is OK. Please confirm
|
|
|
Post by Herve Sors on Jan 5, 2023 22:24:09 GMT
Hi all,
I uploaded a new set of files (2213-R2). Corrections were minor on 21 BGL files (mainly duplicate COMs and some incorrect airport summary flags) so there's little chance it solves the problem but you can give it a try.
Hervé
|
|
|
Post by alcuntor on Jan 6, 2023 2:26:49 GMT
I can confirm that SouthAmerica is OK, I installed your new set of files (2213-R2) and NorthAmerica has the problem. Reinstalled AIRAC without NorthAmerica and GSX workks OK
|
|
|
Post by alcuntor on Jan 6, 2023 2:47:36 GMT
By the way Herve, is there a way to rename the files .bglbckup to antoher .name because FsTramp reads the .bglbckup as an AFCAD file, maybe just .bckup
|
|
|
Post by romeowhiskey on Jan 6, 2023 2:50:06 GMT
Good day, where can I get the 2213 R2? Thanks.
|
|
|
Post by alcuntor on Jan 6, 2023 3:50:17 GMT
|
|