Software Scenario Causes Shutdown

[EaslMar]

I have downloaded Spaceballs Eagle 5 addon, and when I start the "Eagle 5 and DG in orbit" scenario, the simulator loads, then shuts down with a Windows message, "A problem caused orbiter.exe to stop working correctly. Windows will close the program..." It happens every time and I do not know what is causing it. Has anyone ever experienced this, or has any suggestions?

Thanks!

 

[Woo482]

to Orbiter-Forum !, showing us your "Orbiter.log" found in the same directory as the Orbiter.exe will probably help us find out what's causing the crash

 

[EaslMar]

This is what is in the Orbiter.log file, is this what you were looking for?

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

 

[Lucy]

Is that the whole file?

Does this crash occur with other scenarios? (Ones which don't include the Eagle 5)

 

[EaslMar]

Yes, that's all that was in the file.

And yes, it only happens with that scenario.

 

[Woo482]

Windows Vista / 7 Shouldn't really cause a crash, it's more likely he's missing spacecraft3 or something else the addon requires

 

[Woo482]

I'm pretty sure you'll get a similar message in Windows XP if a application crashes... so Windows Vista / 7 probably isn't the problem...

 

[orb]

This is what is in the Orbiter.log file, is this what you were looking for?

Is this the Orbiter.log after the crash, or did you run Orbiter.exe again?

Orbiter Launchpad overwrites this file with new log data. Make sure you copy the content of Orbiter.log just after the crash.

 

[Hielor]

No, if that message comes up, then Vista or Seven is the problem. Try and wipe the Problem reporting EXE off.

Um, no.

If you turn off "problem reporting," Orbiter will still crash, you just won't get that helpful message telling you about it.

 

[EaslMar]

I do have Vista, and I also have spacecraft3--it was included with the addon download.

Getting rid of the problem reporting .exe wouldn't really fix the problem, would it? Wouldn't it just prevent the computer from telling me there was a problem? And might deleting that cause problems with other applications?

I ran it again, here is the new .log:

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Found 0 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 16 bit
Render device: Fullscreen 800 x 600
Device has no 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
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll [API v.060425]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll [API v.060425]
Module Deimos.dll [API v.060425]
Module Galsat.dll [API v.041022]
Module Jupiter.dll [API v.050206]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll [API v.041022]
Module Europa.dll [API v.041022]
Module Ganymede.dll [API v.041022]
Module Callisto.dll [API v.041022]
Module Satsat.dll [API v.050206]
Module Saturn.dll [API v.060425]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll [API v.050206]
SATSAT Mimas: Terms 113
Module Enceladus.dll [API v.050206]
SATSAT Enceladus: Terms 33
Module Tethys.dll [API v.050206]
SATSAT Tethys: Terms 101
Module Dione.dll [API v.050206]
SATSAT Dione: Terms 59
Module Rhea.dll [API v.050206]
SATSAT Rhea: Terms 68
Module Titan.dll [API v.050206]
SATSAT Titan: Terms 100
Module Hyperion.dll [API v.050206]
SATSAT Hyperion: Terms 595
Module Iapetus.dll [API v.050206]
SATSAT Iapetus: Terms 605
Module Uranus.dll [API v.050206]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll [API v.060425]
Module Ariel.dll [API v.060425]
Module Umbriel.dll [API v.060425]
Module Titania.dll [API v.060425]
Module Oberon.dll [API v.060425]
Module Neptune.dll [API v.050206]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Module Triton.dll [API v.060425]
Finished initialising world
Module Spacecraft3.dll [API v.050206]
**** WARNING: Mesh not found: .\Meshes\.msh
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh

This looks better--and look at the bottom. It's missing a mesh. Does anyone know what could have caused that, and how do I fix this? Do I need to get the mesh from somewhere?

 

[Hielor]

Open the scenario file in notepad and look for the following line:

DeltaGlider01:Spacecraft\Spacecraft3

Change it to

DeltaGlider01:DeltaGlider

It looks like the original author used a spacecraft3 version of the delta-glider instead of the normal one.

 

[EaslMar]

That worked! Thanks a lot for the help.

 

[EaslMar]

All right, I've got another problem. I installed another addon and ran one of the scenarios that came with it, but when I tried to rotate the external view, the horizontal arrows, instead of moving sideways around the spacecraft, tipped the entire view over sideways (instead of rotating around the spacecraft it rotated the camera view). I thought it might have had something to do with the addon so I removed the addon files, but the problem remained. It didn't cause any other problems--just the external view. Any ideas what's going on here?

 

[Lucy]

Try pressing F2 while in external view mode.

 

[Hielor]

All right, I've got another problem. I installed another addon and ran one of the scenarios that came with it, but when I tried to rotate the external view, the horizontal arrows, instead of moving sideways around the spacecraft, tipped the entire view over sideways (instead of rotating around the spacecraft it rotated the camera view). I thought it might have had something to do with the addon so I removed the addon files, but the problem remained. It didn't cause any other problems--just the external view. Any ideas what's going on here?

Hit F2.
Orbiter.pdf, page 23--"F2: Toggle tracking mode for external camera views"

 

[EaslMar]

Wow, is it really that obvious? :lol: I must have missed that when I looked in the manual. I'm not at my Orbiter computer right now, but I'll try that later today. Once again, thanks!!

 

[Izack]

Yes, you were in Global Frame, which means the orientation of your spacecraft has no bearing on the orientation of the camera. In Global frame the camera traverses the plane of the ecliptic, while in Target relative mode the camera traverses whatever plane your ship is pointing in. So if you're pointing along your orbital plane, and your inclination is 0.00 degrees to the ecliptic, global frame will look 'normal' for you.

 

[EaslMar]

Tried it and it worked--one again thanks a lot!