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

P3D v4 ADE 1.75 Beta -Support for P3D v4

Something is wrong.
I open CYOW_adep_ade.ad4 that I saved before , change nothing or add a vehicle, compile to addon scenery\scenery and the bgl compiler throws an error.
 
Perhaps you! might tell us what the error is?
 
Translated: "BGL Compiler does not work anymore".
Nothing else except whether I want to send info to Microsoft.

Other example:
Load stock airport EHHO.
I add a library object and try to compile.
This is what I get this time:

Compiler Errors Found. These were not identified by the Issue Manager. Please let us know
what the compiler error is so that we can improve the Issue Manager.

The compiler message is shown below

ScruffyDuck Scenery Design Engine Compiling
Using BglComp....


Parsing document: C:\MSFS\FS Design Tools\175_Beta\!AdeTempWorkOnly\EHHO_ADEP4_RS.xml

INTERNAL COMPILER ERROR: #C2033: XML Parse Error (line, column, error)

ERROR: 65, 34, The attribute 'transparent' on this element is not defined in the DTD/Schema.INTERNAL COMPILER ERROR: #C2952: Attribute 'transparent' is not allowed in element 'Runway'!
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Runway>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = Netherlands
ERROR: city = Hoogeveen
ERROR: name = Hoogeveen
ERROR: lat = 52.730833478272
ERROR: lon = 6.51611119508743
ERROR: alt = 12.192M
ERROR: magvar = 1
ERROR: trafficScalar = 0.7
ERROR: airportTestRadius = 5000.0M
ERROR: ident = EHHO
ERROR: >
ERROR: <Runway
ERROR: lat = 52.7307905629277
ERROR: lon = 6.51709243655205
ERROR: alt = 12.192M
ERROR: surface = GRASS
ERROR: transparent = FALSE
ERROR: heading = 94.0100021362305
ERROR: length = 1077.77M
ERROR: width = 29.87M
ERROR: number = 10
ERROR: designator = NONE
ERROR: patternAltitude = 213.36M
ERROR: primaryTakeoff = YES
ERROR: primaryLanding = YES
ERROR: primaryPattern = LEFT
ERROR: secondaryTakeoff = YES
ERROR: secondaryLanding = YES
ERROR: secondaryPattern = RIGHT
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2607: Compilation errors detected, compilation failed!


Parse complete!

I have changed nothing to the runway!
 
Hi Jon,
I think there is something wrong with the compiler.
I am using Flytampa Dubai Afcad scenery and wanted to update some parking spots.
Please keep in mind that I am using the available installer from Flytampa and migrated the scenery to P3D V4.
On its own it works fine.
However, when I just update parking spot F13 for example for Gate type small to heavy, recompile it and use the parking spot in P3D V4, my GSX throws me an error that this parking spot is isolated. Is this supposed to be happening like this ?
Please let me know if I am missing a step.

Here are some additional config settings done in ADE:
Scenery cfg: C:\ProgramData\Lockheed Martin\Prepar3D v4
FS Main folder: X:\Program Files\Lockheed Martin\Prepar3D v4\ (This is correct)
SDK
bglcomp: C:\Program Files\Lockheed Martin\Prepar3D v4 SDK 4.0.23.21468\World\Scenery\
Ship2Vec: C:\Program Files\Lockheed Martin\Prepar3D v4 SDK 4.0.23.21468\World\Terrain\
Thank you
 
Andrew said:
Would save us tons of work if ADE could punch holes. This problem is not with P3D4 only. It was the same with P3D3.
Click to expand...

Indeed, I like to keep my projects in one project file (ADE at its best).

@Jon: Would it be possible to add this feature to ADE?
 
What happens if you adjust the position of the smaller poly? Do you expect the hole to move?
 
Using the 32bit Sbuilder recommended for Win10, I make a hole. Thereafter I can move the hole around and resize it. When happy with location and size, I then have to draw the LC I want, with borders a little bigger than the hole. Pure magic, tested this at ELLX.
 
It's really simple.

First I draw the Airfield1 texture. On top of that one, I draw an area I want to be cement. Then right click it and select "Make hole". That way I can make several holes. And move them around until happy. Then fill them with the landclass I want.

So the answer is - first draw the big grass area, then punch in the holes.
 
Last edited:
Hello.

First of all, I would like to thank you for the tireless efforts to keep the Airport Design Editor up-to-date. The tool is very useful when creating sceneries. Many Thanks!

Now I had downloaded the latest beta (1.75.6366.19886) and at the first start ADE tells me that I should register my copy, see picture:

ade_175_beta_p3dv4_license.jpg


What exactly do I have to do here? I do not have a registry key, but would like to continue to use ADE as a free version, as before ADE 170.
 
Sorry - the problem is that we shipped the ProKey with the beta. You don't need it - just go to the Plugins folder inside the main ADE folder and delete the file called prokey.dll. Make sure you delete just that file and not one of the others.
 
Hello I have the same error as posted below earlier.

I have tested GSX with a fresh install and works fine, then when I modify and comp the file GSX tells me the parking spot is 'too isolated'- from the GSX forums it says its a scenery fault. I have tried a couple of times. I am running the latest version into P3D V4.

Any ideas?

Kind regards

H


Hi Jon,
I think there is something wrong with the compiler.
I am using Flytampa Dubai Afcad scenery and wanted to update some parking spots.
Please keep in mind that I am using the available installer from Flytampa and migrated the scenery to P3D V4.
On its own it works fine.
However, when I just update parking spot F13 for example for Gate type small to heavy, recompile it and use the parking spot in P3D V4, my GSX throws me an error that this parking spot is isolated. Is this supposed to be happening like this ?
Please let me know if I am missing a step.

Here are some additional config settings done in ADE:
Scenery cfg: C:\ProgramData\Lockheed Martin\Prepar3D v4
FS Main folder: X:\Program Files\Lockheed Martin\Prepar3D v4\ (This is correct)
SDK
bglcomp: C:\Program Files\Lockheed Martin\Prepar3D v4 SDK 4.0.23.21468\World\Scenery\
Ship2Vec: C:\Program Files\Lockheed Martin\Prepar3D v4 SDK 4.0.23.21468\World\Terrain\
Thank you
 
Hello All -- just reporting a basic problem that seems to be related to some of the previous reports regarding layers/polys. I am running 01.75.6372 under Win10 with various ORBX addons including FTX Global Base Pack.
I am experimenting with a basic airport configuration on a remote island, by laying down a poly of Flatten Mask Class Map Exclude AutoGen then applying a runway in the poly.
Compile, then save. Upon running P3D, the flatten/exclude poly does NOT appear but the runway does appear. No errors are indicated.

Also, the latest SAS does not run for me and indicates it cannot find any version of FS. Registry entries all seem OK. Any clues/hints/comments please!!! I know much is still being figured out with P3Dv4.

Thanks ---- Bob :);)
 
Guys - GSX isn't my product and I think it better addressed on their support forum. There is another thread here on the same subject and Umberto from FS Dream Team, the developers, has posted that they have a fix for this issue. There is also a separate thread for SAS for P3D v4. If you have ADE 1.75 working but SAS isn't then, since they basically use the same code to find FS versions, I have probably messed up the code in SAS. However I do not get the problem reported here.
 
You must log in or register to reply here.
Back
Top