Problem Error "base not cataloged" - requesting help

[Dambuster]

Hi all,

I'm trying to chase down a bug I'm having in one large scenario with multiple addons running. Orbiter NG CTDs while the scenario is loading. The end of the log file is this:
D3D9: ERROR: Base Object 0x34A6A30 = 'Myron Base' not cataloged
D3D9: ERROR: Base Object 0x19686E08 = 'UCGO Base Europa' not cataloged
000000.000: D3D9: [Scene Initialized]

After searching I saw several other posts with this "base not cataloged" error, but haven't seen any details on how to resolve it.

Other scenarios in this install work without issues. I have also loaded another scenario with one of the above bases (Myron) and it works without issues and with the base present.

Thanks for any help!

 

[PDF]

I'm getting this same error message

 

[GodAtum]

I'm getting the same error too after installing Arrow for orbiter 2016

 

[Urwumpe]

I would maybe rename the thread to "Base object not catalogued" since the error message is not about the base... Maybe more people find it then.

And then, see this post here:

J

New Release Post in thread 'D3D9Client Development'

Apr 6, 2024

Why this:
D3D9: ERROR: Base Object 0x6A3A62B8 = 'Alcantara' not cataloged
D3D9: ERROR: Base Object 0x6A3A6640 = 'Al Anbar' not cataloged
D3D9: ERROR: Base Object 0x6A3A69C8 = 'Baikonur' not cataloged
D3D9: ERROR: Base Object 0x6A3A3BE0 = 'Barent Sea' not cataloged
D3D9: ERROR: Configuration file not found for object 0x6A39EE30
D3D9: ERROR: Configuration file not found for object 0x6A39EE30

I don't remember the story behind those errors but you can ignore them. I will try to solve it during the coming API cleanup.

• jarmonik

 

[jarmonik]

In Orbiter 2016 D3D9Client doesn't have access to a scenario information such as runway lights configuration etc... So, the client must reload all the configuration files starting from Scenario file to Sol.cfg, Planets and bases. The error is a result of inconsistency between what Orbiter has loaded and what D3D9Client has loaded. It should not cause CTDs.
This is no longer a problem in Orbiter 2024.