Problem Fatal application exit: Orbiter_ng

NextBigLeap

Member
Joined
Jul 17, 2014
Messages
66
Reaction score
0
Points
6
Location
Portsmouth, RI
Using any time warp makes Orbiter_ng with D3D9 client crash saying 20141012_004500[1].jpg then the log says,

Finished setting up render state
Base Object 0x13A5B4A8 = 'Isidis Highlands DRM1 base' not cataloged
D3D9Client: [Scene Initialized]
Orbiter Version 100830
D3D9Client Build [Sep 30 2014]
Exception Code=0xC0000005, Address=0x03E0F8F9
EAX=0x00000000 EBX=0x0F59BB48 ECX=0x00000010 EDX=0x101C7250 ESI=0x00000000 EDI=0x101C7250 EBP=0x009FFC08 ESP=0x009FFBFC EIP=0x03E0F8F9
C:\Intel HD Graphics\New folder (2)\Modules\Plugin\D3D9Client.dll EntryPoint=0x03DD61D7, Base=0x03DD0000, Size=1384448
Exception in clbkRenderScene()
!!! Abnormal Program Termination !!!
 
Last edited:

kuddel

Donator
Donator
Joined
Apr 1, 2008
Messages
2,064
Reaction score
507
Points
113
Hi,

first I would sy it has nothing to to with time-warp. It just shortens the time 'till that base comes into view ;)
Now for the problem: 'Isidis Highlands DRM1 base' not cataloged seems to point into the root cause.
What addon do you run (that has a base with a name like that)?
The (D3D9)Client should not crash to desktop though, but I guess that the add-on is not completely installed. Many times an add-on depends on others, so a "readme" file should be read very carefully, too.
/Kuddel
 

PhantomCruiser

Wanderer
Moderator
Tutorial Publisher
Joined
Jan 23, 2009
Messages
5,603
Reaction score
168
Points
153
Location
Cleveland
Does it crash with any scenario? Meaning the stock Shuttle/DG/Shuttle-A scenarios?
Or only the Mars DRM?
 

NextBigLeap

Member
Joined
Jul 17, 2014
Messages
66
Reaction score
0
Points
6
Location
Portsmouth, RI
It crashes at random times, even without time warp but the time warp makes it crash more significantly more. I deleted the base files and still get fatal application error, the log is basically the same but without the base error. This all happens with any scenario, even the stock ones.
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiBlt
Colour key argument not supported by graphics client
---------------------------------------------------------------
Finished initialising panels
Finished setting up render state
D3D9Client: [Scene Initialized]
Orbiter Version 100830
D3D9Client Build [Sep 30 2014]
Exception Code=0xC0000005, Address=0x773F1830
EAX=0x00500050 EBX=0x00000000 ECX=0x00370000 EDX=0x0BA77C08 ESI=0x0BA77C08 EDI=0x56808E9A EBP=0x009FF628 ESP=0x009FF5FC EIP=0x773F1830
C:\windows\SYSTEM32\ntdll.dll EntryPoint=0x00000000, Base=0x77390000, Size=1404928
Exception in clbkRenderScene()
!!! Abnormal Program Termination !!!
 

kuddel

Donator
Donator
Joined
Apr 1, 2008
Messages
2,064
Reaction score
507
Points
113
O.K. Then would you try without any Module activated?
I mean something like MFDs etc. that are not part of the 'core' Orbiter installation.
I have the feeling that a Module (probably a vessel) is not compatible with external graphics client.
 
Top