FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: diceflo on October 10, 2018, 05:44:45 am
-
So I installed GSX into P3DV4 because I have to if I want to see all the airports that I have bought. I have tried using this program before and I had floating jetways at all my default airports. I deleted it and the problem was solved. I reinstalled GSX today and the problem is back. I was told that I have to exclude them from global vector. I have run the aec tool but I still have floating jetways. What should I do now?
-
It's not clear from your message *when* you reinstalled. We posted a fix late yesterday which is supposed to fix this problem, which was caused by the OrbX altitude correction files, which are now recognized.
-
Probably right before you updated. With my luck, it would be understandable. I will run the live updater and report back.
-
Just to report that the jet ways are back. I ran the live updater and at first I didn't have any jetways at all. I thought to go into the GSX control panel and I clicked enable default jet ways and all is good. I did notice one thing. When I did have floating jet ways they were nice ones with the airport logo on them now I have default ones they just look plain (of course). So is there a way to have the nice jet ways that don't float? I did also disable default jet ways thinking I would have the other ones but I didn't have any at all.
-
So is there a way to have the nice jet ways that don't float? I did also disable default jet ways thinking I would have the other ones but I didn't have any at all.
If you still have them after the update, it means something is still not right with OrbX Vector compatibility. Which is the Scenery Layer for Vector in your system ?
-
I'm also still having this issue after the update. OrbxVectorAEC is at position 155/156 and FSDreamTeamExcludes is at 1.
-
I'm also still having this issue after the update. OrbxVectorAEC is at position 155/156 and FSDreamTeamExcludes is at 1.
The Fsdreamteam exclude doesn't have anything to do with this. What's important to know, is if Vector is higher or lower in priority than then the AFCAD of the airport it's supposed to correct.
-
Lower, it's at the bottom of the list just above Default
-
Lower, it's at the bottom of the list just above Default
That's explains it. GSX always respect the layering order so, if a .BGL sets an altitude, but another one on an higher priority sets a different one, GSX doesn't have much choice other than trusting the one which has the higher priority.
Have you tried asking OrbX is these altitude correction files are supposed to have such a low priority ?
-
I'll post over at FTX and see what they say.
-
FTX confirms that the low priority is intended.
-
FTX confirms that the low priority is intended.
That would be a problem, in fact. We do recognize the files but, the general rule has always been to choose the .BGL that has the higher priority in the Scenery Library, we would have to do some kind of exception in this case.
For the time being, just disable the airport in the AEC utility, until we can come up with a better automatic way.
-
Hi! I have similar problem. In default BIKF, I have normal default jetways, but abnormal SODE jetways( floating above the ground).
I have up-to-date GSX (by FSDT live update), default jetway set to active by GSX control panel, and latest version of makerwys. I have installed ORBX Global but no Vector.
This so far only happens only in BIKF, not in other airports.
Oh, and I have to mention that there is no terminal at where those SODE jetways are. Weird....
Any solution? Thanks so much!
-
Oh, and I have to mention that there is no terminal at where those SODE jetways are. Weird....
That seems GSX is not the only one affected by whatever file is changing the altitude. It's likely the terminal ended up below or above ground.
-
any NEWS about the floating SODE jetways in BIKF ?
-
any NEWS about the floating SODE jetways in BIKF ?
There are no floating jetways in the default BIKF so, in order to understand what the problem might be on your system, you should tell more about which addons you installed.
Do you have OrbX vector ? Have you disabled the airport in the AEC utility ?
-
I have Installed ORBX Vector (p3dv4) - and BIKF is disabled there !
With default jetways , all is ok - jetways on ground....
...but activating the Sode jetways via gmx-tool the 'SODE'-jetways are floating over the ground... !?
greetings
ggerolamo
-
I have Installed ORBX Vector (p3dv4) - and BIKF is disabled there !
Then you must have another scenery in conflict that has changed the altitude for the airport, which is causing the same effect as Orbx vector.
As I've said, this doesn't happen with only the default scenery installed so, it must be some addon you installed that has added a new AFCAD that has a different altitude AND it stays on a higher layer in the Scenery Library, so GSX correctly reads the altitude from there, it cannot possibly know if it's correct or not.
-
There is imho no other scenery !
Is there a possibility to see which scenery-file gsx is using calculating the height of the SODE jetways ?
-
There is imho no other scenery !
There is, otherwise the same problem would happen with default scenery. But I tried loading default BIKF, and jetways don't float here.
Is there a possibility to see which scenery-file gsx is using calculating the height of the SODE jetways ?
Not at this time, we'll have to add this as a diagnostic option and, eventually, an option to override the altitude.
-
Not at this time, we'll have to add this as a diagnostic option and, eventually, an option to override the altitude.
...would be a cool feature to adjust the altitude...I'm looking forward to it !
Meanwhile I obviously have to switch back to default Jetways...
-
I also have floating Jetways.
On Saturday I loaded up a flight in P3Dv4.3 with the Aerosoft Airbus A320 at the default KDEN.
When I operated the jetway, it docked too high and missed the Airbus forward door. I checked the jetway wheels and they were floating approximately 1 foot off the ground.
When the passengers boarded, they were at the correct level and I could see their feet below the jetway floor.
I loaded another default airport (KCOS) and all the jetways were 1 foot off the ground.
I loaded my only add-on airport: UK2000 Heathrow and the jetways wheels were on the ground.
I saw some posts saying disable the airport in ORBX elevation corrections but when I done this, the KDEN jetways went 100 feet in the air.
Things I done that may have broken the jetways elevation: Ran FSDT Live Update, Windows Update and Installed new Nvidia drivers.
-
Please read again my last post:
If you disable the airport in the AEC utility, and you still have floating jetways, then you must have another scenery in conflict that has changed the altitude for the airport, which is causing the same effect as Orbx vector.
As I've said, this doesn't happen with only the default scenery installed so, it must be some addon you installed that has added a new AFCAD that has a different altitude AND it stays on a higher layer in the Scenery Library, so GSX correctly reads the altitude from there, it cannot possibly know if it's correct or not.
Ran FSDT Live Update, Windows Update and Installed new Nvidia drivers.
That's precisely the reason why you have this. Our latest update tried to FIX this, and now it reads altitude corrections files too, that didn't read before. But, of course, it cannot possibly know if they are correct or not, and it must respect the Layering priority, since it cannot possibly know when use the opposite layering priority.
Basically, it's a problem that cannot always be solved automatically.
That's why I said in the next update, you'll have the ability to override the altitude in the GSX customization page.
-
Also have floating Jetways at YMML. I have ran Orbx vector include an exclude with no result.
-
Also have floating Jetways at YMML. I have ran Orbx vector include an exclude with no result.
The last post was a month old. The current version, as promised, DOES have the ability to correct the Airport Elevation, without having to exclude anything.