Quake changing colors mid-game

[Punk_FAS]

Since I've started playing quake again, in the past week or so, sometimes when I'm playing, my colors will all of a sudden turn from a normal color to a purplish/pinkish hue.  I've attached a before/after screenshot to try to show the differences.  Never seen this before, was just curious if anybody else had any clue what was going on.

When I do a vid_restart, it fixes it temporarily, sometimes for only a few seconds, sometimes for many minutes to an entire gaming session.

Any input would be much appreciated 

 

Edit:  Made the pics jpegs so they weren't so huge.  As you can see... my crosshair all but disappears when the colors have a change.  My bright-skinned player models become very hard to see as well.  So for those 2 reasons alone, this annoys me =P

[Punk_FAS]

I did notice that it just seems to be the objects, and not the environment, physical parts of the map, etc.  Hmmm, perhaps that's a clue...

[Punk_FAS]

Ok, loaded up R1Q2 (what I always use), didn't even load a map or anything... Here are a couple screenshots from the console.  As you can see the problem even starts there.

[PANTONE 7717C]

sudden artifacts and colors of the rainbow are normally an indication that the vid card is going south but if it only happens with the entitymodel skins it could be something else.

edit; oh I see it also happens in the console now

suggestions;
-try to find out if this only occurs in Q2 (opengl games)
-probably the card's drivers need a refreshing(?)
-take out and reinstall the card:/
-if you're also using r1gl, set it to standard opengl as a test (vid_ref gl > vid_restart)
-unlikely but maybe something has happened to this file: colormap.pcx

[ReCycled]

The brightness of the objects are only controlled thru gl_modulate. Maybe the setting is too high. The rest of your display seems to stay put although the "intensity" color level looks a bit hyped. If you have time to tweak R1Q2, you can get a pretty nice balanced display. It may be a conflict between r1gl config settings and the normal Quake config.cfg settings for your video display. I had that when I first started using R1Q2. It would actually start to produce flashes in game and color changes.
What happens if you just start stock Quake 2 - 3.20?

[R1CH]

Also run in 32 bit color depth, 16 bit is getting to the point where it is no longer hardware accelerated on some cards.

[ReCycled]

Also run in 32 bit color depth, 16 bit is getting to the point where it is no longer hardware accelerated on some cards.

Good point. I now remember changing from 16 bit to 32 bit as well.

[|iR|Focalor]

As one guy mentioned, perhaps its the colormap.pcx in your added pak file. Perhaps there's more than one colormap there and a config within the pak file is switching to another colormap. Try removing the added pak file from the folder, then play for a while and see if it still occurs.

[X'tyfe]

thats pretty odd, i was also thinking your video card was about to go tits up
but looked again and saw it was just a few things

probably some sorta glitch thats all i can say really

[[BTF] Reflex]

at any rate..

Good to see you playing again.  Hope you get this sorted out

[[BTF]DeathStalker]

Also run in 32 bit color depth, 16 bit is getting to the point where it is no longer hardware accelerated on some cards.

Quadz, remember how i said my system did better using 32bit graphics?

[Punk_FAS]

Still having this problem.  I don't honestly know which pak files are original from Q2 and which I've added.

I have these in my /baseq2/ directory - PAK0.pak, pak1.pak, pak8.pak, pak9.pak

I have pakscape.exe for viewing .pak files.  Where would I find this colormap.pcx file within the pak files, and what specifically should I do about them if there are more than one?

Thanks a ton, this sucks, I haven't played lately because it's frustrating/annoying to keep dealing with this

[Whirlingdervish]

if you are looking in quake2/baseq2/ then the pak1.pak and pak0.pak are the stock ones.

the colormap.pcx file should reside in baseq2/pics or in the "pics" folder of your pak0.pak

the one in your pak0.pak is the stock one so save a copy somewhere before you fiddle with it.


you might check your tourney and other main mod folders for paks as well.
they'll load from there, depending on the mod and you might have one hidden somewhere that has a higher number and a differnt colormap.pcx in it, in which case its loading over your normal one.


another useful tool for pak opening/making/handling is wally.
(it'll also open any of those .pcx files if you wanna look at them)

http://dervish.tastyspleen.net/files/wally_155b.exe

[PANTONE 7717C]

If you don't find anything in your custom paks, check the bitdepth if you haven't done so already:

Also run in 32 bit color depth, 16 bit is getting to the point where it is no longer hardware accelerated on some cards.

... in the screenshot of your console it says you're using a desktop display depth of 16, have you tried changing it to 32 bits? You can also set it from within quake2 -> gl_bitdepth 32 /vid_restart (default =0)

If all this doesn't help, put another (older) copy of the game on the computer and delete the config.cfg. Then load up that Q2 and see what happens...

[peewee_RotA]

Reinstall. Could be pallette issues or problems with your standard .pak file even.

I've seen all sorts of rcrazy things caused by quake2 files corrupting from age.