• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Version 1.39 Feedback

That is interesting.

I checked my addon scenery folder and I only have the .bgl files for KCOS and KATL in there.

There is just the one file in there for KCOS. I also made sure addon scenery was set to the highest priority.

I'm guessing there is a problem with FSX reading the default scenery as well as the addon, since when I first created this .bgl from the stock I got the jetway problem.

I'm not sure how to go about troubleshooting this particular problem though.

Edit: I also forgot to mention that I recently just reinstalled FSX. That might have something to do with the problem.
 
Last edited:
spud88

I also see all the Jetways as per your attached bgl.

Do you have a bgl on your computer that adds an exclusion rectangle to KCOS? There are certain type exclusion rectangles that will stop the Jetways from showing.
 
As far as I'm aware there are none that I added myself. I reinstalled FSX about 2 weeks ago, and the only real modifications I have done are via ADE and some work with SBuilderX, although that is for a different airport altogether.

I haven't done any modifications to KCOS outside of this single ADE .bgl.

When I open the .bgl file directly from the addon scenery file I notice that ADE only adds exclusion polygons for the autogen and generic buildings, which I assume is normal.

I am able to see the jetways after I finished editing KATL, but not KCOS.

I also added a "ready-made" KATL scenery package that added files to the scenery/global/scenery folder and texture, but I have since removed all of them. I noticed that after I removed those files I was able to see the jetways at KATL.

When I make changes in ADE, I save the file in my working folder. I then check for faults and compile it into a .bgl. I then take that .bgl file and cut it from the ADE BGL folder and move it into the addon scenery/scenery folder in FSX. I make sure to delete the existing earlier .bgl for that airport before dropping in the new one.

I am also only using ADE 1.39. I'm not sure if there is any useful information in there, but that's all I have to go by. :confused:


Oh and I'm sorry for sort of derailing this thread :(
 
Last edited:
I stumbled across the FSX Airport Scanner program and ran it. It showed that the only file influencing KCOS was the .bgl that I dropped into the addon scenery folder.
 
Remove the KCOS from your addon scenery\scenery folder.

Place it in your FSX\Scenery\Global\scenery folder. Start FSX and see if the Jetways show up.

This will test your FSX scenery folder for possible read problems that occur sometimes with Vista.
 
Aye, If you remove the .bgl, the default airport has all the jetways and everything is perfect.
 
I've been brainstorming and trying to fix this problem for a while now. I sat down and racked my mind for any ideas and then it hit me...

I should see if there were any service packs for FSX. I ended up installing the two downloads available online.

And low and behold, I have jetways. :D I had to sit back and facepalm for not thinking of this sooner.

It might be a good idea,if you haven't already done so, to include somewhere in the readme for the 1.40 release a note stating you should have these service packs installed.

Thanks guys for offering your help. I figured it had to be a stupid fix like that since I'd exhausted every other option.

Just wanted to say again, that you guys have developed an awesome tool for FSX. Keep up the great work!
 
Jon/Jim:
I've been tinkering with the default CYUL and decided to add some transitions to the existing ILS's per the 2006 plates. For one of the transitions, I added a new T_WP and provided coordinates. I noticed the WP kept moving (the lat would adjust itself randomly) :confused: The ILS was 10 and the T_WP was created to smooth the transition from YUL to ALWAR.

Also, I was able to include the rotating beacon w/glow into an .ade file. When I compile, the beacon and lights show up at the airport now.
 
ADE 1.39 Beta with no jetway option?!?!

Dear Jon,

I am using ADE 1.39 beta, when I right click to add a jetway I cannot find it in the menu, I am doing it manually in the xml file that is generated. Is it something wrong that I am doing or is it really missing?

Thank you for ADE and for your precious time!!!

Jad
 
jaaz

make sure the "Gate" you want to add a jetway to is Highlighted,
then right click, Add and Jetway is the 5th object down,
if it already has a jetway it will not appear in the list, the jetway could be at another gate numbered the same
 
Ray is correct. You need to have a parking spot selected, then right click and the option to add a jetway should appear. ADE will not allow you to add a jetway to a parking spot that already has one - this is because the compiler will fail in this case.
 
Jon:
Another observation with 1.39 beta. When working on an airport (generic stock) and after many saves and compiles there comes a point when I can't add a library object by right clicking on the active screen. For some reason the obtion goes away. The work-around has been to exit (close) ADE 1.39 and reopen the airport with 1.39, then all is fine again.

kagazi
 
kagazi said:
Jon:
Another observation with 1.39 beta. When working on an airport (generic stock) and after many saves and compiles there comes a point when I can't add a library object by right clicking on the active screen. For some reason the obtion goes away. The work-around has been to exit (close) ADE 1.39 and reopen the airport with 1.39, then all is fine again.

kagazi
Click to expand...

Hmmm - interesting, I will take a look
 
just to add to kagazi's quote Jon,
I'm finding the longer i use v1.39, ADE is taking longer to save, not a problem with v1.37
but i do work on the larger airports which may be a reflection
 
Ray

It might not be the longer you keep ADE open but the amount of scenery your adding to the grid. Everything and anything will start to increase the opening of the airport, saving the airport and compiling the airport.

My WSSS has a huge amount of scenery, poly exclusions, LC, poly's, Roads and Vector Shapes for traffic if you have seen some of my screenshots. My .ade binary file is now a whopping 59,366KB's. That is probably the largest size airport to date for anyone and I have not had any problems with ADE.

My WSSS.bgl is 500 KB

As the file has grown in size over the last weeks the save and compile has increased somewhat proportionally. Even on this very fast highend computer my save time is exceeding 30 secs. Opening WSSS takes over 1 min before the Grid fills with the airport. Fault Finder is still very fast since Jon worked on it.
 
thanks Jim,
I do understand that, but i'm not adding much just the normal moving stuff around, alignment and gate assignments,
these airports are a lot smaller than KJFK i did with v1.37, and is taking twice as long to save and also the same when compiling the longer i have ADE open,
i realize the two programs are totally different so i have put it down to that,
i just notice it when spending half a day on each......
not a big problem really :)
 
Jon:

This is a posible little bug (since 1.37 version).

In the runway object -> Edit Object -> properties dialog box -> in Markings Tab the option "Edge Pavement" is not persistent.

I tray to check but the system don´t remember this check.

Best Regards

carlos
 
You must log in or register to reply here.
Back
Top