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

Compile Error #2

TFE123

TFE123

Messages
48
Country
australia
Hey Every one thank for being patient when im asking all my questions, I made an airport but it wont compile for some reason its saying somethings are incorrect does anyone want to try compiling it for me and tell me what was wrong?
View attachment 2549

If you have fixed every thing up or you managed to compile it could you please let me know and attach the BGL

Thanks,
 
Last edited:
You have at least two boundary fences that have only one vertex line 547 and 553 of the xml or thereabouts

Have you run the error checkers in FSXP There may be one to handle orphan boundary fences


You also have a problem with at least one of your parking spots. you need to check out the rules for naming airline codes. you have airlineCodes = The Fling Eagles for taxi parking 11, 16 and a bunch of others. Codes can oly have a maximum of four letters and there are standards set for these.

There is also at least one problem with a taxi sign label that has an invalid character in it

I stopped looking at that point
 
Last edited:
Oh thank you soooo much man thats EXACTLEY what i needed to know, So far i've cleand up those boundry Fences ill check every thing B4 i mention a compile error next time, Now the Preperation settings what do i tick???
 
Last edited:
Well I do not use FSX Planner so I can't answer that question. However I would recommend that when you get compiler errors (from BglComp) to take a careful look at what it says. It may look like a lot of gibberish but it generally tells you exactly what is wrong.
 
I just took a look i fixed some of the bugs like the airline codes and the boundry fences but theres "errors" with the start locations and the COM frequencies attached below is the list of bugs that i need to fix if u can solve any of them i'll b over the moon, thanks for your pacience and does that bgl2xml_gui convert xml's to bgl's or just bgl's to xmls?


View attachment 2551
 
Last edited:
Well as I said you need to look at what it is telling you. If you look at the START errors it is tellings you that you need to define a DESIGNATOR attributes and that is not there. If there is no designator (LEFT, RIGHT etc) then it should be none

As far as all the taxipath errors are concerned check the message and it is telling you that you have missing or incorrect parking spot and taxi point numbers. Each path has to have a start and end. Those are defined in the xml for the path. If the compiler cannot find the relevant parking spot or taxi point then it will throw the errors you are seeing.
 
TFE123 said:
I just took a look i fixed some of the bugs like the airline codes and the boundry fences but theres "errors" with the start locations and the COM frequencies attached below is the list of bugs that i need to fix if u can solve any of them i'll b over the moon, thanks for your pacience and does that bgl2xml_gui convert xml's to bgl's or just bgl's to xmls?
Click to expand...


Bgl2Xml GUI will take a bgl file and convert it to XML. To convert the XML back to a Bgl file is what FSX Planner is doing.
 
Ok, well as of the start points im just going to delete the helipads because i've already done the designators such as 1,2,3 and 4. but do you know how i fix the Frequencies?
 
Last edited:
TFE123 said:
Oh thank you soooo much man thats EXACTLEY what i needed to know, So far i've cleand up those boundry Fences ill check every thing B4 i mention a compile error next time, Now the Preperation settings what do i tick???
Click to expand...

This depends on what you are changing in the airport. The simplest thing to do it leave them all checked. However, you will need to create an exclusion rectangle over the entire airport to exclude taxiway signs, as they are not deleted unsing the Delete tag.

If you want to get more specific, you can just check off the items that are relevant to what you are changing. This lets you have more control over what is written into the bgl file, but takes a bit more knowledge of how items interact.

-Russell
 
ok i kinda understand most of that what if i created a NEW airport do i untick every thing? and how do i solve the problems with the Frequencies
 
Last edited:
I checked Everything yet theres still errors with the taxiways and the start location on runway 36R my airport is attached below if some one cood fix the last few errors tell me what you did i would be over the moon



View attachment 2554
 
Last edited:
There are seven start locations. It should be only six.

