FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Juergen2 on July 08, 2018, 12:37:59 pm
-
Hi,
As of lately when I load an A/C at an airport gate, pres CTRL+F12 the only menu I get is : Select parking facility at "airport" (1/2). Since I want to use the "GSX - Active Ground Services" menu for loading and push back, I am forced to use the FSX-SE pushback feature.
I also noticed, that after a flight and engines shut down (turn around state) the same parking facility menu shows up. If I than warp to a different parking position, I get the "active ground services" menu.
Thanks for suggestions
Juergen Mader
-
Hi,
I have the same problem after updating to P3D v.4.3 from v.4.2.
The problem is exactly as described by Juergen above. But when I run the GSX "Warp me there" tool my planes are placed either far behind the gate position or in some obscure spot far away from any parking facility.
I can see Juergen runs FSX:SE but it is eye-catching how similar the two problems are.
I cruised around in my airport library but can't find any airport where GSX actually can identify the stands/parking spots and that goes for the P3D standart airports as well.
What's strange for me here is, that I have never ever had any serious problems with GSX in all those years I've used the app so for me this is one of those "A ha" moments I guess.
I hope you guys can help us.
Greetings,
Jan
-
Hi again,
I have solved the problem for what concerns my system and first: It has nothing to do with upgrading from P3D v.4.2 to v.4.3!
In short: I use the new Just Flight Traffic Global Early Acess trafic app. The app placese two entrys in the P3D scenery library. The one entry is named "AirportFacilities". Dispite the fact that this entry is placed way down in my P3D scenery library hierarchy, on my system it obviously can mess around with other add-ons and apps like GSX.
So what did I do: I simply removed the "AirportFacilities" entry and abracadabra GSX can find the all gates and parking spots again.
As far as I can see the only "set back" is that Traffic Global gains more massive traffic in some airports.
So Juergen if you are a Just Flight Traffic Global user this might be the answer to your problem.
Sorry guys about all rumble.
Greetings,
Jan
-
This has been explained so many times on the forum. Whenever you see GSX not loading the correct airport, it's NEVER a GSX problem, and it's ALWAYS a problem of scenery conflicts, and AFCADs supplied with AI Traffic products are the most common source of scenery conflicts.
Such AFCADs are meant to be used only as a replacement for default airports but, if you have an add-on airport, they should NOT be used.
Since GSX respects the layering order, you must be sure the Scenery Areas of your add-on airports are all on an higher layer than the AI Traffic product layer. But sometimes this is not enough, and such conflicting AFCADs must be removed manually.
-
Hi Umberto,
Thanks for the reply.
I use UTLive for AI traffic, and also downloaded scenery (airports) from AVSIM.
It could very well be that the airports (scenery) I downloaded from AVSIM are causing the problem. I don't quite understand the "order" and "higher layer" as well as AFCADs not be used with add-on airports you mentioned. Is there a more detailed explanation that I can follow, to check out this problem?
Thanks for help
Juergen
-
GSX will tell you the name of the AFCAD in use in the parking customization page. This will help you identifying the conflicting AFCAD.
-
Hi Umberto,
I found the entry at the airport in question:
KLAS; there is 1 (one) AFCAD "APX17190.bgl".
What do I do now (I understand this might be trivial, but I never had to correct anything there).
Thanks for help
Juergen
-
I found the entry at the airport in question: KLAS; there is 1 (one) AFCAD "APX17190.bgl".
You mean GSX is telling you is using the airport ? If yes, if you don't have an addon airport for KLAS, that seems to be right.
-
Umberto,
I don't have a purchased airport for KLAS, but I downloaded a scenery for KLAS from the AVSIM library.
Is this considered a Add On airport?
Thanks
Juergen
PS: again trivial, but important for me to understand
-
Umberto,
I trie another airport KBOS and the same problem occured: No GSX menue, only runway options. So I checked in the parking customization page and it gave me the AFCAD used (APX29160.bgl). Again, there is only 1 (one) .bgl listed.
Thanks for help
-
Umberto,
I did another flight from Miami: same downloaded scenery from AVSIM -NO Problem-
So what could I check at these affected airports?
Thanks
Juergen
-
It's possible these downloaded sceneries has been rejected because they are too big to be AFCADs. If can be sure of this, by enabling Logging in the Troubleshooting section of the GSX Settings, and choose "Restart and rebuild the airport cache" in the Couatl menu.
After the cache has been rebuilt, exit the sim and check the log file at %APPDATA%\Virtuali\Couatl.LOG, if it says some files has been rejected because they are too big, you can change the default threshold size for rejection by setting the airportCacheMaxBGLSizeBytes paramenter in the %APPDATA%\Virtuali\Couatl.INI file, as explained here:
http://www.fsdreamteam.com/forum/index.php/topic,13489.msg100092.html#msg100092
-
Hi Umberto,
I performed the Couatl restart as per instructions, but I can't find a log file which was supposed to be created. There is a couatl.err file; a couatl configuration setting file and a couatl text document file.
So I opened the text document and all it says is: LogFile="C:\User\Juergen\AppData\Roaming \Virtuali\Couatl.log". see screenshot:
https://www.flickr.com/photos/141330124@N05/shares/X77b61
If this is the generated log file, there are no entries.
Normal????
Thanks
Juergen
-
couatl text document file.
In you screenshot, I can see TWO so-called "text documents", a smaller one (1KB), which is the one you opened, which is in fact the Couatl.INI file, which configures the log file to be created, and another larger (16KB), which I guess IS the Couatl.LOG file you were looking for.
If you enabled the option to see the complete filename with extension (highly recommended), this would have been more obvious.
-
Hi Umberto,
1st: Thanks for the file extension tip (I wasn't aware of this!)
2nd: Can you help me with the log file to see whats wrong on my system?
Thanks
Juergen
-
2nd: Can you help me with the log file to see whats wrong on my system?
As I've said in one of my previous posts, I need to see a .LOG file made after you select the "Restart and rebuild cache" option, otherwise we'll never know if a file has been rejected for some reason.
-
Hi Umberto,
Here is the log file I just created after a Couatl rebuild/restart.
Thanks for patience
-
As the log says, GSX has skipped several airports because they are unusually large for being AFCADs.
In order to speed up the cache rebuilding time, GSX automatically skips .BGLs larger than a certain size (1.2 MB by default), because usually AFCADs of default sceneries and commercial sceneries are much smaller.
However, some freeware authors don't conform to such standard, and have the habit of putting extra things like textures inside the airport .BGL (instead of keeping the airport data separated from the rest of the scenery), which result in files larger than that.
It's possible to raise this threshold in GSX, by setting the airportCacheMaxBGLSizeBytes in the Couatl.INI file, as explained here:
http://www.fsdreamteam.com/forum/index.php/topic,17221.msg121243.html#msg121243
Of course, you'll have to do another "Restart and rebuild cache", after you set this parameter.
-
Umberto,
Thanks for speedy response. I will be out of town for a week. Upon my return, I will change the threshold and try again.
Thanks alot
-
I am very interested in what the outcome here was because I have the same problem, and I have followed all instructions to increase the bgl size (in the ini file) and rebuild the system. I am still getting nowhere with it...
Gary
-
Hi,
I finally got around to looking into the couatl.ini file and found out that there are NO entries other than:
"logFile="C:\Users\Name\AppData\Roaming\Virtuali\Couatl.log"
So I really don't know what's going on?
I guess I need some help
Thanks
-
I finally got around to looking into the couatl.ini file and found out that there are NO entries other than
Of course there aren't. If you want to change the default, you must CREATE that line yourself.
-
Great, but how do I know what the default value is; e.g. "airportCacheMaxBGLSizeBytes = 4000000"?????
And how do you increase the maxbgl file size in increments of 1000 or 10000 or 100000?
Again, thanks for help
-
That's very easy. Look the name of the files that has been rejected for being too bug in the Couatl.LOG, and set a value higher than the largest of these files.
-
Hi Umberto,
I looked at the log file and can't find any rejected files. It is mostly "missing one or more files" "No module named ...."skipped, likely too big to be an airport".
There is no file size associated with it.
Could you have a look at the log file and see if you can find rejected files.
Thanks
Juergen
-
I looked at the log file and can't find any rejected files. It is mostly "missing one or more files" "No module named ...."skipped, likely too big to be an airport".
I meant: rejected because they are too big to be an airport...I can see the ones under Addon Scenery surely looks like airports.
There is no file size associated with it.
There's isn't supposed to be any. To check the size, open the file location, and check it by right-click on the file, select Properties->Details.
-
Umberto,
Are you talking about these:
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\CYYC_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\EDDF_CW_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\EHAM_CW_RS.bgl skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\KBOS_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\KDEN_CW_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\KDFW_CW_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\KIAD_CW_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\KJFK_CW_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\KLAS_CW_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\KLAX_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\KSEA_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\KSFO_CW_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\KTPA_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\OMDB_RS.BGL skipped, likely too big to be an airport
File C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery\PHNL_CW_RS.BGL skipped, likely too big to be an airport
Folder C:\Program Files (x86)\Steam\steamapps\common\FSX\Addon Scenery\scenery processed in 0.019 seconds
thanks
-
Are you talking about these:
Yes, those are the ones under "Addon Scenery" which were rejected for being too big.
-
Umberto,
these addon scenery files are all between 3,200KB and 3,700KB. So the command in the .ini file should be:
airportCacheMaxBGLSizeBytes=400000
Would this be correct?
Thanks
-
these addon scenery files are all between 3,200KB and 3,700KB.
So the command in the .ini file should be: airportCacheMaxBGLSizeBytes=400000. Would this be correct?
Of course not. If you wanted to set it at 4MB (4,000KB), it must be 4000000. 4 millions = SIX zeroes.
-
Hi Umberto,
Of course you are correct, I wanted 4MB = 4,000,000 Bytes = 4,000KB. I forgot 1 zero.
However, I was also concerned about the syntax of that log file line.
Is it correct??
Thanks
-
However, I was also concerned about the syntax of that log file line. Is it correct??
Yes. And, in fact, if you read my replies on the linked thread I posted earlier, it included an example with PRECISELY the 4MB size you needed:
airportCacheMaxBGLSizeBytes = 4000000