Saturn & Uranus Crash Program

[DC]

I am using a Pentium 2 w/384 Mgb of Ram and Win98 and a Riva TNT w/16Mgb of Ram. The program runs fine except when I try to see or goto Saturn or Uranus. I have tried to sneak in by going to one of the moons of the planet and even in the demo when it tries to goto Saturn I get the illegal operation stating that a fault in NV4ogl.dll. I believe I have the current driver. Any help would be appreciated.

[ogg]

repeatedly had a similar problem, until I went to Windows Update and got the latest *Windows* driver from there for my (generic) graphics card. Ie not the one from the card manufacturer. Don't know if that helps, but good luck.

ogg

[George]

I am using a Pentium 2 w/384 Mgb of Ram and Win98 and a Riva TNT w/16Mgb of Ram. The program runs fine except when I try to see or goto Saturn or Uranus. I have tried to sneak in by going to one of the moons of the planet and even in the demo when it tries to goto Saturn I get the illegal operation stating that a fault in NV4ogl.dll. I believe I have the current driver. Any help would be appreciated.

I have exactly the same Problem on my Linux box, witch has also a Riva TNT2 Card inside. I'm working with the original Nvidia X-Server 1.0 for Linux. Celestia crashes with a "Memory Access Failure" when i go to Saturn/Uranus

[DragonSpirit]

http://www.celestiaproject.net/forum/viewtopic.php?t=512
"How to avoid crashes on Saturn flight."

Wish people woudl do this, as this topic has been posted in four or more places and with about 25 posts to those topics. If only people would open their eyes and read before freaking out.

Dragon

[marco]

Hello,

Well, I did try adding the line:

nSimultaneousTextures = 1;

and recompiling but Celestia still crashes (segfaults) on Saturn.
Here is the gdb session (I start celestia, select object Saturn
and type "G"):

reimeika% gdb /usr/local/bin/celestia
GNU gdb Red Hat Linux (5.1.90CVS-5)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
(gdb) run
Starting program: /usr/local/bin/celestia-1.2.4/bin/celestia
[New Thread 1024 (LWP 12252)]
Parent body 'BD -10 3166' of 'b' not found.
fv: 6
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 12252)]
0x0815ab28 in glActiveTextureARB ()
(gdb) quit
The program is running. Exit anyway? (y or n) y

The above happens whether I apply the workaround or
not, the only difference being that in the latter case the
"glClientActiveTextureARB" line reads:

0x0815ab4f in glClientActiveTextureARB ()

I'm running Red Hat 7.3, and the glx.h header states:
/* $XFree86: xc/include/GL/glx.h,v 1.7 2000/06/30 18:27:00 dawes Exp $ */

According to rpm I have:

XFree86-4.2.0-8
XFree86-devel-4.2.0-8

My video card is an ATI Radeon 7500 w/64MB. If you
need any more info please feel free to contact me at:
marco@reimeika.ca

Celestia is wonderful BTW.

Cheers!

[t00fri]

Marco:

did your really double check that you placed the

nSimultaneousTextures=1;

statement at the correct place!?

You are the first one where this does not seem to help...

Bye Fridger

[marco]

Hi,

I'm sorry, my fault. The workaround says:
"add right behind the lines" which I interpreted
as adding "before the lines". Adding:

nSimultaneousTextures = 1;

*after* them does the trick. Sorry for the
confusion, and thanks for the help!

[billybob884]

Not to be rude, but I think your computers are just too slow because I havent had any problems at all.

[ogg]

Not a slowness thing, Billybob. I'm getting a very good framerate on my machine and it's buggy on the rings. Always has been. It's just an OpenGL compatibility problem that some have due to their specific graphics cards not supporting the extensions... or at least that's what my problem seems to be. If you have no problems, hooray for you. But when everything else works fine and just one feature causes the whole thing to go pear-shaped, it can be somewhat frustrating.