Problem Fatal Application Exit

[Damascus]

I hadn't used orbiter in a while and I got a CTD every time I tried so I re-installed everything: base files, hi-res Earth, Moon and Mars, planets, Orbiter Sound 4.0, UCGO, and DG IV. Using Orbiter_ng.exe, I get this Fatal Application Exit on every scenario. Depending on the scenario, the error is different. Sometimes it mentions RegisterVisObject (DeltaGliderIV), sometimes D3D9 Client (if I'm not using the DG4). Very confused.

 

[orb]

Is the Fatal Application Exit happening only with Orbiter_NG + D3D9Client? If so, post contents of D3D9Client.log and Orbiter.log.

 

[Damascus]

I like D3D9 with the UCGO addons so I use that. If I use orbiter.exe, it crashes immediately. Orbiter.log is attached; there is no D3D9Client.log that I could find.

 

[Lucy]

I like D3D9 with the UCGO addons so I use that. If I use orbiter.exe, it crashes immediately. Orbiter.log is attached; there is no D3D9Client.log that I could find.

If you're trying to use the D3D9 client with orbiter.exe then it won't work. orbiter.exe has its own graphics client and should refuse to load others if I recall correctly, which would explain that crash. Does it happen without that module enabled?

Your log shows that the client loaded, and the absence of anything after that strongly suggests there was a problem with the client itself. As a starting point, I recommend you download the DirectX 9 runtimes - it's a web installer which pulls in the Dx9 runtimes not included in Windows 7.

 

[orb]

I like D3D9 with the UCGO addons so I use that. If I use orbiter.exe, it crashes immediately. Orbiter.log is attached; there is no D3D9Client.log that I could find.

The Orbiter.log gets overwritten when you re-run Orbiter. The one you attached contains only modules loaded up to the launchpad, as there's no "Creating Simulation Session" logged. If the launchpad appears without CTDing, then the Orbiter.log you posted won't help finding the problem. You need to get the Orbiter.log just after the crash.

D3D9ClientLog.html file where D3D9Client's events are logged is located in Modules/D3D9Client subdirectory of Orbiter.

 

[Damascus]

Thanks for the quick response. I found the D3D9 log and have attached it. (BTW, there is also a D3D9Client20 directory.) The orbiter.log is the one after the crash. The program crashes while loading; I can access the launchpad freely but can't run any scenario. I have Windows XP and use orbiter_ng.exe. DirectX says I am up-to-date.

.

---------- Post added at 02:53 PM ---------- Previous post was at 02:51 PM ----------

I see I didn't send the attachment. I tried again and it said it was an invalid file so here it is in all its glory.

D3D9Client Log




(0: 0.01s 7132940663us)(0x2E4) [nVidia API Initialized]
(1: 0.02s 7132946534us)(0x2E4) ================ clbkInitialise ===============
(2: 0.02s 7132946624us)(0x2E4) Orbiter Version = 100830
(3: 0.03s 7132958292us)(0x2E4) Index:0 640 x 480 60Hz (22)
(4: 0.03s 7132958540us)(0x2E4) Index:1 640 x 480 70Hz (22)
(5: 0.03s 7132959417us)(0x2E4) Index:2 640 x 480 72Hz (22)
(6: 0.03s 7132960046us)(0x2E4) Index:3 640 x 480 75Hz (22)
(7: 0.03s 7132960673us)(0x2E4) Index:4 720 x 480 60Hz (22)
(8: 0.03s 7132961304us)(0x2E4) Index:5 720 x 576 60Hz (22)
(9: 0.03s 7132961932us)(0x2E4) Index:6 800 x 600 60Hz (22)
(10: 0.03s 7132962562us)(0x2E4) Index:7 800 x 600 70Hz (22)
(11: 0.03s 7132963193us)(0x2E4) Index:8 800 x 600 72Hz (22)
(12: 0.03s 7132963821us)(0x2E4) Index:9 800 x 600 75Hz (22)
(13: 0.03s 7132964463us)(0x2E4) Index:10 1024 x 768 60Hz (22)
(14: 0.03s 7132965096us)(0x2E4) Index:11 1024 x 768 70Hz (22)
(15: 0.04s 7132965724us)(0x2E4) Index:12 1024 x 768 72Hz (22)
(16: 0.04s 7132966355us)(0x2E4) Index:13 1024 x 768 75Hz (22)
(17: 0.04s 7132966986us)(0x2E4) Index:14 1152 x 864 60Hz (22)
(18: 0.04s 7132967612us)(0x2E4) Index:15 1152 x 864 70Hz (22)
(19: 0.04s 7132968246us)(0x2E4) Index:16 1152 x 864 72Hz (22)
(20: 0.04s 7132968873us)(0x2E4) Index:17 1152 x 864 75Hz (22)
(21: 0.04s 7132969505us)(0x2E4) Index:18 1280 x 720 60Hz (22)
(22: 0.04s 7132970136us)(0x2E4) Index:19 1280 x 768 60Hz (22)
(23: 0.04s 7132970761us)(0x2E4) Index:20 1280 x 768 70Hz (22)
(24: 0.04s 7132971413us)(0x2E4) Index:21 1280 x 768 72Hz (22)
(25: 0.04s 7132974860us)(0x2E4) Index:22 1280 x 768 75Hz (22)
(26: 0.05s 7132975508us)(0x2E4) Index:23 1280 x 800 60Hz (22)
(27: 0.05s 7132976148us)(0x2E4) Index:24 1280 x 800 70Hz (22)
(28: 0.05s 7132976783us)(0x2E4) Index:25 1280 x 800 72Hz (22)
(29: 0.05s 7132977412us)(0x2E4) Index:26 1280 x 800 75Hz (22)
(30: 0.05s 7132978045us)(0x2E4) Index:27 1280 x 960 60Hz (22)
(31: 0.05s 7132978691us)(0x2E4) Index:28 1280 x 960 70Hz (22)
(32: 0.05s 7132979320us)(0x2E4) Index:29 1280 x 960 72Hz (22)
(33: 0.05s 7132979955us)(0x2E4) Index:30 1280 x 960 75Hz (22)
(34: 0.05s 7132980242us)(0x2E4) Index:31 1280 x 1024 60Hz (22)
(35: 0.05s 7132980450us)(0x2E4) Index:32 1280 x 1024 70Hz (22)
(36: 0.05s 7132980563us)(0x2E4) Index:33 1280 x 1024 72Hz (22)
(37: 12.28s 7145207785us)(0x2E4) Node[0] = D3D9ClientRescue (0x6EF08)
(38: 12.28s 7145207891us)(0x2E4) Scenario = .\Scenarios\D3D9ClientRescue.scn
(39: 12.51s 7145442586us)(0x2E4) D3D9Client destructor called
(40: 12.54s 7145472314us)(0x2E4) --------------ExitModule------------
(41: 12.65s 7145580836us)(0x2E4) Log Closed

 

