Problem Orbiter crashes after startup

[Plutonium239]

Hello,

I've searched this forum and the internet and I couldn't find a solution for this problem. Earlier today I downloaded Orbiter for the first time and I decided to try the "Space Shuttle to ISS" tutorial. It started working, but it said I should enable LuaMFD. So I quit, restarted the simulator, and checked the "ScriptMFD" box by mistake (I don't think this is the problem, though). I tried the tutorial with it enabled, but it stopped working, so I restarted it and enabled LuaMFD, but it crashed again. I thought I broke it, so I just reinstalled Orbiter. The simulator will still not work even when no boxes are checked. Do any of you know how I can fix this problem? Here are the contents of the log:

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 4.46221e-007 sec
Found 0 joystick(s)
Devices enumerated: 4
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D HAL (Intel(R) HD Graphics 3000)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]

 

[Matias Saibene]

A question.

[FONT="<font><font>Verdana</font></font>"]Hello Plutonium239[/FONT].

Before dialing mistakenly ScripMFD box, Orbiter worked?

I await your response, and I hope to help you.

 

[Plutonium239]

[FONT="<font><font>Verdana</font></font>"]Hello Plutonium239[/FONT].

Before dialing mistakenly ScripMFD box, Orbiter worked?

I await your response, and I hope to help you.

Yes. With ScriptMFD it crashed, and even when I restarted Orbiter and replaced it with LuaMFD it wouldn't work.

 

[Matias Saibene]

Another question

Do you have installed C + + and updates relevant?

 

[Plutonium239]

I believe I do. That is under the advanced installation options in the MSI, right? I used that.

 

[Matias Saibene]

Very well, I will investigate a bit about it. :compbash2: :compbash:
Best regards.

 

[Plutonium239]

Very well, I will investigate a bit about it. :compbash2: :compbash:
Best regards.

I checked the MSI installer and there is no C++ update. I would assume that mine is new enough (this computer was made after 2010), but what version would I need? I don't want to send you on a pointless mission.

 

[garyw]

Is that all that's in the orbiter.log file after the crash? What pop up do you see when orbiter has crashed?

 

[orb]

Is that all that's in the orbiter.log file after the crash?

I don't think so, as it's orbiter.log file yet before launching any scenario.

But I'm guessing it's local light sources, because of no hardware T&L. :crystalball2:

 

[Matias Saibene]

Some questions...

What directory has used to install Orbiter?
What is your operating system?
What error message appears immediately after CTD (Crash to Desktop)
Meanwhile I go search in the forum "problems with LUA Script" :sos:
Greetings.

 

[Plutonium239]

Operating system: Windows 7 Home Premium Service Pack 1 (x64)

It installs itself in My Documents, which is strange. The error I get is "orbiter.exe has stopped working / Windows can check online for a solution to the problem." Also, those are the only contents of the orbiter.log file.

 

[orb]

Did you enable local light sources (and if you don't know, post the orbiter.cfg file)? If so, did you include a workaround for the bug of negative number of supported local light sources in your orbiter.cfg (already fixed in Orbiter beta 100903)?

Also, the orbiter.log you posted earlier isn't from the time just after the crash when launching simulation, but from after closing the Orbiter Launchpad normally later. You need to open the orbiter.log just after the crash, without re-running Orbiter.

It isn't an issue that it's installed in the Documents folder.

 

[Plutonium239]

Did you enable local light sources (and if you don't know, post the orbiter.cfg file)? If so, did you include a workaround for the bug of negative number of supported local light sources in your orbiter.cfg (already fixed in Orbiter beta 100903)?

Also, the orbiter.log you posted earlier isn't from the time just after the crash when launching simulation, but from after closing the Orbiter Launchpad normally later. You need to open the orbiter.log just after the crash, without re-running Orbiter.

It isn't an issue that it's installed in the Documents folder.

Here is the second part of orbiter.log that comes after the part I posted before:

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1360 x 740 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: -1
Loading 15382 records from star database
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Finished initialising world

And I'm not sure about local light sources, so here is the CFG file. It seems short, so I'm not sure if it's what you need.

; === ORBITER Master Configuration File ===
EchoAllParams = FALSE
LPadRect = 161 145 711 718

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

; === Active plugin list ===
ACTIVE_MODULES
  LuaMFD
END_MODULES

 

[garyw]

Local lights are not supported:

Graphics: Active lights supported: -1

That could be your problem

 

[Matias Saibene]

Possible solution

It happened to me just the same. I think the solution is to add this line in the file Orbiter.cfg below the lines ==Visual Parameters == ==

MaxLights = 8

 

[Plutonium239]

I added:

; === Visual parameters ===
MaxLights = 8

But it stops working at the same point as before. Is this the correct format?

 

[Loru]

First of all you have to disable local light sources as your GPU doesn't suport them.

Make sure it's unticked in visual effects tab

 

[Plutonium239]

It has been unchecked. I tried configuring it exactly as you have it in the picture, but it still does not work. I brought it back to how I had it, but thanks.

 

[orb]

Strange, I can't see LuaMFD.dll present in your orbiter.log, though it's included to be loaded in orbiter.cfg.

 

[Loru]

Can you move orbiter outside windows?? Copy entire folder to for example c:\orbiter or d:\orbiter.