FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Ray Proudfoot on May 30, 2015, 10:25:15 am
-
SimWings have just released La Palma - GCLA. Unfortunately GSX vehicles are slightly sunk into the ground and their wheels are not visible.
Is a fix possible?
-
It seems like a problem of the airport elevation in the scenery AFCAD not matching the actual elevation of the airport, probably because they don't have a better way of solving the problem of ground flickering when doing the scenery ground as a 3d model over a platform, which is what we also use for our own airports, but without inserting the wrong elevation value in the AFCAD, because we have other methods to solve ground flickering.
There was a similar issue with Madeira, which had the altitude in the AFCAD set 9 meters *below* the real one, just that with this one, they made the altitude difference a bit less, so it's not enough to give the impression that GSX vehicles "disappeared" because of some kind of GSX problem, but enough to sink their wheels.
We think the elevation in AFCAD file should be always as correct as possible, because it won't affect "just" GSX, but potentially any other addon that needs to read the AFCAD for any reason, and there are other ways to prevent ground flickering of native 3d FSX scenery over a platform without having to resort to such tricks ( KDFW, CYVR, JFK V2, and all our airports that have 3d taxiways have their ground made as 3d model over a platform, but the elevation in the AFCAD is the correct published one ).
But in any case, GSX being the flexible program that it is, can be easily updated to add an "Elevation override" in the airport customization, so it will be possible to tell GSX to ignore the AFCAD elevation and use a different one, and that will be available as an FSDT-provided airport customization (at least for these two Aerosoft airports that are well known to have this issue), AND as an user customization option in the scenery .INI file, so new airports that will eventually released in the future that will still use this method, can be added even without our support.
In fact, it's one of the things we were already working on, and will likely appear in the next major upgrade, which is currently in Public Beta.
-
Hi Umberto,
That's excellent news, thanks. I hadn't appreciated GSX was so versatile. Looks like you have created a real masterpiece! I look forward to its release. :)
I can certainly live with the visual anomaly for the time being.
-
my solution for the problem. deactivate Stock Airport La Palma APX43210.bgl. So GSX works well.
-
I've edited my message, because the situation at Madeira (not sure about La Palma, but probably is), is really different.
The Madeira AFCAD is correct, it's just a bit unusual because, since the airport is sloped, and in reality one runway end is about 44 meters and the other is 58 meters, with a published elevation of 58.5 meters, the AFCAD has been set to 50.5 meters, which is somewhere in the middle.
Sloped airports are really a mess in FSX, so I can understand the design decision, we do the same with sloped airports, although we usually set the whole airport to the published elevation, rather than using an average value.
The problem with GSX at Madeira is likely caused by the fact the airport is "hollow" under the AFCAD, to simulate the runway which is like an highway bridge, so the terrain below is entirely flattened down.
We made several raised taxiways in our airports, but we never removed a section so large, so we still have the mesh underneath at the proper altitude, so the vehicles can pass on it without falling down, because they are considered to be "on ground".
I guess we'll just have to update GSX to position the vehicles using absolute positioning about Sea Level, instead than AGL, which might even easier to do, since it won't involve having to add an option to override the AFCAD which, at least in this case, is not the issue.
-
Hi Umberto,
In regard to La Palma is A320 User's solution one you would agree with? My only reservation is that airports other than GCLA might be affected.
-
here my result.
-
Any News for the User they did not use my way.
-
I suggest to wait for a proper fix, so that GSX will support those "hollow" airports with no terrain underneath.
-
But in any case, GSX being the flexible program that it is, can be easily updated to add an "Elevation override" in the airport customization, so it will be possible to tell GSX to ignore the AFCAD elevation and use a different one, and that will be available as an FSDT-provided airport customization (at least for these two Aerosoft airports that are well known to have this issue), AND as an user customization option in the scenery .INI file, so new airports that will eventually released in the future that will still use this method, can be added even without our support.
In fact, it's one of the things we were already working on, and will likely appear in the next major upgrade, which is currently in Public Beta.
Has this been included in the latest update and if so how do we add this elevation override in the airport customization?
-
Has this been included in the latest update and if so how do we add this elevation override in the airport customization?
Not yet, sorry. When we'll add this, it will be indicated in the release notes.
-
Awesome thanks.
-
Hi, is this problem still active with the latest GSX? Thank you.
-
Hi, is this problem still active with the latest GSX? Thank you.
As in my last reply:
When we'll add this, it will be indicated in the release notes.
So no, it's not there yet, and it will indicated in the Live Update release notes when it will.
-
Umberto,
any news about this problem?
Thank you
Paolo
-
any news about this problem?
As I've said in my last reply:
When we'll add this, it will be indicated in the release notes.
So no, it's not there yet, and it will indicated in the Live Update release notes when it will.
-
Well, I suppose you are having a hard time to fix the issue, since this topic has been open for one year, now..
-
Well, I suppose you are having a hard time to fix the issue, since this topic has been open for one year, now..
We fixed this months ago, but because of the many changes we made to support all the new KMEM features, we cannot release it right now, but it won't be long now.