[DaveS]

Here's what you need to do for us to get the correct logs:

1. Press the "Extra" button in the Orbiter Launchpad
2. Click on the bottom most option titled "Debugging options"
3. Open "Orbiter shutdown options"
4. Makes sure either "Terminate Orbiter process" or "De-allocate memory and display launchpad dialog" is selected
5. Exit and re-launch Orbiter_ng to make sure the changes will have taken effect
6. Now re-run the problematic scenario(s) and post the logs, this time inside CODE brackets to minimize scrolling

 

[Damascus]

All of this was already checked. Now I can't get to the launchpad, which I was able to reach earlier. I don't know what you mean by "inside code brackets," but the D3D9 file is the same exact file as before.

 

[orb]

The Orbiter.log is still too short. What's the path to your Orbiter directory?

Also, if you can access the Launchpad, in the Video tab click "Advanced" button and change the "Debug level" to 4, and then attach the D3D9ClientLog.html after the crash while loading scenario. You can either place it inside [code][/code] tags, or attach it to post in a ZIP archive.

 

[Damascus]

Let's start fresh. I installed all of Orbiter except the D3D9Client and it works fine. (Occasionally it crashes when I hit CTRL-Q to exit.) I have a D3D9ClientR12.zip ready to use. When I unzip it, should I overwrite all the folders or copy the contents of the D3D9 folders (config, doc, modules, texture, mesh) to the appropriate existing Orbiter folders?

I installed the D3D9 by putting its files into Orbiter, but that didn't work as the D3D9 wasn't listed in the modules part of the launchpad and the advanced button wasn't there to set up the links. So I just unzipped it into Orbiter, selected the links and the D3D9 module and it crashed as usual. Attached are the two logs. (Orbiter is now on the E:\ drive.)

 

[kuddel]

Hi Damascus,

it seems we're getting closer

Let's start fresh. I installed all of Orbiter except the D3D9Client and it works fine.

O.K. The step-by-step approach is the best thing to do :thumbup:

(Occasionally it crashes when I hit CTRL-Q to exit.)

Hmm, this should not happen, but that might be another issue.

I have a D3D9ClientR12.zip ready to use. When I unzip it, should I overwrite all the folders or copy the contents of the D3D9 folders (config, doc, modules, texture, mesh) to the appropriate existing Orbiter folders?

Yes!
For example: A file contained in folder "Modules" of the D3D9Client ZIP should be ending up in the "Modules" folder of your Orbiter installation directory.

I installed the D3D9 by putting its files into Orbiter, but that didn't work as the D3D9 wasn't listed in the modules part of the launchpad and the advanced button wasn't there to set up the links. So I just unzipped it into Orbiter, selected the links and the D3D9 module and it crashed as usual.

Looking at the log you've attached it looks like you've extracted the D3D9Client correctly.

Attached are the two logs. (Orbiter is now on the E:\ drive.)

It looks like you've started the following scenario: ".\Scenarios\DeltaGliderIV\Earth Scenary\Landed KCS departure to ISS.scn".
This isn't in the base Orbiter install and also not in the D3D9Client zip.
Did you also install "DeltaGlider IV"? you shouldn't (for now)!
Anyway, could you please perform only these steps:

1. Install (unzip) Orbiter (only Orbiter, as you did the last time)
2. Install (unzip) D3D9Client into that same directory, preserving the directory structure.
3. Start orbiter_ng.exe, activate D3D9Client, setup your video-settings and close the launchpad.
4. Restart orbiter_ng.exe and select the Scenario ".\Scenarios\Delta-glider\DG Mk4 in orbit.scn" (this is included in the Orbiter-Base installation. So we don't have to worry about any further addon-incompatibilities)

If it still crashes, post the logs (Orbiter.log & D3D9ClientLog.html located under ".\Modules\D3D9Client")
Packed in one ZIP would be more convenient for us

 

[Damascus]

No crash following your instructions. ALSO: No crash running that scenario, or any other non-DG-IV scenario under D3D9 in the original Orbiter folder (the one that crashes). It seems that the add-on is the problem.

 

[kuddel]

No crash following your instructions.

Great.

ALSO: No crash running that scenario, or any other non-DG-IV scenario under D3D9 in the original Orbiter folder (the one that crashes).

Even better

It seems that the add-on is the problem

Aha.
Although I do not really know if (or if not) the Delta Glider IV is D3DClient-compatible, I have the feeling that I've had issues with that addon, too.
I'll check later if I can find some GO/NO-GO for that addon.

Regards,
Kuddel