P3D v4 ADE 1.75 Beta v4 Compile Error

[PaulH2]

This is only happening with one airport? It is only happening for one person (so far) Let me see the log please: https://scruffyduck.screenstepslive...8/l/199769-how-do-i-send-you-the-ade-log-file

Jon,

The log file is attached, as requested.

Paul

 

[PaulH2]

Nothing obvious from the log Jon?

I really don't understand why I can compile other projects (including the default PHNL) but not this file, why it will compile with the v3 SDK, and why on two different machines (must be something in common, but I have no idea what).

Looks like I'm stuffed...

 

[scruffyduck]

Sorry - no. I really have no idea since we can't replicate it

 

[PaulH2]

Sorry - no. I really have no idea since we can't replicate it

OK, thanks for trying Jon, and everyone else who tried.

 

[GavNormandale]

Could you try making a back up then deleting a few objects at a time then compile, if you find a point when it works you could go back to your back up file and delete the things that got it working and try to narrow it down, in case there is a piece of faulty content on your machine but not on ours?

Gav

 

[PaulH2]

Could you try making a back up then deleting a few objects at a time then compile, if you find a point when it works you could go back to your back up file and delete the things that got it working and try to narrow it down, in case there is a piece of faulty content on your machine but not on ours?

Gav

Hi Gav,

I think the issue lies with something outside the project itself. I can compile it on my home theater PC. It's not exactly an elegant solution, but I installed the SDK on there and manually compiled the .xml output from ADE and it compiles on the machine perfectly). The only catch is that I don't get the CVX of GP files compiled (I assume these are separate xml files that ADE isn't outputting because the main xml fails to compile).

The main difference between my HTPC and the other two is that they are both running Visual Studio (2015 on one, 2017 on the other) and both are running Windows 10 Insider Preview, so I'm guessing something has been changed in msxml on those machines that has (partially) broken bglcomp.

So I guess my next step is to either do a full ADE install (and therefore have to install P3D v4 itself, which I don't really want to do) on the HTPC, or figure out if there is a way to just have ADE output the XML files so I can compile them all manually on the other machine.

Paul

 

[zzip]

Hi all,
I am busy converting an FSX airport to P3Dv4.
When I want to compile, I get an error.
See .txt file.

Grtz
Peter

 

[scruffyduck]

Are you using the P3D v4 compiler?

 

[zzip]

Yes, Jon,
This airport is made in FSX with ADE 1.65.
I have used the AD4 file to open it in ADE 1.75.
Open, save airport is no problem .

Grtz
peter

 

[zzip]

I receive a new CVX file, but no BGL ADEP BGL file .

Grtz
Peter

 

[tgibson]

Sounds to me like ADE might not be pointing to your P3Dv4 BGLComp compiler properly. Check your paths.

 

[zzip]

Thanks Tom

I will check this once.
I have compiled another airport,
And I get the same result.
The error must therefore lie with me.

Grtz
Peter

 

[zzip]

Tom,
I have installed the SDK for Prepar3Dv4 (I used the SDK of FSX).
All settings are correct now.
I also modified my project path, which was linked to my external disk (G) .

But I still get a notification in Dutch.
I translate :
Can not find part of path ... ADE 1.75_Beta \ P34 \ Xml \ EBBL_ADEP4_ZZIP.xml.

This message still refers to my external drive (G) .
I gonna uninstall ADE 1.75 now and install it again .
I hope it works .

Grtz
Peter

 

[zzip]

===PROBLEM SOLVED===

After I've installed ADE 1.75 RC1 again, I've entered all settings correctly .
Everything works perfectly.
No more error messages.

Thanks all !
Peter

 

[PaulH2]

Just an update on my original problem. I bit the bullet and did a fresh Windows install to see if that helped. This is a completely clean installation, only Windows, P3D v4, P3D v4 SDK and ADE are installed. I get the exact same parse error on the PHNL project, other airports compile fine. At this stage, the only thing I can think of different with my HTPC is that my desktop is running Windows 10 Insider preview, so I have to conclude that this issue is due to something that has changed (presumably within MSXML) in the Fall Creator's Update.

I'll keep trying, but I don't know what to try next.

 

[zzip]

I do not know, but just a try, do you have the SDK for P3Dv4?
Do you have ADE 1.75 RC1 installed ?
I uninstall my ADE and install ADE 1.75 again .

BGLComp Folder in :
C:\Program Files\Lockheed Martin\Prepar3D v4 SDK 4.0.28.21686\World\Scenery

Shp2Vec Folder in :
C:\Program Files\Lockheed Martin\Prepar3D v4 SDK 4.0.28.21686\World\Terrain

I do not know anymore either Paul .

Succes
Peter

 

[PaulH2]

I do not know, but just a try, do you have the SDK for P3Dv4?
Do you have ADE 1.75 RC1 installed ?
I uninstall my ADE and install ADE 1.75 again .

BGLComp Folder in :
C:\Program Files\Lockheed Martin\Prepar3D v4 SDK 4.0.28.21686\World\Scenery

Shp2Vec Folder in :
C:\Program Files\Lockheed Martin\Prepar3D v4 SDK 4.0.28.21686\World\Terrain

I do not know anymore either Paul .

Succes
Peter

Yes, ADE 1.75 RC 1, latest Prepar3D v4, only the v4 SDK. In my case, the folder paths are the same, but on D: drive (as is ADE).

Paul

 

[zzip]

Sorry Paul, I do not know anymore .


But i have another question .
I have an FSX airport .
I will open it in ADEP4 .
When I compile the airport now, is it a real P3Dv4 airport from then on?

Grtz
Peter

 

[scruffyduck]

The bgl will be based on the compiler you use. If you compile using the P3D v4 compiler then it will have formats not understood by earlier versions of FS and P3D.

The ADE project file may also be slightly different and you could get errors compiling with an earlier compiler.

 

[zzip]

Thanks Jon, that is clear.

How you did that, I do not know, but every day it's a pleasure again
to work with such a nice program.
From me this program gets a big 10!

Thanks again, Jon