Hello:
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...
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...
Code:
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)
