• 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.

Addon airports updated to V5

R

rjlfry

Messages
12
Country
unitedkingdom
When editing an FSDT airport with ADE 179 for V5 to only resize gates and gate codes for my AI, I found scenery bleed though from the default after re-activating the dev`s AFCAD it was OK, I was then informed by the FSDT dev that i should use ADE 175 v4 compat as the updated airport do not use the slopped runway SDK, I had un-installed P3Dv4.5 but luckily still had a v4 AFCAD BGL and it worked OK, now the problem without 4.5 installed ADE 175 will not work so any other dev that does the same will cause problems, if i just install V4 sdk will ADE 175 work.
Regards Ray Fry.
 
I have re-installed V4 SDK and have been able to get V4 ADE 175 working again no sim installed, this makes it possible to edit addon airport that have not updated the AFCAD in V5 addons without causing an issue.
 
I been forced to re-install P3Dv4 without it v4 ADE will not compile and FlightBeam and FSDT are still using the old V4 CAD files in the updated airport and you get default scenery bleed through if you use V5 ADE.
 
I am trying to understand what you want to do
 
When purchased P3Dv5 i like to edit my default airport CAD files so i downloaded the new ADE for V5, however it turns out that when editing my updated addon airport like FSDT and FlightBeam if you edit them just changing the parking codes and compiling with ade179, when replace the airport cad file and turn of the devs cad file in the sim you get default scenery bleed.
KORD in v5 edited with 179.
https://flic.kr/p/2jbK1Nw
https://flic.kr/p/2jbF1HF
Remove the ADE 179 and edit with ADE176 v4 and no scenery bleed all OK i found this when the FSDT dev informed me that FSDT airports in V5 do not use V5 updated cad slopped runways, and it appears the same with FlighBeam at KDEN i found the hanger was default scenery but when i edited with 176 again ok.
I suspect some have pushed out v5 updates so quick they are not using the v5 sdk.
 
I am not sure I understand that. Generally it does not make sense to me. ADE 1.79 behaves the same way as 1.76 for v4. Are you saying that somehow if you compile for v4 and install it in v5 that the default v5 scenery does not appear? But then you refer to problems if the v5 compilers are not used with v5
 
Last edited:
What i am saying is if you edit an addon airport with V5 ADE 179 then compile and use that AFCAD in place of the devs CAD you get default scenery bleed showing in the airport, if you use V4 ADE 176 this will not happen, check out my post on FSDT forums I thought it was a LM problem but the FSDT developer informed me not to use V5 ADE 179 as the cad file was still the V4 flat runway type. do you get what i am saying using ADE179 on some addon airports in V5 can cause a problem i found the same in FlightBeam KDEN it caused default hangers to appear, also KPDX.
Un-installed V4.5 as i now use V5 but had to re-install 4.5 to get 176 working again it will not work without the sim installed you see the problem i cannot remove 4.5 as i may need to edit an airport, until addon developers move to V5 cads.
https://flic.kr/p/2jebMz2
Another example LSZH default hanger should not be there edit the cad with 176 and not 179 and this will not happen.
 
Last edited:
OK - I see what you are saying - my problem is in understanding why. You are saying that an addon compiled with the v4 compiler and loaded into v5 will exclude v5 stock elements. But if you recompile the addon using the v5 compiler and load it into v5 then v5 stock elements will show through.

v5 will compile the same flat airport as v4. Sloped features require a flag to be set. If there really is some problem with ADE 1.79 then I need to work out what it is since what you are finding is counter to my understanding of how things work. Please do two things for me. First send me a link to the thread in the FSDT forums so I can see it and second please zip up and email me a couple of these addon airport bgl files which you are seeing the problem with. I want to replicate your findings so that if there is some bug in the way ADE 1.79 works I can fix it. Email is jon AT scruffyduck DOT org

Thanks
 
My understanding from FSDT dev when the airports were updated to V5 they still use the V4 AFCAD file, i reported the problem to them that when they told me to use V4 ade and not the V5 ade.

V5 AFCAD`s

