happen only in ETQW[other GL-based games not affected.
happen only on particular angle of view[about 20 degrees << from spawn and ±15 degrees from horison on verical]
any ideas ?
persist on drivers from 10.4 to 11.3 
or its time to move to NVidia hardware(bye-bye ATi Image quality, hello flawless drivers)?
Well, ATI(AMD) and this game don’t get along so well. It might be some specific cvars that triggered weirdness in etqw so you could try to fiddle with those. I think one was normals compression.
And getting nvidia isn’t a bad idea. Heck, i even prefer to use 9300m GS over hd4850 for etqw renders even tho it takes years, it actually renders it correctly.
ATI image quality is a myth. They are known to tweak lod biases so screenshots look good, then in dynamics you get flicker and ****.
thats depends.
their AF[with or without tri-linear filtering] quality was better. same was about [default]DXT compression quality.
but relying on z-space compression[instead of imroving rendering back-ends to be able to handle fill-rate]cause HUGE/Horrific artifacts in-game, sure.
but… when you talk about 2D quality, ie picture itself, esp on notorious CRT screens… ATi is still WAY ahead.
sure, NVidia improve IQ considerably in Fermi chips and bring DAC’s back into chips, but improvements still leave ATi beneficiary for IQ-relying guys, such as painters, photographers and etc.
[QUOTE=murka;284771]Well, ATI(AMD) and this game don’t get along so well. It might be some specific cvars that triggered weirdness in etqw so you could try to fiddle with those. I think one was normals compression.
And getting nvidia isn’t a bad idea. Heck, i even prefer to use 9300m GS over hd4850 for etqw renders even tho it takes years, it actually renders it correctly.[/QUOTE]
Nvidia fan boys BEGONE, I had a similar error with ETQW on an Nvidia card, the textures would all look exactly as the attached screenshot. This would happen at random times and only a full reboot would restore things to normal. Other applications were unaffected.
The fix in my case… was to buy an ATI card and I have NEVER had the issue again.
stick that in your heat pipe and smoke it.
MOOKA!
what is interesting, thats its happen after last [hidden]ETQW updates, dunno what updated[PB or ETQW itself].
“on DirectX” even iNtel GMA is “flawless”.
point is “how flawless?” answer.
and thats depend other factors too. for example, AMD leading in adopting OpenGL 4.x and moving toward OpenCL, while ATi got stricter OpenGL compliance on each [implementation]level, and done it with HW support, not as “software wrapper” as AMD [initially]does, despite [even better]HWsupport[for such feats].
point is - Nobody was perfect and both vendors complimentary, helping each other, advancing with or against own wills.
I can repro those artifacts with r_useIndexBuffers “0” did you changed it? Because the default is “1”
Also read somewhere that this setting is for ATI cards, I’m not sure what it does.
But you can try if it solve your problem: r_useFBODestinationBuffer “1”
GL
[QUOTE=Breo;286820]I can repro those artifacts with r_useIndexBuffers “0” did you changed it? Because the default is “1”
Also read somewhere that this setting is for ATI cards, I’m not sure what it does.
But you can try if it solve your problem: r_useFBODestinationBuffer “1”
GL[/QUOTE]
its WORKS.
r_useIndexBuffers in “1” was eliminated issue/artefact.
which is exactly what i trying to get.
thanks 4 highlight/help.
dunno WHY this cvar altered[never played with cvars “in general” or using foreign configs, tweaking only basic stuff, like visibility distance, mip-mapping and texture filtering] and how.
more interesting thats happen even with clean install of ETQW from disc[and retail patch rolled atop of it, after].
probably leaked from a or profile preset 
but HOW/WHY its altered initially ???!