-
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.
FS2004 Remove Stock Airport from bgl
- Thread starter beroun
- Start date
Much as @hgschnell has written.
Generate a new version of 1S0 containing no features at all, but ensuring that all the previous features, runways, taxiways, aprons etc. are disabled.
This will ensure that the original scenery isn't visible in the simulator ... unfortunately the airfield will still exist on the menus and maps/GPS etc.
Editing the the default AP915150 may or may not work completely satisfactorily.
In my experience, BGL2XML can have difficulty dealing with some navigation features, which will cause recompilation errors.
These errors may well be related to other airfields in the file and can require quite extensive "digging and poking" and reference to the SDK documentation, either to rectify the situation or to remove the failing feature, which can be related to VORs, ILS, and some other stuff.
In this instance, AP915150 appears to decompile and recompile, with 1S0 completely removed, with no errors
For personal use, this would be my choice, but for re-distribution purposes, I always have reservations about this approach as it may cause issues for end users further down the line.
When making modifications like this to default files I ALWAYS keep an adjacent backup, with an adjusted suffix, eg. AP915150.bgx, AND an adjacent text file, eg. AP915150.txt, containing notes of what changes have been made.
I seem to remember that some third-party software will recognise that a default file has been changed, and ignore it or refuse to load it.
This may cause other problems if wanting to make other edits in the immediate vicinity.
Good luck
Generate a new version of 1S0 containing no features at all, but ensuring that all the previous features, runways, taxiways, aprons etc. are disabled.
This will ensure that the original scenery isn't visible in the simulator ... unfortunately the airfield will still exist on the menus and maps/GPS etc.
Editing the the default AP915150 may or may not work completely satisfactorily.
In my experience, BGL2XML can have difficulty dealing with some navigation features, which will cause recompilation errors.
These errors may well be related to other airfields in the file and can require quite extensive "digging and poking" and reference to the SDK documentation, either to rectify the situation or to remove the failing feature, which can be related to VORs, ILS, and some other stuff.
In this instance, AP915150 appears to decompile and recompile, with 1S0 completely removed, with no errors
For personal use, this would be my choice, but for re-distribution purposes, I always have reservations about this approach as it may cause issues for end users further down the line.
When making modifications like this to default files I ALWAYS keep an adjacent backup, with an adjusted suffix, eg. AP915150.bgx, AND an adjacent text file, eg. AP915150.txt, containing notes of what changes have been made.
I seem to remember that some third-party software will recognise that a default file has been changed, and ignore it or refuse to load it.
This may cause other problems if wanting to make other edits in the immediate vicinity.
Good luck
Last edited:
Have a look:
FS2004 - ATC to call ADE modified airport by its Name
HI, Have just modified the default 1S0 Pierce airport in Washington State by ADE. Have changed the name to correct KPLU (current new airport designation) using ADE ProKey Plugin, also added some scenery and traffic..... the usual stuff. Airport looks great! BUT. The ATC now calls airports...
www.fsdeveloper.com
- Messages
- 553
- Country
Beroun,
Instructions for Modifying Airport Files (KPLU and 1S0)
Instructions for Modifying Airport Files (KPLU and 1S0)
- Fixing KPLU and 1S0:
- I will update both KPLU and 1S0 ADE files for you. Note that 1S0 cannot have its stock airport removed. All stock airports in Flight Simulator cannot be deleted.
- Process for Editing the Stock Airport:
- Open the stock airport (1S0) in ADE first.
- Then, edit everything you want to keep—objects, runways, taxiways, etc.
- Next, pull down the Raw Data menu.
- Change the airport code from 1S0 to KPLU. Make sure that all airport codes are changed to KPLU.
- Once you’ve made the changes, close the Raw Data window.
- Saving the File:
- Go to File > Save As.
- In the save dialog box, make sure the filename reads KPLU_[Your Name].bgl (you can add your name or any identifier).
- Save the file and compile it.
- This completes the first part of the process for KPLU.
- Reopening ADE for Further Edits:
- After saving the first KPLU file, reopen ADE and load the stock airport 1S0 again.
- Now you can remove taxiways, lights, buildings, and any other objects.
- Important:Do not remove the runway, but you must modify it:
- Reduce the runway length from 4,000 ft to 40 ft.
- Reduce the runway width from 90 ft to 10 ft.
- This will leave a small section of the runway (a "box"), but it is necessary to keep the runway to avoid confusing the stock airport or causing it to malfunction.
- Leaving Key Data Intact:
- Do not remove the ARP point (the pink point on the map); leave it alone.
- Save and compile the 1S0 file again.
- Final Step:
- Leave 1S0 in the scenery, but note that 1S0 will only show as an empty airport (no runway, apron, or ramp).
- The new KPLU will overlap beneath the 1S0 layer. Don’t worry about this—it will work fine.
That is simply incorrect (or at least incomplete)
Decompile the default AP915150 using BGLXML, edit the resultant xml file with Notepad (or similar text editor) to remove the section pertaining to 1S0, then recompile using BGLCOMP from the FS2004 SDK
It's a procedure I use (as required) for my own benefit, but not one I'd recommend for redistribution.