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

Adding objects to default airport

Messages
5
Country
scotland
Hi one and all ...

new to FSXplanner!

just setup R23 on my machine and tried to add missing vasi lighting to the secondary end of R4L at PHNL. The addition shows up fine on the FSXplanner page then i ask the program to compile using 'write runways' and get a message saying the parse is complete (no errors). On starting up FSX i get the new scenery being created message but on checking the airport the lights aren't there, nor when i go back to open up FSXplanner and pull up the airport are they there either ... appreciate any help ...

Alan
 
Hi one and all ...

new to FSXplanner!

just setup R23 on my machine and tried to add missing vasi lighting to the secondary end of R4L at PHNL. The addition shows up fine on the FSXplanner page then i ask the program to compile using 'write runways' and get a message saying the parse is complete (no errors). On starting up FSX i get the new scenery being created message but on checking the airport the lights aren't there, nor when i go back to open up FSXplanner and pull up the airport are they there either ... appreciate any help ...

Alan

OK - I'll split this into sections:
1) After you added the vasi to the runway, did you save the airport as an xml file? If not you should do that and then when working on the airport in the future you should open the xml file and not the bgl file. The bgl file should only be opened once. After that you should save the airport as an xml and use that for all your changes. FSX Planner does not make any changes to the default bgl files. So if you make changes and then just re-decompile the bgl file again you won't see your changes.

Basically the procedure to modify a default airport is:
a) decompile the airport from the default bgl file
b) make your changes
c) save the airport as an xml file
d) compile the airport to a bgl file
e) if more changes are needed in the future re-open the saved xml file from step c

2) To see the airport in FSX you need to make sure the new bgl file is placed in the appropriate scenery folder. By default this is the addon scenery folder, but you may place it in a different subfolder if you prefer. Then you also need to make sure it is selected in the FSX scenery options and that it is at the top of the list. If it isn't then you won't see any of your changes.

-Russell
 
Hi Russell ... appreciate your prompt reply to my message. I was missing out the 'convert to xml' step. Now that i've followed your instructions and bumped my Addon Scenery folder to priority 1 my changes show up, but i have to report an overhead! ... at phnl i'm only being given the active runway and an assortment of parking slots as starting location ... prior to the change i could select any runway for takeoff ... and as for phjr a few miles west wowee ... the airport has been re-organised just a tad ... one of the westbound runways now ends out in the ocean and has a building sitting about halfway down its length. The north/south runway also now juts out into the water ... that this should happen on the back of a simple attempt to add approach lighting has me baffled ... perhaps you can cast some light (no pun intended of course!) ...

Alan
 
That's very strange that a different airport would be affected. I'm not sure what changes you made, so it's a bit difficult to determine why this would happen. There are a lot of people here who know all the little details of airport design and how they can affect other airports, so perhaps they might be able to help with this?

-Russell
 
if i gave the impression that the changes at phjr were in some way related to changes i made at phnl it was unintentional ... i added approach lighting at phjr as a separate exercise ...

alan
 
I don't have Ultimate Terrain installed but my Oahu scenery is photorealistic from the Megascenery stable. I'd stress there is no problem with my PHJR scenery pre the fsxplanner modification as if i remove the newly created bgl from my Addon Scenery folder the airport returns to being exclusively on dry land with no buildings on the runways ...

Alan
 
I keep forgetting about Mega:X O'ahu.

Make sure you're editing the proper file; PHJR-BarbersPointNAS.BGL located in the Mega folders and not the default file.
 
That's it! After converting the bgl from the Mega ...X folder to XML using bglxml as fsxplanner wouldn't open it direct ( got message saying 'there are no airports in this XML file' which strikes me as not terribly logical given i'm trying to open a bgl file ... still, got there in the end ... that's the important thing) ... my thanks for your help in this ...

Alan
 
That's it! After converting the bgl from the Mega ...X folder to XML using bglxml as fsxplanner wouldn't open it direct ( got message saying 'there are no airports in this XML file' which strikes me as not terribly logical given i'm trying to open a bgl file ... still, got there in the end ... that's the important thing) ... my thanks for your help in this ...

Alan

FSX Planner decompiles a bgl to xml in memory and then parses that xml. So it's possible that the decompiling process didn't find any airports and therefore created an empty xml file, which would show the above error message.

However, it means that there is a problem that the Mega X bgl file is causing in the decompiling process. But as I don't have that bgl file I can't test it. :(

-Russell
 
Back
Top