Products Support > GSX Support FSX/P3D
No exclude radius checkbox at FlyTampa EHAM
virtuali:
--- Quote from: Flying Dutchman on January 05, 2021, 09:45:27 pm ---So making an exclude file seemed a piece of cake now, but not. I got an error message (see screenshot). The compiler was searching for a .bgl file in stead of a .xml file to compile to a. bgl file.
--- End quote ---
I don't understand that error, nobody ever reported it before. Try to remove both the XML and the BGL from the Fsdreamteam\Exclude and Fsdreamteam\Exclude\Scenery folders, and do it again. The XML is created after you act on at least one "Exclude Radius" checkbox so, to force it to recreate it again, click twice, then press Apply to save the changes, exit the sim, WAIT for it to close, open the GSX Control Panel and see if you have an .XML file waiting to be compiled and compile it.
Flying Dutchman:
Umberto,
Very friendly of you to reply, but as you can see in my reply to Kevin, I have already found a workaround:
Rename ft_jetwayLib.LOD.bgl > ft_jetwayLib.LOD.off. The manoeuvrable jetways don't show up.
Rename jets_static.bgl > jets_static.off. The static jetways dont show up.
Start P3D (P3D5.1 in my case)
Open GSX customize airport position.
Check the checkbox 'exclude jetway radius'. Neccessary in order to be able to select a new jetway later on.
Apply. Compiling is not desired.
Select all airport positions with jetways (77).
Select a new jetway, suitable for the EHAM bridges. No bridge (default).
Apply.
Quit GSX customize airport position.
Now I have replaced the default jetways at 77 airport positions by a new, better working SODE jetway. Unfortunately, I had to do this 5 times, because FlyTampa EHAM has 5 .BGL files (4 wind directions and 1 for all wind directions).
I understand that you would like to have more insight in my error message, but I hope you will understand that I will not change my customization again, now I have the situation that I was aiming at.
Captain Kevin:
--- Quote from: Flying Dutchman on January 07, 2021, 02:27:25 pm ---Now I have replaced the default jetways at 77 airport positions by a new, better working SODE jetway. Unfortunately, I had to do this 5 times, because FlyTampa EHAM has 5 .BGL files (4 wind directions and 1 for all wind directions).
--- End quote ---
Unless you are constantly changing the runway configuration, why are you even doing this. I'm more so wondering why you're constantly changing the runway configuration in the first place.
Flying Dutchman:
--- Quote from: Captain Kevin on January 07, 2021, 10:34:18 pm ---Unless you are constantly changing the runway configuration, why are you even doing this. I'm more so wondering why you're constantly changing the runway configuration in the first place.
--- End quote ---
Hello Kevin, good question. Sometimes you are doing things without realizing anymore why you do them. It's a routine that I execute for many years, originally intended for preventing AI aircraft to use runways that don't meet the wind directions of that moment and therefore cause chaos at the airport. I remember that using this routine, the chaos was over.
But due to your question I was rethinking about this routine. I use a third party ATC add-on (VoxATC) that control all AI aircraft. So why should they use runways not in use? So I decided to execute an experiment. Set the surface winds at 260 degrees, 10-20 knots. Logically runway 27 should be used for departing traffic and runway 24 for arriving traffic or the other way around. This is what I noticed. ATIS stated runway 27 as departing and arrival runway. When I use tower view / have a look on my moving map, I can see that all departing and arriving aircraft are using runway 27.
So, you're totally right. There is no need at all to change AFCADS and indexing for each flight. Thank you very much for this wakeup call.
Captain Kevin:
I've never used VoxATC, so I don't know how it works. I normally fly on VATSIM, so at that point, the runway configuration is irrelevant because the only other traffic around is other people who are flying, so they go where they want.
Navigation
[0] Message Index
[*] Previous page
Go to full version