celestia v1.2.5b2 bug: crashes under XP Pro

Report bugs, bug fixes and workarounds here.
Avatar
Topic author
selden
Developer
Posts: 10190
Joined: 04.09.2002
With us: 21 years 10 months
Location: NY, USA

celestia v1.2.5b2 bug: crashes under XP Pro

Post #1by selden » 04.09.2002, 03:45

Celestia v1.2.5 beta 2 (and beta 1) crashes almost immediately when run under Windows XP Pro. It creates the graphic window, but never draws anything.

Beta2 runs fine on the same system when running under Win98 2nd edition (except for the textures problems reported by others).
V1.2.4 runs fine on the same system under XP Pro and under W98 2e.

Exception Information:
Code: 0xc0000005 Flags: 0x0
Record: 0x0 Address: 0x0


CPU Hardware: Asus p2b-ds motherboard; dual 500MHz Pentium III; 256MB
Graphics hardware: 3dfx Voodoo5 5500 [dual processor, 32MB/proc]

Please let me know if you need any additional information.

Additional information added later:
Under XP I'm using the graphics drivers supplied in XP, since 3dfx and Nvidia never provided any for XP.
Under W98 I'm using drivers provided by 3dfx (v4.12.01.0636 dated 9-25-2000)
Last edited by selden on 04.09.2002, 10:44, edited 1 time in total.

ogg
Posts: 83
Joined: 15.07.2002
With us: 21 years 11 months
Location: Canberra, Australia
Contact:

Another startup problem, perhaps related, perhaps not

Post #2by ogg » 04.09.2002, 04:16

I use XP Pro too, when Celestia 125p2 starts I get a window hazed with diagonal lines, can't make anything out. When window is resized or maximised, everything is fine.

Celeron 1.1Gz, OpenGL info:
Vendor: Trident
Renderer: Blade XP/AGP
Version: 1.2.1
Max simultaneous textures: 2
Max texture size: 1024
Supported Extensions:
GL_ARB_multitexture
GL_EXT_abgr
GL_EXT_bgra
GL_EXT_compiled_vertex_array
GL_EXT_packed_pixels
GL_EXT_paletted_texture
GL_EXT_vertex_array
GL_WIN_swap_hint
___________

ogg
___________

D.Edwards
Posts: 136
Joined: 25.05.2002
With us: 22 years 1 month
Location: Oregon/USA

Post #3by D.Edwards » 04.09.2002, 05:00

I use XP and It just takes a while for it to load. But them I am using some very big textures.

Avatar
Topic author
selden
Developer
Posts: 10190
Joined: 04.09.2002
With us: 21 years 10 months
Location: NY, USA

Post #4by selden » 07.09.2002, 00:28

My problems with crashes and strange textures on the Earth model clearly were all due to different bugs in the Voodoo5 drivers available for the various versions of Windows :(

I just finished upgrading to an Nvidea GeForce Ti4200 128MB.
It only took me 2.5 hours. grump.

Celestia 1.2.5b2 no longer crashes under XP Pro.
The combined textures used on the supplied Earth model all seem to be working fine, too.
Selden

Darkmiss
Posts: 1059
Joined: 20.08.2002
With us: 21 years 10 months
Location: London, England

Post #5by Darkmiss » 07.09.2002, 05:38

I use XP Pro and Detonator 30.82 drivers
and don't have any crash or graphics problems, at all.

I did get a crash, when trying to run Celestia in full screen
and running Dtonator 40.41 drivers

So i just rolled back to 30.82
CPU- Intel Pentium Core 2 Quad ,2.40GHz
RAM- 2Gb 1066MHz DDR2
Motherboard- Gigabyte P35 DQ6
Video Card- Nvidia GeForce 8800 GTS + 640Mb
Hard Drives- 2 SATA Raptor 10000rpm 150GB
OS- Windows Vista Home Premium 32

Guest

Post #6by Guest » 07.09.2002, 09:44

Thanks for the warning!
I'm running D30 now and was thinking about trying D40.
I guess I'll wait until the final versions are available.

Avatar
Topic author
selden
Developer
Posts: 10190
Joined: 04.09.2002
With us: 21 years 10 months
Location: NY, USA

Post #7by selden » 07.09.2002, 09:47

(That was me responding. I guess I was a little too overzealous in the disk cleanup.)
Selden

steve.wray
Posts: 17
Joined: 26.06.2002
With us: 22 years

Post #8by steve.wray » 09.09.2002, 00:06

I had terrible problems with later detonator drivers in XP... by the sound of it these may have been fixed (it was a problem with opengl or something).

For those having XP problems, try running celestia in win98 compatibility mode (go to the properties of the celestia.exe file).

If it works in compatibility mode then its a display driver issue (AFAIK)
It'll be very slow tho... but at least it narrows the problem down.


Return to “Bugs”