P3D v4 P3D v4.1 + ADE 1.75 + FSTramp question

[PhilK]

I am using FSTramp addon with my P3D4, and have noticed following, particularly when trying to modify GCRR / Lanzarote after a one week holiday there.
My modification was mainly just to reduce the size of the airport background, which is far too huge on both runways sides.
Using ADE, I opened the stock airport, then excluded the original background, set a shorter one, without changing the airport itself, saved and compiled the airport.
Whereas the airport(s) show correctly into P3D4.1 as well as in Little NavMap, it looks that FSTramp is no more showing in the map view window runways, taxiways and other elements. So I assume it is not decoding properly these elements. Might this be related to the new ID's mentionned in some other post on this forum?...

Checking further, I could find I have the same problem with an old ADEX data where I did recompile PASI to put the marinas back into the water after installation of ORBX Vector...

Problem reported to FSTramp support a few days ago, but no answer up to now.

Any advice or suggestion will be appreciated

Thank you for your help

 

[scruffyduck]

Runways and taxiways have a different file structure in P3D v4. This requires that applications needing to read airports created for that version and using that compiler will need to update the way that they read those elements. I would say this needs to be addressed by the FSTramp developers - I am sure you have checked to see if they have a recent update.

 

[PhilK]

Jon,
Thank you for your answer. I do have FSTramp latest version (7.0.2), and it displays without trouble all the stock airports layouts (question being were they all recompiled for the x64 opus?).
If for instance I just keep my own cvx file but the stock airport layout, I have no display problem (see encl.).
Only when I use an ADEP4 airport layout I get problems with FSTramp, whereas both P3Dv4.1 and LNM do display correctly.
So I understand that FSTramp is not decoding properly something, and I will contact again their support.
Would it be worth meanwhile trying to use a prior compiler than P3Dv4.1?
Thank you for your comprehension and assistance
Blue skies
Philippe

 

[scruffyduck]

Stock airports are generally not recompiled as far as I can tell so won't show this error. Airport compiled with compilers before P3D v4 should not show the error either but may have other issues displaying in P3D v4.

 

[PhilK]

Jon,
Thank you for the information. I have few 3rd party airports, not all active, but at present time I can tell that some ADEX bgl's are displaying pretty fine (at least for the moment...) whereas some ADE bgl's clearly do not show various elements into P3D v4.1.
Will look for answer back from FSTramp support, and/or will re-install some earlier SDK's.
Have a good day
Philippe

 

[Pyscen]

Installing earlier SDKs for P3D will NOT help... if you are running the latest (LM v4.1) then you need to stick with the latest SDK, as Jon suggested. You could run into more problems if you do!

 

[PhilK]

Well,
Just for testing purposes, I reinstalled last P3Dv3 SDK and used it to compile my .ad4 file for GCRR as collected from stock P3Dv4.1, and an ADEX bgl released by one of my VA members for PASI, where I further relocated marinas as per Google Map pictures (so might not be completely actual) to get them into the water with ORBX FTX Vector.
With this older compiler, both airports do show in P3Dv4.1, and are also displayed correctly (mean taxiways, runways, etc...) into FSTramp. The question is just how long will this trick work...
Blue skies