begin program (location IO)
i enter "hubble"
hit G
zoom nicely towards hubble
when i get close... close enough to where detail of hubble begins
slight pause... error... then XP must close program
no crash problem if i zoom in my self... very slowly
in a few cases it left "celestia.exe" process running
this happened when i used "win98/ME compatability mode"
and tried alt-enter fullscreen...
"Runtime Error!
Program:C:\blahblah\celestia.exe
abnormal program termination"
DELL INSPIRON 8100 LAPTOP
16MB GForce 2 Go Mobile
XP - 320MB - 3/10G freespace
all drivers up-to-date
<<POSSIBLE CAUSE>>
netmeeting running in background
hope this helps
hubble - goto - crash on arrival
Similar crashes
I get similar crahses, when the program just freezes. It happens when I go to a satellite, and try to put the Earth in the window. The program just stops.
Computer:
Celeron 700 MHz
128 MB RAM
20GB hard drive
NVidia TNT2 M64 32MB Video Card
Celestia, V 1.2.4
Win ME
Can anyone help?
Computer:
Celeron 700 MHz
128 MB RAM
20GB hard drive
NVidia TNT2 M64 32MB Video Card
Celestia, V 1.2.4
Win ME
Can anyone help?
I'm just guessing here, since it works fine for me...
In 1.2.4 when you GoTo Hubble from the opening screen at Io, right now the trajectory takes you through the Earth object. Maybe the OpenGL routines that you're using get unhappy when they try to draw that situation?
What versions of the graphics device drivers are you folks using?
(I'm at work, so I'm running NT4sp6, 2GHz P4, ATI Rage 128 Pro Ultra, OpenGL v 1.2.1517 according to Celestia's OpengL Driver Info)
In 1.2.4 when you GoTo Hubble from the opening screen at Io, right now the trajectory takes you through the Earth object. Maybe the OpenGL routines that you're using get unhappy when they try to draw that situation?
What versions of the graphics device drivers are you folks using?
(I'm at work, so I'm running NT4sp6, 2GHz P4, ATI Rage 128 Pro Ultra, OpenGL v 1.2.1517 according to Celestia's OpengL Driver Info)
Selden
OpenGl Version
I'm using OpenGL version 1.3.1, but it says max simultaneous textures: 2. Could that be the problem?