Celestia Forums

Hi folks,

I've downloaded the latest modified sourcefiles from cvs. The modifications of the source files are concerning "added new fragment programs for per pixel specular on GeForce hardware". After compilation I run Celestia and go to Earth. At that moment, when I change the OpenGl renderpath with Ctrl-V, Celestia will crash. When I go to some other object in space e.g. Sedna, I can use Ctrl-V as usual.
When I set the "IgnoreGLExtensions ["GL_Arb_Vertex_Programs"]" in the celestia.cfg file, I'm able to use Ctrl-V but without the latest FX features.

AMD Athlon 1.8GHZ, 512Mb ram, FX5200 video 128Mb, Driverversion 53.03

HB,

You need to update the OpenGL drivers: 53.03 is obsolete already.
The current version is 56.72

To add to this ... On my ATI 9700, the vertex_program path no longer appears. All I get are Basic and Multitexture.

On Selden's suggestion I download and Install the latest OpenGL drivers version 56.72. Unfortunatly the problem is still the same.

Hi, Don

I am too using ATI9700, I have never managed to get the vertex_program path on any occasion to appear on my XP. I have been assuming it is caused by ATI card not the Celestia. When I read your message, I now doubt my assumption? Maybe ATI9700 is innocent?

Joe

HB,

I'm using an FX5200 (by Asus) on my computer at work. I haven't had Celestia crash for a very long time, looking at Earth or elsewhere. Can you supply a Cel:// URL of the viewpoint where Celestia crashes?

System specs:
512MB 2.4MHz P4, WinXP Pro SP1
128MB Nvidia FX5200, drivers v56.72
Celestia built from CVS on April 21 (not by me)

Joe,

The specific loss of the vertex program that Don mentions is a bug that's seen if you build Celestia from scratch using source code download on April 21 (and maybe later).

The vertex shader rendering path is missing when Celestia is run on my system at work (with an FX5200) but present on my home system, which has a Ti4200, so I suspect it's the result of an accidental typo introduced in a very recent code change.

I do still see all the Nvidia-specific rendering paths on the FX5200 system, though, including the new FX-only shadow rendering path.

For Selden:

The requested URL:

cel://Follow/Sol:Earth/2004-04-23T12:33 ... s=1.000000<d=0&rf=36759&lm=0

Another approach to crash Celestia:
I startup Celestia, I get a view of Earth as I've configured in start.cel.
I change the object to goto Gaspra and use Ctrl-V to toggle the rendering-path untill "NVidia Geforce FX" is displayed in the lower left corner. After that I change the object to goto Earth and as soon as it start rendering this planet, Celestia will crash. The same happen if I use Saturn instead of Earth.

HB,

Actually that request was for the convenience of Chris Laurel, who's the person who'd actually have to fix the code.

I do hereby confirm that
cel://Follow/Sol:Earth/2004-04-23T12:33:11.63176?x=SMGsOrRWRW+wDA&y=LEIZ0UirBA&z=Bgpaq7s2q80I&ow=0.706148&ox=-0.000000&oy=0.708064&oz=-0.000000&select=Sol:Earth&fov=34.999996&ts=1.000000<d=0&rf=36759&lm=0

causes the 21Apr build of Celestia to crash on my system at work when the FX rendering path is chosen.

It does not crash Celestia v1.3.2pre7.

Thanks Selden for your support,

I 'll wait for a new update for these files.

Hi Joe,

Joe wrote:I am too using ATI9700, I have never managed to get the vertex_program path on any occasion to appear on my XP.

Have you kept your system device drivers (Microsoft) updated via the Microsoft Update web site? A while back, there was an ATI-specific driver release.

I also stay fairly current with the ATI Catalyst drivers from the ATI web site. Each new release offer more OpenGL support, and usually fixes some prior bugs.

For all graphics cards, keeping your drivers current is very important for running Celestia.

don wrote:To add to this ... On my ATI 9700, the vertex_program path no longer appears. All I get are Basic and Multitexture.

Strange . . . This can happen when I screw up and don't check in all the latest shaders, but everything looks OK. Can you try running Celestia from the command line and redirect output to a file:

celestia > log.txt

...then post the contents of the log here. If there are any problems loading the shaders, they'll be reported in the log.

--Chris

Here you go Chris...

Don,

Did you check to make sure that you have the most recent shaders?

Several shader programs, including texphong_arb.vp, were updated on March 23rd, which is after pre7 was released.

I had a problem similar to yours which was fixed by downloading the newest shaders.

Added slightly later:

HB and Chris,

To be specific, downloading the shaders of 23Mar eliminated the crash I previously confirmed for HB above.

Good catch Selden! That was it. Thank you!

Good evening to all of you,

Unfortunatly the latest shaderprograms doesn't fix the problem for me. As confirmed by Selden the build of 21 of April will crash Celestia.

For bughunting I will add a log.txt too:

Error getting joystick caps.
nStars: 112522
Initializing ARB vertex programs . . .
Loading ARB vertex program: shaders/diffuse_arb.vp
Loading ARB vertex program: shaders/specular_arb.vp
Loading ARB vertex program: shaders/haze_arb.vp
Loading ARB vertex program: shaders/bumpdiffuse_arb.vp
Loading ARB vertex program: shaders/bumphaze_arb.vp
Loading ARB vertex program: shaders/shadowtex_arb.vp
Loading ARB vertex program: shaders/diffuse_texoff_arb.vp
Loading ARB vertex program: shaders/rings_arb.vp
Loading ARB vertex program: shaders/ringshadow_arb.vp
Loading ARB vertex program: shaders/night_arb.vp
Loading ARB vertex program: shaders/glossmap_arb.vp
Loading ARB vertex program: shaders/multishadow_arb.vp
Loading ARB vertex program: shaders/texphong_arb.vp
All ARB vertex programs loaded successfully.
Initializing NV fragment programs . . .
Loading NV fragment program: shaders/shadow_on_rings_nv.fp
Error loading NV fragment program: shaders/shadow_on_rings_nv.fp
render path: 5

Maybe it wil help in finding the problems.

Kind regards

Hans B.

BH,

It looks like either you're missing the shader file "shadow_on_rings_nv.fp" or it's damaged. Double check to make sure you've installed all of the _nv.fp shaders.

Here's what I get when I GoTo Saturn and type Ctrl-V:

Oh, how stupid of me.

Yes indeed Selden, this shader file wasn't there. Thank you very very much!!