General Question Launch Orbiter Runtime Error

[William Peek]

When I choose a scenario and hit launch/start button it goes to the load the scenario but it just stays on the loading scene. (Earth on top black space below/files being loaded flashing on bottom of screen) Except no files being loaded flash on screen. I have to ctrl/alt/del and end task. The only message I get is "Runtime Error". No details or anything. Has anyone seen this before?:facepalm:

 

[orb]

• Is it the same for every scenario?
  
  
• Can you post Orbiter.log?
  
  
• What graphics card do you have?
  
  
• Did you install any add-ons, and if so, which?

 

[orb]

Since it may help other people having the same issue, who will search the forums, here are more details from our conversation:

Thank you for responding.
I will try to answer your questions in the order received.

Is it the same for every scenario?:
Yes. I've even erased orbiter from my computer, re-installed it without any addons and on the first launch it crashes.

Can you post orbiter.log?:
I'm not a developer but if you can tell me where to find it I would be happy to post it here to you.

What graphics card do you have?:
I'm using an hp G50 Laptop
This is copied and pasted from dxdiag.
Card name: Mobile Intel(R) 45 Express Chipset Family (Microsoft Corporation - WDDM 1.1)
Manufacturer: Intel Corporation
Chip type: Mobile Intel(R) 4 Series Express Chipset Family
DAC type: Internal
Device Key: Enum\PCI\VEN_8086&DEV_2A42&SUBSYS_360B103C&REV_07
Display Memory: 1309 MB
Dedicated Memory: 64 MB
Shared Memory: 1245 MB

Did you install any addons?:
When the problem happened at first I had addons. I then erased ORBITER from my computer and reloaded it without addons and I'm getting the same crash.

Any help you can give is appreciated.
Thanks,
William Peek

The issue is with your graphics card not supporting hardware Transform & Lighting and Orbiter's "Local light sources" feature. {...} Just search the forums or ORBITER 2010 project to find a workaround or solution to the issue. It involves either editing the Orbiter configuration file, or otherwise installing Orbiter beta which has it fixed. There is also an article on the board telling you how to find the Orbiter.log or Orbiter.cfg files.

I have the local light sources turned off in Orbiter launch menu and the problem still persists. I also found orbiter.log and this is all that is on it...

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 4.73789e-007 sec
Found 0 joystick(s)
Devices enumerated: 4
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D HAL (Mobile Intel(R) 45 Express Chipset Family (Microsoft Corporation
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module CustomMFD.dll ......... [Build 100830, API 100830]
Module transx.dll ............ [Build 100824, API 100823]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1274 x 772 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
[highlight]Graphics: Active lights supported: -1[/highlight]

Did setting maximum light sources in the configuration file not help?

Actually, today I disabled local light sources and all is functioning properly. Thanks for the help.

Thanks,
William

You don't need to disable local light sources. Setting the following option in Orbiter.cfg:

MaxLights = 8

should also allow using local light sources on cards not supporting the hardware Transform & Lighting.

If simply that doesn't help, you may need to change the following option in Orbiter.cfg to TRUE:

EchoAllParams = [color=#c00][s]FALSE[/s][/color][color=#0a0]TRUE[/color]

For more information about the issue, see "Runtime-related crash with Local Light Sources activated" bug report.