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

Loadsa Parse Errors

R

rondon9897

Messages
16
Country
unitedkingdom
If someone could look at the attached .txt and see what's cracking off - there's so much wrong I don't know what's happening.

I'm trying to add T5 spaces to EGLL and several other little ditties at Heathrow, and somehow I've cocked it up good.
Any help HUGELY appreciated (particularly as I'm with BA Virtual now, I need EGLL!!)

Thanks again,

CJ (using new ADE 1.35)

:cool:
 

Attachments

Do you have FSX SDK SP2?

This is the fourth post in the thread "Sticky: Airport Design Editor FAQ"

Regards

Horst
 
Last edited:
I wish I had a £,$(fill in your favorite currency here) for each time this has been asked ;)
 
Ahh, ok. My BGL .XSD file is 29 August exactly, which could well be the problem. Could you give me a link to a newer one?
 
Last edited:
For ADE you must have FSX SDK SP1A or SP2. They are Service Packs for the SDK, not for FSX!

Regards

Horst
 
rondon9897 said:
Ahh, ok. My BGL .XSD file is 29 August exactly, which could well be the problem. Could you give me a link to a newer one?
Click to expand...

Nope - that IS the problem :D

As Horst says you need to download (www.fsinsider.com) SP1a for the SDK if you are running the RTM version of FSX, SP2 if you have FSX SP2 or if you have the Acceleration pack then the updated SDK is on the DVD.
 
Jon

Have updated SP2 SDK - and compile still doesn't work (.txt above still applies when I click compile).


Any suggestions?

CJ:cool:
 
I assume you mean that you are still getting the boundary fence error? In that case it would seem that ADE is still pointing at the old BglComp.

Please update the folders in ADE. Settings > Options > Folders and click the Find button. To be sure then shut ADE Down and re-start it.

If you still have the problem the attach the file ade_200807.log. It is in the ADE application folder.
 
This is not a compiler error but warnings that you have some objects at a great distance from the airport. You are using the correct compiler now. I would suggest that you restart with the stock EGLL.
 
NO NO NO NO! I can't start again!!! It took me HOURS!!!!


It is definitely a compiler error - the runways are NOT 400km away. Something is wrong with the software - I'm not a lunatic.

Believe it or not.

Is there no way around it Jon?

CJ:cool:
 
rondon9897 said:
NO NO NO NO! I can't start again!!! It took me HOURS!!!!


It is definitely a compiler error - the runways are NOT 400km away. Something is wrong with the software - I'm not a lunatic.

Believe it or not.

Is there no way around it Jon?

CJ:cool:
Click to expand...

Let's get a couple of things clear. This is not a compiler error - they are compiler warnings; and ADE does not put things 400km away from the ARP on its own. The warnings:

WARNING: #C1102 EGLL 433367 RUNWAY 5000 Airport (EGLL) has object (RUNWAY) that is 433367 meters from the ARP with a test threshold of 5000 meters! XML line: 869.
WARNING: #C1102 EGLL 433367 RUNWAY 5000 Airport (EGLL) has object (RUNWAY) that is 433367 meters from the ARP with a test threshold of 5000 meters! XML line: 911.
WARNING: #C1102 EGLL 433368 RUNWAY 5000 Airport (EGLL) has object (RUNWAY) that is 433368 meters from the ARP with a test threshold of 5000 meters! XML line: 953.
WARNING: #C1102 EGLL 433367 RUNWAY 5000 Airport (EGLL) has object (RUNWAY) that is 433367 meters from the ARP with a test threshold of 5000 meters! XML line: 995.
WARNING: #C1102 EGLL 433367 RUNWAY 5000 Airport (EGLL) has object (RUNWAY) that is 433367 meters from the ARP with a test threshold of 5000 meters! XML line: 1037.
WARNING: #C1102 EGLL 433367 RUNWAY 5000 Airport (EGLL) has object (RUNWAY) that is 433367 meters from the ARP with a test threshold of 5000 meters! XML line: 1079.
Click to expand...

indicate that you have six runways that are at a great distance from the airport. Have you implemented cross wind runways? This is the usual reason for runway warnings of this type. If not then I would recommend that you List > Runways and see which are not in the stock airport. If you did not intend to add extra runways then you can delete the ones that should not be there.
 
You must log in or register to reply here.
Back
Top