Quake3Arena and WinXP problem

[MrBond]

Ever since I upgraded to WinXP, q3a has been giving me fits. No matter what video card drivers I run, it starts, runs the loader thingy (the window that pops up initially), goes to a light blue screen, then crashes. Then its like the gamma setting on Windows is bumped WAY up, which requires a reboot to fix it. Anyone else encounter this with a Geforce2 GTS and XP? Did a certain driver version help? TIA

 

[fastcobra]

Wierd,
I am using latest nvidia detonators. (Whatever is latest on their site right now), no problems.
WinXP
GF2
Runs like a champ

 

[Ronin]

Any chance you have the VIA chipset? If so, go to www.viahardware.com and download the beta fix for Nvidia/Via combos.

 

[odd]

My problem is similar.
When I goto play quake 3 and games based of the quake3 engine, the game resets my default color settings (desktop) and uses them in game. So it's basically all dark. Then when i exit the game the settings are the same. Even if i change it back, in any game it resets the color settings. And I must restart in order to fix it.

 

[MrBond]

<< Any chance you have the VIA chipset? If so, go to www.viahardware.com and download the beta fix for Nvidia/Via combos. >>

Yep, I'm running a via chipset, hopefully thats it. I'd think all quake3 based games would have the same problem though, but RtCW runs fine on my system.

It's quite possible I may need to reinstall q3a. I have a seperate partition for my OS, and I've formatted and reinstalled Windows several times since the initial install of q3a. Its worked in the past, but i've probably reinstalled windows 4-6 times since I bought q3a and installed it initially. My CD's aren't here though, so I'll have to wait until this weekened to try.

Edit: I can't seem to find the nvidia/via fix on viahardware.com, can someone link me cause I must be blind

 

[Workin']

Q3 works fine on my rig, VIA KT266A, GF3, XP Pro.

I'm running the VIA drivers that shipped with XP and 22.50 nvidia drivers. I didn't install ANY patches or updated VIA drivers. Works flawlessly, not a single crash or glitch. Other nvidia drivers worked fine too, except the 23.xx series ignore your vsysnc settings for Direct3D, meaning framerates are capped at your vertical sync frequency. Switching back to 22.50's fixed that.

 

[MadAd]

thats what u get when u buy an OS thats had half the gaming guts ripped out of it and forces u to play native OGL and glide games (like Q3 (and mods) HL (and mods) Wolfiensien, UT etc etc) in d3d or thru glide>d3d wrappers.

hail the new gods- M$ & Nvidia - there to ensure even your software needs replacing in 1-2 years (like your hardware) wether you like it or not

Infact u might as well just sign over a % of your paycheque to them annually

 

[sabrownfl]

I have the exact same problem. I can get into the game, play about 10 mins, and then I get an error message and the game crashes. My desktop then is jacked like the gamma is set off the chart.

Using latest Nvidia drivers and all patches, system settings bone stock right now trying to isolate the problem...

sabrownfl

 

[jfunk]

Possibly related, possibly not about color settings.

I don't have any Q3 probs, but whem my GF plays SIMS, the XP color palette is all screwed after exit.

I was rebooting to fix it for a while, but I found just openin my color tab in advanced display props and hitting OK reset it.

Still haven't found any other fix...

j

 

[BFG10K]

Any chance you have the VIA chipset? If so, go to www.viahardware.com and download the beta fix for Nvidia/Via combos.

All you need is the latest 4.37 drivers and make sure you have the latest BIOS for your motherboard.

I've never had any problems with Quake3 on Windows XP. It runs great.

 

[digim0rtal]

Format and start over.

 

[Compellor]

<< All you need is the latest 4.37 drivers and make sure you have the latest BIOS for your motherboard. >>



I wouldn't install these unless you're getting the "NVIDIA Infinite Loop error" or you'll take a slight performance hit. Stick with the default 4in1's that come with XP unless you're getting this error.