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

Something to worry about?

G

garfield_x

Messages
72
Country
netherlands
Today i tried to do make soem changes to EHAM (Schiphol)

After saving the changes i got the compile screen with the following warnings.
Is that something to worry about?

Peter

Code: 
ScruffyDuck Scenery Design Engine Compiling
Using FSX BglComp....


Parsing document: D:\Temp\ade_040_2723\work\EHAM_AFX_ ADE.xml

WARNING: #C1102 	EHAM	5546	RUNWAY	5000	Airport (EHAM) has object (RUNWAY) that is 5546 meters from the ARP with a test threshold of 5000 meters!  XML line: 300.
WARNING: #C1102 	EHAM	6975	START	5000	Airport (EHAM) has object (START) that is 6975 meters from the ARP with a test threshold of 5000 meters!  XML line: 696.
WARNING: #C1102 	EHAM	5091	TAXI_POINT	5000	Airport (EHAM) has object (TAXI_POINT) that is 5091 meters from the ARP with a test threshold of 5000 meters!  XML line: 965.
WARNING: #C1102 	EHAM	5472	TAXI_POINT	5000	Airport (EHAM) has object (TAXI_POINT) that is 5472 meters from the ARP with a test threshold of 5000 meters!  XML line: 971.
WARNING: #C1102 	EHAM	7026	TAXI_POINT	5000	Airport (EHAM) has object (TAXI_POINT) that is 7026 meters from the ARP with a test threshold of 5000 meters!  XML line: 977.
WARNING: #C1102 	EHAM	5348	TAXI_POINT	5000	Airport (EHAM) has object (TAXI_POINT) that is 5348 meters from the ARP with a test threshold of 5000 meters!  XML line: 5063.
WARNING: #C1102 	EHAM	5071	TAXI_POINT	5000	Airport (EHAM) has object (TAXI_POINT) that is 5071 meters from the ARP with a test threshold of 5000 meters!  XML line: 5267.
WARNING: #C1102 	EHAM	5341	TAXI_POINT	5000	Airport (EHAM) has object (TAXI_POINT) that is 5341 meters from the ARP with a test threshold of 5000 meters!  XML line: 5819.
WARNING: #C1102 	EHAM	5357	TAXIWAY_SIGN	5000	Airport (EHAM) has object (TAXIWAY_SIGN) that is 5357 meters from the ARP with a test threshold of 5000 meters!  XML line: 32505.
WARNING: #C1102 	EHAM	5082	TAXIWAY_SIGN	5000	Airport (EHAM) has object (TAXIWAY_SIGN) that is 5082 meters from the ARP with a test threshold of 5000 meters!  XML line: 32512.
WARNING: #C1102 	EHAM	5080	TAXIWAY_SIGN	5000	Airport (EHAM) has object (TAXIWAY_SIGN) that is 5080 meters from the ARP with a test threshold of 5000 meters!  XML line: 32645.
WARNING: #C1102 	EHAM	5069	TAXIWAY_SIGN	5000	Airport (EHAM) has object (TAXIWAY_SIGN) that is 5069 meters from the ARP with a test threshold of 5000 meters!  XML line: 34675.
WARNING: #C1102 	EHAM	5353	TAXIWAY_SIGN	5000	Airport (EHAM) has object (TAXIWAY_SIGN) that is 5353 meters from the ARP with a test threshold of 5000 meters!  XML line: 34682.
WARNING: #C1102 	EHAM	5453	TAXIWAY_SIGN	5000	Airport (EHAM) has object (TAXIWAY_SIGN) that is 5453 meters from the ARP with a test threshold of 5000 meters!  XML line: 34689.
WARNING: #C1102 	EHAM	6720	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 6720 meters from the ARP with a test threshold of 5000 meters!  XML line: 34864.
WARNING: #C1102 	EHAM	6769	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 6769 meters from the ARP with a test threshold of 5000 meters!  XML line: 34867.
WARNING: #C1102 	EHAM	6825	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 6825 meters from the ARP with a test threshold of 5000 meters!  XML line: 34870.
WARNING: #C1102 	EHAM	6920	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 6920 meters from the ARP with a test threshold of 5000 meters!  XML line: 34873.
WARNING: #C1102 	EHAM	7319	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 7319 meters from the ARP with a test threshold of 5000 meters!  XML line: 34876.
WARNING: #C1102 	EHAM	7509	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 7509 meters from the ARP with a test threshold of 5000 meters!  XML line: 34879.
WARNING: #C1102 	EHAM	7710	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 7710 meters from the ARP with a test threshold of 5000 meters!  XML line: 34882.
WARNING: #C1102 	EHAM	7706	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 7706 meters from the ARP with a test threshold of 5000 meters!  XML line: 34885.
WARNING: #C1102 	EHAM	7675	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 7675 meters from the ARP with a test threshold of 5000 meters!  XML line: 34888.
WARNING: #C1102 	EHAM	7587	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 7587 meters from the ARP with a test threshold of 5000 meters!  XML line: 34891.
WARNING: #C1102 	EHAM	7112	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 7112 meters from the ARP with a test threshold of 5000 meters!  XML line: 34894.
WARNING: #C1102 	EHAM	7112	BOUNDARY_FENCE_VERTEX	5000	Airport (EHAM) has object (BOUNDARY_FENCE_VERTEX) that is 7112 meters from the ARP with a test threshold of 5000 meters!  XML line: 35155.


Parse complete!
 
Peter

An FSX airport has a Warning Limit Circle around it set usually at 5000m by SDE/ADE. If you have placed things further away from the Airport Reference Point than that then BglComp warns you. It maybe that you intended them that far out in which case all is well. If youare using ADE then zoom out and you will see a red circle around the airport, This is the Airport Test Radius. If it is not visible then right click on the ARP and make sure that ShowTestRadius is true.

If the object concerned are in the right place but outside the test radius then all is ok, On the other hand they may be in the wrong place and you need then to move them.
 
Looks like the test-radius is too small.

Btw. I have noticed that a change in the testradius doesn't get saved, at least not in version 0.42.... so you have to set it each time you compile your airport..

Ups... beaten by The man himself ... ;-)
 
Last edited:
DanKH said:
Btw. I have noticed that a change in the testradius doesn't get saved, at least nit in version 0.42.... so you have to set et each time you compile your airport..
Click to expand...

Correct - in this situation where we are not saving to XML at the moment then the test radius is not saved as it is not taken into the Bgl file.

I am working on an extension to the way ADE handles data that will allow this kind of thing (and other stuff besides) to be saved
 
A i see. :)

Its warning about the 'polderbaan' (RW36L) on EHAM which is far from the airport. So i need to adjust the test radius before saving it.

thx!
 
No you can ignore it if you know that your elements are in the correct place. It will not stop the compile. Extending the test radius will just stop the warnings that some people find disturbing or annoying - it will not stop the objects being compiled or appearing in FSX
 
Thx Jon

So nothing to worry about then :)

It will be a great program when it will be finished :) Altohough its already very workable.
 
You must log in or register to reply here.
Back
Top