Products Support > GSX Sharing area - Scenery Configs
Armi Project Muscat Intl OOMS GSX L2 Compatible
CosmicWanderer:
I tried rebuilding the cache. It took 55 seconds, then nothing. I also tried reloading the sim after that, but still no jetways. :/
virtuali:
--- Quote from: fahdriyami on November 26, 2018, 09:14:28 pm ---I tried rebuilding the cache. It took 55 seconds, then nothing.
--- End quote ---
"nothing" is strange. You either got a message saying the cache regeneration completed successfully, or a message saying the cache rebuild was a failure.
"nothing" looks like you have a corrupted .BGL file somewhere, one that might cause the program to crash, because it's corrupted. Or, possibly, the usual antivirus interference, which is hard-blocking the program from accessing the .BGL file, just because the antivirus thought it was smart to do that...
Try to configure the antivirus to exclude the whole simulator folder and, if you have sceneries installed outside the simulator, add their folders to the antivirus exclusion list as well. Don't worry, you cannot catch virus from sceneries, and disabling all their folders will result in the sim starting up faster, and GSX rebuilding the cache *much* faster as well.
CosmicWanderer:
No I mean it said cache rebuilt successfully in 55 seconds. By nothing I meant that no jetways appeared after that.
CosmicWanderer:
If anyone is having this issue as well, here is how I managed to fix it:
I loaded the airport, and start editing a parking spot. After saving the changes, I went back to C:\Users\User\AppData\Roaming\Virtuali\GSX and saw a newly created ooms-RANDOMLETTERS.ini file. I then opened the ooms-xujqjb.INI file provided here, and copied its contents into the newly created .ini and now all the jetways are showing up.
The only difference I could find was the first line of each ini. The ini provided here pointed to a "OOMS_ADEX_ADE.bgl" file, while ini created by GSX pointed to a "AFX_OOMSP3D.bgl". That might have been the reason. I can only guess.
I'm assuming OP was using the FSX version, while I was using the P3D release of the airport, which uses a different BGL file.
virtuali:
--- Quote from: fahdriyami on December 05, 2018, 02:54:17 pm ---The only difference I could find was the first line of each ini. The ini provided here pointed to a "OOMS_ADEX_ADE.bgl" file, while ini created by GSX pointed to a "AFX_OOMSP3D.bgl". That might have been the reason. I can only guess.
--- End quote ---
Of course it is.
Each .INI file is tied to a specific AFCAD name, the one used by whoever made the .INI configuration to begin with. An .INI will be loaded only if the AFCAD name in the .INI matches the one currently in use in the sim.
This in order to allow multiple .INI files for the same airports, with the correct one always being loaded.
If we didn't do this, you could (for example), load an .INI made for a default airports when you have a 3rd party airport loaded, surely causing a big mess of mismatched gates and jetways.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version