FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: tkemp66 on October 04, 2018, 08:00:01 pm
-
First of all I love the new features of GSX v.2 and still trying to figure it out. As far as I can tell, it works fine with all default airports and 99.99% of 3rd party airports...except for KBOI by SceneryBuilders. I just purchased ad installed it today but cannot figure out this problem. I sent the developer a report on the issue and is awaiting their response. In the main time I thought I would check here to see if someone have an idea how to resolve. I currently own ORBX Global, Vectors, FTX, Open LC North America and all of the Regions including FTX CRM (Central Rocky Mountain), and FS Global, and pretty much all of your US airports except KDFW. I have attempted numerous configuration including disabling FTX CRM.bgl for KBOI, which incidentally, realigned the jetways with the airport, but unfortunately, also left sink holes around airport. Please note that each time I made a change to scenery, I re-ran make runways, FSDT Live update, and also FTX Global Vectors. Nothing seems to work.
Any help is appreciated. Thanks
Troy
-
Well it looks like the developers only suggestion was to disable KBOI blg files under ORBX. This only made things worse. So I'm hoping this is the right place to find help on fixing my issue with the floating Jetways at KBOI. Thanks
Troy
-
Funny you posted this today - I did as well: http://www.fsdreamteam.com/forum/index.php/topic,19207.0.html
Issue seems to also affect some default airports while others aren't affected. Hoping to hear an answer.
-
Well it looks like the developers only suggestion was to disable KBOI blg files under ORBX. This only made things worse. So I'm hoping this is the right place to find help on fixing my issue with the floating Jetways at KBOI. Thanks
Exactly, if you have OrbX vector, disable the airport in their AEC utility. Please explain what do you mean with "made things worse". Do the jetways go back to ground ?
-
His suggestion was to "delete 4-5 files that comes up from searching for KBOI under F:\Prepar3D v4\ORBX, which is where I have P3dv4.3 installed. The four files that came up were a ABP_KBOI.bgl, ADE_FTX_CRM_KBOI_Boise_Air_Terminal-Gowen_CVX, ADE_FTX_CRM_KBOI_Boise_Air_Terminal-Gowen.bgl, FTX_CRM_objects_KBOI_PLC. Instead of deleting them, I just turned them off by adding .OFF after BGL. Doing so created elevation issues over the entire airport and surrounding areas of the city. If I turn OFF only the first two files, everything goes back into their normal place except your Jetways.
Troy
-
The other thing I noticed, is that your jetway numbers are wrong. The ones on the terminal are correct. If there was only an option to customize the jetway to MOVE DOWN, that would be nice. Is there any way to remove your jetways from this airport?
There is one thing I forgot to mention. The default jetways for this airport was automatically replaced by your jetways. I was never given an option to configure it. Perhaps maybe uninstalling GSX and KBOI, then reinstalling KBOI then GSX might work. I'll try that
Troy
-
I uninstalled GSX, disabled KBOI 3rd party airport, re-ran make runways and vector and the default KBOI loaded up fine. I then re-enabled KBOI 3rd party airport, re-ran make runways and vectors again and KBOI 3rd party airport looks fine. This is without GSX installation....See image
Stay tuned for GSX installation...
Troy
-
After GSX install...Not Good :'(
Hopefully you guys an help because I certainly do not know where the problem lies.
Troy
-
Well it looks like the developers only suggestion was to disable KBOI blg files under ORBX. This only made things worse. So I'm hoping this is the right place to find help on fixing my issue with the floating Jetways at KBOI. Thanks
Exactly, if you have OrbX vector, disable the airport in their AEC utility. Please explain what do you mean with "made things worse". Do the jetways go back to ground ?
Can you do me a favor and see if KBOI exist in vectors AEC in your ORBX folder please?
Troy
-
I still need help with this issue. GSX does not work at this airport and I'm sitting in limbo. KBOI airport does not exist in Vectors AEC, so there is no way to disable whatever it is I'm suppose to be disabling. Based on ORBX website, not all airports are available in vector. What I do know is that the default KBOI works fine with GSX but when GSX replaces the jetways for this third party airport, GSX jetways are placed on the roof, with the incorrect gate numbers. I need help..
Troy
-
Could be you have another altitude-correction AFCAD for this scenery under Scenery\World\Scenery ?
-
The only thing I have is (ADE_FTX_CRM_KBOI_elevation_adjustment.BGL). This is part of ORBX Central Rockies region. I also disabled it to see if it would make a difference but it didn't.
Troy
-
BTW, I ran FSDT updater yesterday and today and still the same issue
Troy
-
I had this problem at MROC. Here's what I did. I made a very basic AFCAD using the software from the link below. Because of ORBX the airport is shown to be at 2997 feet, approx. The default in P3D V4 is 3021 feet. GSX reads the default so the gates appear up high. I did not like disabling the AEC file in ORBX because the airport gets messed up in the North America LC from Orbx. By creating my own basic AFCAD and resetting the altitude to the Orbx altitude, GSX now reads the new AFCAD and puts the gates at the correct altitude. I think this is the best way to do it.
http://www.scruffyduck.org/airport-design-editor/4584106799
Lee
-
GSX reads the default so the gates appear up high.
GSX reads both files now, including the elevation correction .BGL. But the issue is, it seems the ones from OrbX are placed in a very low layer, just above the default terrain, but BELOW all the airports.
Since GSX respect the Scenery Library layer priority, it will give the default airport an higher priority, because it HAS an higher priority so, whatever altitude it read from the OrbX altitude correction .BGL, will be overwritten by the altitude set in the default AFCAD, which DOES have an higher priority.
I though it seemed weird to have an altitude correction file below the airports, but another user asked on OrbX forum, and they replied this is the way it should be.
Now, your report seems even more puzzling because, what you did, was to create *another* altitude correction file, not unlike the ones from OrbX, but you placed on an higher level and, sure enough, GSX read its altitude, and everything's working fine.
So, I now wonder why OrbX asks to have their altitude correction files below the airports, since yours works fine. Is your file able to fix issues like the plateau effect on airports with sloped runways ?
-
I set my new AFCAD to the ORBX altitude of 2997 feet as opposed to the default which is 3021. GSX reads that new AFCAD fine and the gates appear fine at the correct level. I'm not a master AFCAD maker, I just did it as an experiment and was pleased to see it worked.
Lee
-
I set my new AFCAD to the ORBX altitude of 2997 feet as opposed to the default which is 3021.
Sure, that's what I said, you basically created a duplicate of the OrbX correction file, just on an higher layer so GSX could read it.
That's why I was wondering if it's really required for these altitude correction files to be lower than airports (possibly AI are involved), and if the file you made shows any visual problems to the mesh around.
-
So, I now wonder why OrbX asks to have their altitude correction files below the airports, since yours works fine. Is your file able to fix issues like the plateau effect on airports with sloped runways ?
Thanks for your suggestion. I managed to create a new BGL file with elevation correction that matches the airport elevation in ORBX, but I still did not see any difference. I read through instructions which suggested that a new BGL would be created and placed into scenery/world/scenery, and I confirmed that it is there. However, the instructions never mentioned anything about what to do with the original BGL file for that airport. Am I suppose to disable it?
Troy
-
I'm done with this third party airport. I'm removing it and going back to the default, when GSX v2 worked. The developer was no help and pretty much ignored me. Stay clear of them.. This airport is NOT compatible with GSX: https://www.fspilotshop.com/fsx-p3d-scenery-kboi-boise-air-terminal-gowen-field-for-fsx-and-p3d-p-7328.html
Thanks for all your help.
Troy
-
I can just confirm that moving the ORBX AEC file on top really does not work (I am not entirely sure why). It skrews everything in a strange way - taxiways and terminals (and also GSX gates) are at the original (before AEC) altitude, wheras the grass between them in the "AEC" altitude.
-
I had this problem at MROC. Here's what I did. I made a very basic AFCAD using the software from the link below. Because of ORBX the airport is shown to be at 2997 feet, approx. The default in P3D V4 is 3021 feet. GSX reads the default so the gates appear up high. I did not like disabling the AEC file in ORBX because the airport gets messed up in the North America LC from Orbx. By creating my own basic AFCAD and resetting the altitude to the Orbx altitude, GSX now reads the new AFCAD and puts the gates at the correct altitude. I think this is the best way to do it.
http://www.scruffyduck.org/airport-design-editor/4584106799
Lee
Im really confused on how to create JUST an AFCAD, in ADE it seems it wants to recompile the entire airport? if you have the time can you walk me through how you did that? im struggling with Default KSTL. With Orbx AEC enabled for KSTL the Jetways are above the roofs, with AEC disabled they are floating still but lower than before... very frustrating :D
-
Umberto,
What could be the reason I am getting no jetways in this airport?
I have only ORBX Global & LC installed.
-
I had to do that with several airports after I installed ORBX LC but found that also VECTOR changed the elevations that several airport AFCAD's rested upon (that is why that file is below the AFCAD). I had two choices: first was to find out if ORBX had its own designed airport AFCAD. If so, I normally found it easier to disable it (change BGL to OFF) in the ORBX directory. I found, however that disabling any of the elevation BGL's for an airport caused major distortions in the airport and the scenery. So the only solution was to load the default airport into ADE (scruffyduck). I then loaded a default 737 and set it on the runway of that airport. I know that the elevation top menu line reads 10 ft above the airport elevation. So I loaded the default airport into ADE and in ADE/tools menu I selected "change airport reference data" and set the new corrected airport elevation. I then saved and compiled my corrected airport. Compiling it placed it in "addon" scenery file so it was now above the original default. After restarting FSX all my scenery elements at that airport appeared to be in sync since GSX2 reads that top most AFCAD.
The key is that you don't have to "create" a new airport, just load the default, change the field elevation in the AFCAD, and then recompile it. Now, I have FSX, but the same technique hopefully will work equally well in P3D.
Craig
-
OK I can confirm I have no issues with KBOI 3rd party airport.
For some reason there were no jet-ways when adding the scenery in the scenery library AFTER launching the sim. Not sure why...
However when adding the scenery prior to launch the jet-ways appear perfectly.
Shom
-
All the information about creating a new altitude correction file found in this thread are now obsolete since the Nov. 2nd Live Update, which allows you to override the altitude in the GSX scenery customization page so, there's no need to disable the airport in AEC (if you have Orbx Vector installed) or to create an altitude correction .BGL anymore.