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

P3D v4 Unable to compile in 1.7.0; unable to use compilations from 1.7.5


In the interest of brevity, I've redacted large portions of my original post. If I've inadvertently left out any critical details, I apologize. Disclaimer: I've never used ADE before undertaking this task, and I am by no means knowledgeable with scenery development. Any advice/assistance is appreciated!

I recently converted to P3D(v4) and I've been trying to tweak the old FS scenery files I've been using. The only problem I've observed is that the taxiways aren't consistently displayed, so I end up seeing taxi lines through grass. I found this article that explained the problem, and indeed the fix worked. I've been able to patch many of the scenery files I have and get them to display properly in P3D. I've been running into issues that I haven't been able to overcome, though, and I'm looking for help.

As I understand it, 1.75 is the beta version that's P3Dv4 compatible. With this new version, I'm able to compile my patches without any errors from ADE; however, I was running into issues Aivlasoft EFB recognizing the scenery. EFB seems to flat out reject anything compiled by 1.7.5 with an error "Unknown Id 003E in Airport-Structure, Filename: my_bgl.bgl" and thus none of my patched works load properly. I dug around and found this thread which indicated that 1.7.0 compiles files compatible with EFB. Accordingly, I installed 1.7.0, pointed it at my P3Dv4 installation, and it worked much better.

I haven't figured out what the scenery files have in common, but I'm finding that occasionally I can't patch an airport in 1.7.0. When I import the airport, it loads fine, but when I go to compile the airport again (even without editing anything), I get an unhandled exception (I've included it below).

In every case I've encountered, the same scenery file both imports and compiles properly in 1.7.5; however, the product isn't compatible with other addons, so I can't use it as intended.

I'm sure I'm doing something wrong, but I just don't know enough about the task I'm undertaking to figure it out. Any help would be greatly appreciated. I just want to get my old scenery files displaying properly in P3D and still usable with EFB.

The issue may seem fairly petty with EFB compatibility; however, EFB has a "feature" that renders the software almost completely unusable for airports where it detects a runway mismatch. If the AIRAC and FS scenery don't match up on runway data, EFB disables runway selection (which precludes the user from selecting any procedures [departure/arrival/approach]) at the airport. So, for airports that have had runway changes (either new runways, or simply renumbered runways), it's important that I get EFB to recognize the scenery file.

Thank you in advance for your time...

System.Exception: Unknown ID 62 found in airport record
   at ScruffyDuck.Flightsim.Scenery.SceneryObject.Airport.decompileVariableEntries(Byte[] rawData, Int32 localPointer)
   at ScruffyDuck.Flightsim.Scenery.SceneryObject.Airport.Decompile(Byte[] rawData)
   at ScruffyDuck.Flightsim.Scenery.SceneryObject.Airport..ctor(String objectName, Byte[] rawData, Int32 offset, SceneryBase parent)
   at ScruffyDuck.Flightsim.Scenery.SceneryFile.ObjectFactory.New(String newType, String newName, Byte[] rawData, Int32 offset, SceneryBase parent)
   at ScruffyDuck.Flightsim.Scenery.SceneryFile.ObjectFactory.New(SceneryObjectType newType, String newName, Byte[] rawData, Int32 offset, SceneryBase parent)
   at ScruffyDuck.Flightsim.Scenery.SceneryFile.SceneryFile.processAirport(Int32 pointer)
   at ScruffyDuck.Flightsim.Scenery.SceneryFile.SceneryFile.processSelectedSection(SectionPointer currentSection, GeneralSectionHeader currentSubSection, Int32& p2)
   at ScruffyDuck.Flightsim.Scenery.SceneryFile.SceneryFile.processGeneralSection(SectionPointer currentSection)
   at ScruffyDuck.Flightsim.Scenery.SceneryFile.SceneryFile.DecompileFull()
   at ScruffyDuck.Flightsim.Scenery.SceneryFile.SceneryFile.Decompile(DecompileType decompileType)
   at ScruffyDuck.AirportDesignEditor.MainForm.postProcessApronEdgeLightProperties(String sourceBglPath)
   at ScruffyDuck.AirportDesignEditor.MainForm.CompileProject()
   at ScruffyDuck.AirportDesignEditor.MainForm.OnCompileOptionsStatusChanged(Boolean compile, Boolean statusChanged)
   at ScruffyDuck.AirportDesignEditor.Helpers.ProjectPropertiesCompileOptions.OnSaveClick(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
You posted an error message from ADE. I don't think that comes from ADE v1.75. If it is coming from 1.70 or 1.71 then that is what I would expect. LM changed the format of the bgl file in P3D v4 and 1.75 deals with that but 1.70 does not
You posted an error message from ADE. I don't think that comes from ADE v1.75. If it is coming from 1.70 or 1.71 then that is what I would expect. LM changed the format of the bgl file in P3D v4 and 1.75 deals with that but 1.70 does not

Thank you. Yes, I should have clarified. The exception happens on 1.70. I found this thread and this webpage, and used the BglViewer tool to find that 1.75 seems to be inserting a field at offset 0180 that seems to be what EFB is complaining about. Is there any way to get 1.75 to compile in "legacy mode" or something of the sort, where the Bgl would still be compatible? Or am I going about this all wrong?
Okay, my initial finding was incorrect; offset 0180 is not a static thing. I just tried a different scenery, and the offset is different, but according to BglViewer, it's the same blank field right after the airport name.
So, I did some more research. According to this link, the "Name" field section should have three... "items" ... and on all of the compiled bgl files that I'm having trouble with, there's a fourth blank item which seems to correspond to where EFB chokes up at.

Is this something I can rectify?
It seems this issue is with EFB. Have you contacted the developer? They may need to make some changes to their software to support the new P3D v4 bgl format. ADE handles and compiles the changes correctly. There are changes to three airport elements in P3D v4 - taxipath, runway and apron. There are no changes in the airport header. The developer of EFB is aware of the format changes.