[Problem] Orbiter Crashes On Start-up

[SpecterFan]

I'm new to this forum so be kind.

I've been working with Orbiter for several days. I have been installing add-ons. I finally decided to try some of my handiwork.

I launch Orbiter. The opening screen comes up. Then I get a blank white screen. A small message pops up which says "Orbiter Crashed".

Any idea how to resolve this issue? I have included a copy of my current log file. Hopefully this will add some clue which will lead to a resolution.

As always, any and all help is always appreciated.
SpecterFan

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Found 1 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]
Module orbspotlight.dll [API v.060425]
Module ummufa.dll [API v.060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 32 bit
Render device: Fullscreen 1024 x 768
Device has hardware T&L capability
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
*** WARNING: Old-style texture contents file Earth_lmask.bin

[Scruce]

Quote:

Originally Posted by SpecterFan

 I've been working with Orbiter for several days. I have been installing add-ons. I finally decided to try some of my handiwork.

How do you mean by "handiwork"?

[Kveldulf]

From the looks of things, you've installed something wrong. I can't pinpoint the exact problem though, but it looks like a texture problem. Have you used any texture replacers?

The fastest solution would just be to delete Orbiter and use a clean install, but if you'd like, we can try and pinpoint the problem

[Rtyh-12]

First of all, to the forums!

Then, your problem seems to be with the Earth. Quite ironic, if you think about it... have you installed any texture replacements? If that doesn't solve your problem, try disabling orbspotlight and UMMUFA from the modules tab. Also, I can see you're using Orbiter 2006, an older version. Would you mind upgrading to 2010P1? It is waaaaay better than 2006. Just a tip, it's your choice, that's the beauty of Orbiter! Also, we're always kind!

[Scruce]

Quote:

VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
*** WARNING: Old-style texture contents file Earth_lmask.bin

I would say a texture addon made for O2010-P1 not O2006 would be the problem.

O2010-P1 Clean Install,
http://www.orbithangar.com/orbiter.php

[Rtyh-12]

Or that...

[SpecterFan]

By handiwork I mean all the add-ons I installed. I didn't purposely alter Orbiter in any way.

If I re-install Orbiter over itself, might that take care of the problem? I've done so much work, I don't want to start over again. I think I'd rather cure the textures problem.

[PhantomCruiser]

It might, it depends, have you added anything into the textures2 folder (like maybe the Seth Eden level10 Earth or something? Textures2 is where all the high-res textures hang out, and (normally) orbiter will load them if they are there.
It might be worthwhile to take a look at Generic Mod Enabler, you can pick and choose what mods are running in your installation. If something crashes, simply remove it, and load up again. If it works, you've found your culprit.

[SpecterFan]

I re-installed Orbiter and it still crashes. I found the bad texture referred to in the log file and tried renaming it to see if that would have an effect but it still did the same thing (i.e. loads the texture file).

[garyw]

Textures will never cause a CTD. Can you DELETE your orbiter.log file, relaunch orbiter, wait for it to crash then post the contents of the orbiter.log file and the content of the .scn file please?

You might want to wrap those in [code] tags for readability.

[SpecterFan]

I found another copy of the texture file in the Textures2 folder. I tried re-naming it like the other one. When I tried to launch Orbiter, it crashed again. The log file is different this time so I included a new copy.

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Found 1 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 32 bit
Render device: Fullscreen 1024 x 768
Device has hardware T&L capability
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564

[martins]

You appear to have corrupted your texture directory. You should not manually rename or remove files unless you know what you are doing. In this case it seems that you have renamed the texture file, but left the table of contents (.bin) in place, which is a bad idea.

You should try reinstalling Orbiter from scratch (not over an existing installation!) without any addons or texture updates. This will get rid of the texture version warning and hopefully avoid the crash. Once this works you can try re-installing the texture packs, but only those valid for Orbiter 2006. If you install any textures for 2010 you are asking for trouble.

I assume you have a reason for using Orbiter 2006.

[SpecterFan]

I'm using Orbiter 2006 because the add-ons were primarily for 2006.

I installed three add-ons for 2010. Can I go back and remove those? What about add-ons intended for earlier versions of Orbiter? Would add-ons intended for 2006 work in 2010?

[Wishbone]

What exactly prevents you from having two setups - the 2006 and the 2010 ones?

[fireballs619]

I think the best solution here after a reinstall is to simply have two installs of Orbiter at once; One O2006, and another O2010-P1. This way, you have access to essentially all add-ons, and you won't have the problem of working with older versions.