Code: 
		<Start
			type="RUNWAY"
			lat="-27.77874366142903"
			lon="161.88136312095673"
			alt="6.705M"
			heading="0.0"
			number="36"
			designator="R"/>
		<Start
			type="RUNWAY"
			lat="-27.76651337949959"
			lon="161.88136751040912"
			alt="6.705M"
			heading="180.0"
			number="18"
			designator="L"/>
		<Start
			type="RUNWAY"
			lat="-27.76650450746908"
			lon="161.87808320146638"
			alt="6.705M"
			heading="180.0"
			number="18"
			designator="C"/>
		<Start
			type="RUNWAY"
			lat="-27.76661859408972"
			lon="161.8746791810722"
			alt="6.705M"
			heading="180.0"
			number="18"
			designator="R"/>
		<Start
			type="RUNWAY"
			lat="-27.77891423857227"
			lon="161.8747055347656"
			alt="6.705M"
			heading="0.0"
			number="36"
			designator="L"/>
		<Start
			type="RUNWAY"
			lat="-27.78154375755895"
			lon="161.87626117771865"
			alt="6.705M"
			heading="0.0"
			number="36"
			designator="R"/>
		<Start
			type="RUNWAY"
			lat="-27.7788496130711"
			lon="161.87805632532496"
			alt="6.705M"
			heading="0.0"
			number="36"
			designator="C"/>

There are others errors, but I coult not find (yet).

Regards,

José
 
Hi,

I deleted the repeated start location and edit the taxiway path from (0) to (36).

<Start
type="RUNWAY"
lat="-27.76661859408972"
lon="161.8746791810722"
alt="6.705M"
heading="180.0"
number="18"
designator="R"/>

It compiled ok.

The XML code and the BGL are attached.

Regards,

José
 

Attachments

Ty Sooo much man and thanks for sacing the XML aswel so i can see where i went wrong and correct it in future airports
 
Hi, Jon and Russell

There was some difficulties to find the above errors, since:

1. FSX Planner did not identify the errors (the tool find everything is ok);

2. FSXP (supposedly) attribute number 0 (zero) to references to runway 36;

3. SDE do not read the XML file because there were library objects coded;

4. ADE do not read XML, but bgl.

I had to edit and compile in DOS CMD, to catch the errors messages.

I think in near future those issues will be correctly addressed.

Regards,

José
 
José said:
There are seven start locations. It should be only six.

Code: 
		<Start
			type="RUNWAY"
			lat="-27.77874366142903"
			lon="161.88136312095673"
			alt="6.705M"
			heading="0.0"
			number="36"
			designator="R"/>
		<Start
			type="RUNWAY"
			lat="-27.76651337949959"
			lon="161.88136751040912"
			alt="6.705M"
			heading="180.0"
			number="18"
			designator="L"/>
		<Start
			type="RUNWAY"
			lat="-27.76650450746908"
			lon="161.87808320146638"
			alt="6.705M"
			heading="180.0"
			number="18"
			designator="C"/>
		<Start
			type="RUNWAY"
			lat="-27.76661859408972"
			lon="161.8746791810722"
			alt="6.705M"
			heading="180.0"
			number="18"
			designator="R"/>
		<Start
			type="RUNWAY"
			lat="-27.77891423857227"
			lon="161.8747055347656"
			alt="6.705M"
			heading="0.0"
			number="36"
			designator="L"/>
		<Start
			type="RUNWAY"
			lat="-27.78154375755895"
			lon="161.87626117771865"
			alt="6.705M"
			heading="0.0"
			number="36"
			designator="R"/>
		<Start
			type="RUNWAY"
			lat="-27.7788496130711"
			lon="161.87805632532496"
			alt="6.705M"
			heading="0.0"
			number="36"
			designator="C"/>

There are others errors, but I coult not find (yet).

Regards,

José
Click to expand...

Hey José,
Just outta curiosity why can i only make 6 Start points?
 
Sam;

Starting points are for runways and helo pads.

Hence if you have 3 rwy's (in this case R/C/L), 6 starting points.

Everything else would be started at Parking/Gate spots.

I guess and this is just a guess, but if you wanted to create a mid-field point on, say on a rather lengthy rwy, you probably could. But the FAA kind of frowns those.

Dave
 
You must log in or register to reply here.
Back
Top