Products Support > GSX Support FSX/P3D

No exclude radius checkbox at FlyTampa EHAM

(1/2) > >>

Flying Dutchman:
I want to replace the default jetways at FlyTampa EHAM by SODE jetways, but I don't see the exclude radius checkbox on the GSX customization page (see screenshot).

I studied the manual on this subject thoroughly. I read the post (http://www.fsdreamteam.com/forum/index.php?topic=18372.msg127769#msg127769) and viewed the instruction video (that uses FlyTampa EHAM as example!!), I read other posts on this subject and saw instruction video's on YouTube. But I don't see the checkbox. I tried with one of 5 bgl files (south) and the allround bgl.file (allrunwaysopen.bgl), but that doesn't make any difference. Why don't I see this checkbox, whereas it can be seen in your instruction video about FlyTampa EHAM?

I apologize for not having found the answer on this forum (if it should be there).

Hans Hartvelt
The Netherlands

virtuali:

--- Quote --- but I don't see the exclude radius checkbox on the GSX customization page (see screenshot)
--- End quote ---

I can see it right there, in the screenshot you posted. It's just the menu has way more options now compared to the one in the video tutorial, so the "Jetway Exclude Radius" check box has been moved up to make space for other options, but it still works the same.

Flying Dutchman:
Umberto, thank you very much for replying.

You're right. When I look closer I do see the checkbox at another spot in the screen. Because the tutorial video's that I saw showed the checkbox at the bottom of the screen, I haven't look further and concluded that there was no checkbox.

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.

Nevertheless, I could make a new jetway on page Jetway 1. But because the default jetway is still there also, I now have two jetways. The only action I can take is to select 'no jetway' on the parking page. Then the new jetway is not visible anymore, there's only the default jetway that also still works. I also have removed the exclude.xml file.

I'm afraid I made a mess of the scenery. :-[. How can I restore the original situation and how can I make a correct exclude file?

Captain Kevin:

--- Quote from: Flying Dutchman on January 05, 2021, 09:45:27 pm ---Nevertheless, I could make a new jetway on page Jetway 1. But because the default jetway is still there also, I now have two jetways. The only action I can take is to select 'no jetway' on the parking page. Then the new jetway is not visible anymore, there's only the default jetway that also still works. I also have removed the exclude.xml file.

--- End quote ---
The exclude jetways doesn't touch the jetways for third party scenery. With the FlyTampa EHAM scenery, if you go into the scenery folder, there should be something like jetways.bgl (I don't have access to my computer at home, so don't remember the exact name), move that out of the scenery folder (I would just leave it in the main EHAM folder, that should get rid of it.

Flying Dutchman:
Hello Kevin, thank you for replying.


--- Quote from: Captain Kevin on January 06, 2021, 01:10:42 am ---The exclude jetways doesn't touch the jetways for third party scenery.

--- End quote ---

That's strange. In their 'how to replace default jetways by SODE jetways' instruction video, Vituali uses FlyTampa EHAM as an exemple how to accomplish this. And that's exactly the airport where I want to replace the jetways. So I see your suggestion as a useful workaraound. Thanks for that anyway.


--- Quote from: Captain Kevin on January 06, 2021, 01:10:42 am --- With the FlyTampa EHAM scenery, if you go into the scenery folder, there should be something like jetways.bgl (I don't have access to my computer at home, so don't remember the exact name), move that out of the scenery folder (I would just leave it in the main EHAM folder, that should get rid of it.

--- End quote ---

I found 3 files regarding jetways:
ft_jetwayLib.off
ft_jetwayLib.LOD.bgl
jets_static.bgl

The second one concerns the manoeuvrable jetways and the third one the static jetways. I renamed them both .off. And yes all jetways are gone. I choose a nice new one and implemented that one on all exits.

So I realized what I wanted, however in another way. Thanks again for helping.

Navigation

[0] Message Index

[#] Next page

Go to full version