Shearing in Q3A

[Blueline]

I just recently swapped my TNT2 for a G400Max and I noticed that when I play Quake 3 with my G400 the image seems to shear when I move the mouse too quickly. The objects on the bottom half of the screen seem to move across a tiny bit faster than the top. This is really irritating, is there any way to fix this?

Any input is appreciated,
Blueline
------------
PIII500
256 Meg PC133 RAM
Millenium G400 Max 32
Powerdesk 5.41.008
TurboGl 5.41
SB Live

[absalom]

Sounds like your describing the visual "tearing" associated with verticle sync being disabled. By default, the g400 opengl driver has vsync disabled. You have to manually enable it for it to work properly. Just goto q3's console and enter these:

r_finish 1
r_swapinterval 1

It's been my experience that the q3 menu option for vsync is useless. It seems you have to manually enter it for it to work. Enabling it also makes the mouse responsiveness alot crisper, imo.

[This message has been edited by absalom (edited 16 January 2000).]

[Blueline]

Thanks absalom
That cleared it right up.
Much Apreciated

[Edguy]

Hmmm, that doesn't seem to make any difference for me tho :/

never had Vsync on Opengl based games... not that i find it very annoying, but i'd like to fix it...

Direct3d games all work with Vsync...

Any suggestions?

[absalom]

Right after the g400 hit the market, the very first few releases of PD 5.x (pre-turbogl) did not support vsync in it's opengl ICD. If your using an old ICD then those settings will not work. But, in any case that's the universal way of enabling vsync in quake3... so it should work regardless of the video card.

[Blueline]

Hey Guys, just some clarifications

I think you may be looking at two different problems. The shearing I was talking about was brutally obvious, and made the game almost unplayable. I found that I had inadvertantly messed with the Quake set-up to cause it and I restored the original cfg from the CD and verified the cvars that absalom pointed out.

There is a second similar problem that I found with the TurboGL that I found aswell where the textures/geometry (as opposed to the whole image) seem to shift and become discontinuous as the player moves from side to side or turns. This is especially noticeable in maps with tall vertical pillars etc. There have been several posts about this aswell, and I am also trying to fix this problem with much less success.

Perhaps that is why Edguy saw no difference?

Anyhow, if anybody can fix that texture/geometry shifting problem please let me know.

[Edguy]

The only problem i've been seeing is that Vsync is disabled with both the ICD and the turbo GL, that's what's causing the phenomenon of the "shearing" or what ever they called it...

i got it working with my old G200 when the ICD came out for it, but somehow, it stopped working... now no OpenGL based games have Vsync enabled, and alla Direct 3d games do...

just my question is there any way to Enable it on the ICD and the TurboGL ?

[Edguy]

Hmmm, i thought when using the Turbo GL, the ICD didn't matter? im using Pd 5.30 with whatever ICD came with it, would it be any different if i installed the 5.41 and the GenericCPU Turbo GL ?

[absalom]

I don't think there is anyway "simply" to make the ICD (or turbogl) run opengl apps with vsync on as a default. Vsync (in all id software's engines) is controlled by the cvars. The recent ICD and turbogl supports vsync. In fact, I think turbogl has always had vsync supported. So if you want vsync to work in half-life, sin, quake, quake2, quake3, heretic2, etc. you control it through the cvars.

PD 5.30's ICD does support vsync as well as turbogl. I don't know why your seeing shearing, unless it's something else. Your autoexec.cfg having r_swapinterval 0 would override manually setting it everytime q3 loads. Check your q3config or an autoexec.cfg for something like that.

[zef]

OK. I've got the same problem that Blueline has. I'm using PD5.41 w TurboGL 1.00.002. Tearing is SUXXX!

Absalom! Are you sure that vsync is really supported under G400's OGL drivers (any version)? I'm afraid it isn't...

Hey Guys at Matrox! Please fix this problem!

[skeoch]

Sorry if Im off track, but has anyone tried the VSNYC reg http://www.murc.ws/Utils/PD5RegHacks.zip

It worked for me.




------------------
I have FLAK CANNON, U have FLAK!

[absalom]

It is my understanding that the g400 reghacks only work for toggling vsync under the direct3d api. Again, I'm stressing that in a game like quake3, you control vsync through it's cvars.

[Adi]

Hey guys...

I have the same problem with Q3. Everytime I turn around the game runs very "slowly". And this sucks. I guess it´s the old V-sync problem.... and please don´t tell me that a registry hack is the only solution for this problem.

Adi