V5 AFCAD`s
www.fsdreamteam.com
Also V4 ADE 176 will not open a V5 CAD default file you will get "Failed to decompile" but will open all AFCAD files for payware addon airports from FSDT and FlightBeam.
 
Last edited:
For the avoidance of doubt there is a difference between the sim being used and the ADE version. ADE 1.79 will work fine with P3Dv4 and the v4 SDK. It will also work with the v5. So you do not need to go back to 1.76 in order to compile for v4. 1.76 does not support v5 so if you intend to do some work with v5 then you might find it more convenient to just have 1.79 installed. Of course 1.76 will not decompile a v5 bgl file since it knows nothing about the v5 code. ADE 1.79 will open v4 and v5 bgl files.

I think the sloped airport issue is a red herring since v5 compiles the same effective code for a flat airport as compiling with v4.

I am asking again for you to be kind enough to send me one or two of the AFCAD bgl files that give you the issue so that I can test it. In case you aren't aware, I am the developer of ADE and want to be sure that it is not contributing to the problems. This is important since I can see no reason for your issue based on how things work.

Thanks for your time
 
OK - I have checked this and can confirm that this is not related to P3D versions , SDK versions, Third party developers or ADE. First both files you sent me would not initially compile with any compiler due to errors which are not related to scenery objects or buildings. I am not sure how they came to be compiled in the first place. I corrected those errors so that I could compile both airports using ADE 1.79 set to P3D v5. In both cases the default scenery did not show through the airport behaving exactly the same way as the original bgl files and those files compiled with the P3D v4 SDK.

Each of the files you provided contain a large number of user placed exclusion rectangles covering the entire airport, and by chance all the v5 scenery. Neither contain any scenery objects or taxi signs so I assume those provided with the addon are in a separate file.

Those exclusion rectangles when compiled in any compiler and specifically P3D v4 and P3D v5 will exclude the v5 scenery and that is what I expected and saw.

The most likely explanation why you see them if you compile with ADE 1.79 rather than 1.76 is user settings being different in the different ADE versions. There is a setting in ADE which determines whether scenery objects (including exclusions) are compiled with the airport or in a separate bgl file with _OBJ as part of the name. The default setting can be found in Settings > Options > Project

1592831847844.png


If it is checked then the exclusion rectangles will be compiled to a separate bgl file. If it is not checked then the exclusion rectangles are in the main airport bgl files. That is how they are in the files you sent me.

I can see that if you do have this set for separate bgl files in ADE 1.79 but only copied or added the airport bgl file to P3D v5 then you will see the default scenery as you did. If ADE 1.76 had this option unchecked or you loaded the original file then you will not see default scenery when using that version of ADE.

I am sorry if this is a bit long winded but the bottom line is that it is perfectly fine to use ADE 1.79 and compile your changes for v5 with the v5 compiler provided you have the correct settings or make sure you copy both files into the P3D v5 installation

1592832144349.png


Of course there could be another explanation that some how in your modification work the exclusion rectangles were removed from the project and therefore did not get compiled at all. There could be other more arcane ways of achieving the results you saw but I would say they would be hard to achieve 'by accident'
 
You get the same with FlightBeam when edit the AFCAD file you only see the runways taxiways and parking no scenery in the addon AFCAD bgl, and the problem i see each developer has there own way of doing it, i posted a thread on LM forum they said to get on to you, changing the AFCAD BGL in V5 is the problem i think LM have taken one step back, i edit some of the default airports for my AI and some are usable example default KDTW in v4 ok in V5 shocking.
 
No changing the Bgl in v5 is not the problem. The problem is that LM changed the airports in v5 so they are no longer the same layout as in earlier versions Mostly adding and changing the buildings and taxi signs. The airport layouts are also modified so that they do not match what was in v4. Therefore a v4 airport imported into v5 generates a lot of problems. You are right that each developer is using different techniques on airports. There is no problem compiling a v4 project or bgl to v5 since the code is the same for flat airports.

There has been some work done on how to make the conversion. This is one way https://www.fsdeveloper.com/forum/t...lier-project-files-to-use-with-p3d-v5.447641/

You haven't mentioned yet whether you had ADE 1.79 set for separate bgl files but I guess you uninstalled it.

I am not sure what else I can say. Transfer of v4 and earlier to v5 is not an easy task and the reason is simply that LM have updated all the airports in v5. Many have a lot more detail and are better representations of the real thing. Hopefully third party devs will create updates to their work for v5 and save others from this hassle
 

Attachments

  • 1592837031319.png
    1592837031319.png
    126.5 KB · Views: 331
I have both v4 ADE 176 and v5 179, I had to reinstall V4.5 to use 176 which i upgraded to the pro version i notice that the V5 179 does not show this in the title bar.
 
Copy ProKey.dll and Infralution.Licensing.dll from the plugins folder in ADE 1.76 into the plugins folder in ADE 1.79
 
You must log in or register to reply here.
Back
Top