|
|
Post by alcuntor on Jan 4, 2023 20:05:33 GMT
When installed AIRAC 2213-R1 "FSDreamTream FSDT GSX stops working, I did a new install from AIRAC 2207-R2 anf now GSX is working again, I like to have a newer working AIRAC cause 2207-R2 is the last I have
|
|
|
|
Post by Herve Sors on Jan 4, 2023 21:50:28 GMT
Hello Sir,
Could you please send me the GSX log file that is created after this failed event
Use my email adress: 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 michaelengl on Jan 6, 2023 23:27:30 GMT
Hi Herve , same problem with 2213-R2 Can you explain how your update and GSX are connected? Look: www.fsdreamteam.com/forum/index.php/topic,28900.0.html I uninstalled all America files and now GSX works again. Why? Happy new year Best Michael |
|
|
|
Post by michaelengl on Jan 6, 2023 23:50:06 GMT
Only North America is the problem with 2213-R2.
I did not fly with 2212, 2211 was OK.
I saw there is another thread . Just wanted to share this here.
|
|
|
|
Post by Herve Sors on Jan 7, 2023 8:43:35 GMT
OK Michael
Duly noted. Some tests will be performed soon, focusing on files that were updated since 2211. I already checked some
-H
<Edited>
There is no connection between my updates and GSX. The updated files in my package just replace the stock sim scenery files
I presume GSX proceeds to an analysis of airport files (APX) while loading for getting some data the program uses and it seems it doesn't like some of them in the North America region, although I checked those that were updated on cycle 2212 and 2213 (2211 was OK according to a report made here) and didn't find any damage in any of them by now.
What I regret is that GSX crashes without providing any information that may help. So, I'm on my own and it may take some time debugging more than 200 files :-(
-H
|
|
|
|
Post by preynolds on Jan 8, 2023 14:50:03 GMT
Hi Herve,
I've looped through all the APX files and decompiled them. All decompile without error apart from APX20200.bgl which errors with the following:
"Unknown ID 4464 found in airport record"
Hopefully this will help you pinpoint the issue (I presume GSX is reading the APX files and is falling over with the same issue in this file).
Cheers
Phil
|
|
|
|
Post by preynolds on Jan 8, 2023 17:48:14 GMT
Hi Herve,
Just to confirm the above information, I have tested GSX in P3D using the 2213-R2 release but manually replacing APX20200.bgl with the P3D original and everything works as expected.
So the issue is definitely with APX20200.bgl.
Cheers
Phil
|
|
|
|
Post by Herve Sors on Jan 9, 2023 7:52:14 GMT
Hi Phil,
Thanks for the report. Indeed APX20200.bgl is the culprit. Another user (alcuntor) confirmed that in a long serie of tests. Also, thanks to him
However, I didn't have any decompilation error using ScruffyDuck Bgl2Xml on this file and I could recompile it, again without any error using the MS Bglcomp, the reason why I didn't detect it at first glance.
Know that my updates are directly done on BGL files using AIE without any decompilation/recompilation. Many update processes are rather "technical" but the program is now well tested and debugged
Could you tell me with which decompiler you get this Unknown ID 4464 and if the offending airport is identified in the error report so as I can see if a correction is possible or if I will have to rebuild this file from scratch?
Cheers
Hervé
|
|
|
|
Post by preynolds on Jan 9, 2023 8:38:22 GMT
|
|
|
|
Post by Herve Sors on Jan 9, 2023 9:22:58 GMT
Ok Phil got it with v1.7.0 of Bgl2Xml as you. My v1.10.7504.13655 version released in 2020 (that includes compatibility with P3DV5) doesn't raise this error
I will ask Jon
-H
<Edit>
I now identified the problem. BGL was slightly misformed on a single airport (KHOB) with some unreferenced bytes and removal of ground structure. But it shouldn't have caused a crash just be ignored since all pointers were OK
A corrected APX20200.bgl file will be made available on next release (2301-R3)
|
|
|
|
Post by preynolds on Jan 9, 2023 12:48:48 GMT
Great stuff, glad you got to the bottom of it.
Cheers
Phil
|
|
|
|
Post by Herve Sors on Jan 9, 2023 18:06:17 GMT
A corrected APX20200.bgl file is now available here and should solve the GSX crash www.aero.sors.fr/beta/APX20200.rarNorth America region can now be installed as before using 2213-R2, then the APX20200.bgl file (located in the Scenery/0202/scenery subfolder) has to be replaced with the corrected one (ensure first the APX20200.bgl.bglbckup exists) This corrected file will be included in the R3 revision that will be available on next thursday (January 12th) A new installer will also be included starting with 2213-R3 including the following changes - change of the default backup file extension to .hsbckup (so as to avoid problems with some other software that use the .bglbckup extension). For those who already have installed any version of the package, extension renaming will be automatic so you do not have to worry about this change - possibility to selectively install or uninstall some airport APX files by using a special /FileSelect argument Documentation will be updated accordingly Special thanks to Alejandro (alcuntor) and Phil (preynolds) who helped me debugging this difficult problem Hervé |
|
|
|
Post by alcuntor on Jan 9, 2023 23:24:03 GMT
Was my pleasure Hervé
|
|
