[Software] C++ Runtime Libary error.

[Chub777]

I used to get a normal runtime error (like this one). I then activated "Local Light Sources" in the "Visual Effects" tab and tried the scenario again. This time I got this:





I can't seem to find the solution via search. Please help. Thanks.

[Face]

1. Insufficient input -do you use a vanilla Orbiter install? Which version?
2. The link is messed up. If you extract image link from it, you get the very same picture you inserted.

Please be more careful with your error descriptions, otherwise it is hard to help you or even understand what is the problem.

[Chub777]

Quote:

Originally Posted by Face

 1. Insufficient input -do you use a vanilla Orbiter install? Which version?
2. The link is messed up. If you extract image link from it, you get the very same picture you inserted.

Please be more careful with your error descriptions, otherwise it is hard to help you or even understand what is the problem.

1. I have an Orbiter installation with the following addons:

• Ariane 6
• Aerobrake MFD
• Antares
• Aurora (base)
• BaseSync MFD
• Columbus (station module)
• Comet (station module)
• Cupola (station module)
• CVEL Ariane 5
• Destiny (station module)
• Eranda (station module)
• Falcon 9/Dragon
• Galaxy (station module)
• ISS v3.2
• Jarvis HLV
• Jarvis (base)
• ITS (station module)
• Nebulus (station module)
• Neesys (station module)
• Novae (station module)
• Pirs-Progress (station module)
• Pollux Castor
• Pulsar (station module)
• Screen Capture
• Shuttle Fleet 4.7
• Soyuz FG/U
• Soyuz series
• Spacecraft 3
• UMMU
• Artmetis, Thermis and PMA
• Wideawake
• Zarya-J
• Mir-2
• URMS

It's the latest version (2010 P1).

2. Let me just fix this...also apologies for the vague description. I was in a rush.

EDIT; Link should be working.

[orb]

Quote:

Originally Posted by Chub777

 I then activated "Local Light Sources" in the "Visual Effects" tab and tried the scenario again.

Did you try with deactivated local light sources?

Does your Orbiter.log say this?:

Graphics: Active lights supported: -1

[Face]

Quote:

Originally Posted by Chub777

 1. I have an Orbiter installation with the following addons:

<snip long list>

It's the latest version (2010 P1).

Given your long list of addons, I'd propose to try the very basic bug-hunting work-flow first:

1. unzip a new vanilla Orbiter, try it with the core settings you want, check.
2. if not working, report to Orbiter's bugtracker.
3. if working, install one addon, check again.
4. if not working, contact the addon's developer with the problem, as it seems to be this addon causing the problem.
5. if working and there is another addon you want, install it and repeat at 4.
6. if working and all addons are installed, dance and be happy .

This should narrow down the cause of your problem to either the core or one of the addons.

At least try the vanilla install before guessing video settings.

regards,
Face

[Chub777]

Quote:

Originally Posted by orb

 Did you try with deactivated local light sources?

Does your Orbiter.log say this?:

Graphics: Active lights supported: -1

When I deactivated local light sources, I got a runtime error exactly the same as this one. I don't get this in my Orbiter.log, though:

Graphics: Active lights supported: -1

My Orbiter.log looks almost exactly the same with a CTD issue I had a while ago.

Quote:

Originally Posted by Face

 Given your long list of addons, I'd propose to try the very basic bug-hunting work-flow first:

1. unzip a new vanilla Orbiter, try it with the core settings you want, check.
2. if not working, report to Orbiter's bugtracker.
3. if working, install one addon, check again.
4. if not working, contact the addon's developer with the problem, as it seems to be this addon causing the problem.
5. if working and there is another addon you want, install it and repeat at 4.
6. if working and all addons are installed, dance and be happy .

This should narrow down the cause of your problem to either the core or one of the addons.

At least try the vanilla install before guessing video settings.

regards,
Face

Hmm, this will take a while...
EDIT: Turned local light sources on, started up the "Welcome" scenario on a clean Orbiter install. I got this:

[Face]

Quote:

Originally Posted by Chub777

 EDIT: Turned local light sources on, started up the "Welcome" scenario on a clean Orbiter install. I got this:

{image}

Could you please post the log for this clean Orbiter run, too? The generic error box there is close to useless, unfortunately...

[Chub777]

Quote:

Originally Posted by Face

 Could you please post the log for this clean Orbiter run, too? The generic error box there is close to useless, unfortunately...

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.80208e-007 sec
Found 0 joystick(s)
Devices enumerated: 4
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D HAL (Intel(R) Q45/Q43 Express Chipset (Microsoft Corporation - WDDM 1
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]

Nothing seems to be out of the ordinary.

[orb]

Could you please post Orbiter.log after the crash and not after closing the launchpad?

Could you post contents of Orbiter.cfg too.

Could you please read this article?

[Chub777]

Quote:

Originally Posted by orb

 Could you please post Orbiter.log after the crash and not after closing the launchpad?

Could you post contents of Orbiter.cfg too.

Could you please read this article?

1.After the crash, the launchpad closes automatically.
2.This was taken after the CTD:

; === ORBITER Master Configuration File ===
EchoAllParams = FALSE
LPadRect = 0 0 550 573

; === Visual parameters ===
EnableLocalLights = TRUE

; === Device settings ===
DeviceIndex = 2
ModeIndex = 6

3.Alright. I'm reading it.

[DaveS]

Quote:

Originally Posted by Chub777

 1.After the crash, the launchpad closes automatically.

In that case, go to the Extra tab, and then the Debugging options tree. Then doubleclick on Orbiter shutdown options and in the window that opens select the third option "Terminate Orbiter process".

[Chub777]

Quote:

Originally Posted by DaveS

 In that case, go to the Extra tab, and then the Debugging options tree. Then doubleclick on Orbiter shutdown options and in the window that opens select the third option "Terminate Orbiter process".

Still crashes automatically and I still get the "orbiter.exe has stopped responding" popup. Here's the log:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.80207e-007 sec
Found 0 joystick(s)
Devices enumerated: 4
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D HAL (Intel(R) Q45/Q43 Express Chipset (Microsoft Corporation - WDDM 1
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1018 x 740 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: -1

[orb]

Quote:

Originally Posted by Chub777

 1.After the crash, the launchpad closes automatically.

Does that mean that Orbiter crashes even before you click on the "Launch Orbiter" button? -- The Orbiter.log you have presented shows only what was logged but only before starting simulation.

If you run Orbiter (can be just the launchpad) after the crash, the file will be recreated with new data, which won't contain the last lines which were logged before the crash.

Or maybe, is your Orbiter installed in "Program Files (x86)"? If so, then there will be another Orbiter.log file in C:\Users\<your user name>\AppData\Local\VirtualStore\Program Files (x86)\<Orbiter folder>", which will contain the correct log.

[orb]

Quote:

Originally Posted by Chub777

 Still crashes automatically and I still get the "orbiter.exe has stopped responding" popup. Here's the log:

Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: -1

Please turn off the local light sources and try again.

[Chub777]

Quote:

Originally Posted by orb

 Does that mean that Orbiter crashes even before you click on the "Launch Orbiter" button? -- The Orbiter.log you have presented shows only what was logged but only before starting simulation.

If you run Orbiter (can be just the launchpad) after the crash, the file will be recreated with new data, which won't contain the last lines which were logged before the crash.

Or maybe, is your Orbiter installed in "Program Files (x86)"? If so, then there will be another Orbiter.log file in C:\Users\<your user name>\AppData\Local\VirtualStore\Program Files (x86)\<Orbiter folder>", which will contain the correct log.

No, Orbiter crashes after I click on the "Launch Orbiter" button but before anything else loads. In other words it happens immediately after I press the button.

Also, my vanilla Orbiter installation is located on my desktop, not in the "Orbiter_path" folder.