F5F Stay Refreshed Software PC Gaming Half-Life 1 : Weird OPENGL texture glitch with Windows 10

Half-Life 1 : Weird OPENGL texture glitch with Windows 10

Half-Life 1 : Weird OPENGL texture glitch with Windows 10

A
aidanm6
Junior Member
26
04-16-2016, 03:03 AM
#1
Half-Life (OpenGL) – Double Vision on Windows 10 – Seeking Confirmation

I’m experiencing a strange visual anomaly with Half-Life running through OpenGL on my Windows 10 machines. It appears as a form of double vision, similar to stereoscopic 3D, primarily affecting floor and lower wall textures across all maps. This occurs with all Gold Source titles, including Counter-Strike 1.6 and the Half-Life expansions. I’ve ensured my Nvidia drivers are up-to-date and that stereoscopic 3D is disabled in the control panel. The issue is consistently present on both a laptop and desktop running Windows 10. Specifically, observing the elevator floor at a 30-degree angle or looking at textures like those in de_dust2 reveals this double vision effect. I’ve been unable to play titles that trigger this due to migraines caused by the visual distortion. Has anyone else encountered this issue on Windows 10?
A
aidanm6
04-16-2016, 03:03 AM #1

Half-Life (OpenGL) – Double Vision on Windows 10 – Seeking Confirmation

I’m experiencing a strange visual anomaly with Half-Life running through OpenGL on my Windows 10 machines. It appears as a form of double vision, similar to stereoscopic 3D, primarily affecting floor and lower wall textures across all maps. This occurs with all Gold Source titles, including Counter-Strike 1.6 and the Half-Life expansions. I’ve ensured my Nvidia drivers are up-to-date and that stereoscopic 3D is disabled in the control panel. The issue is consistently present on both a laptop and desktop running Windows 10. Specifically, observing the elevator floor at a 30-degree angle or looking at textures like those in de_dust2 reveals this double vision effect. I’ve been unable to play titles that trigger this due to migraines caused by the visual distortion. Has anyone else encountered this issue on Windows 10?

P
ProMegaYT
Junior Member
5
04-21-2016, 06:01 PM
#2
Shift from OpenGL to D3D Renderer in video settings of the games. Should solve your problem.
P
ProMegaYT
04-21-2016, 06:01 PM #2

Shift from OpenGL to D3D Renderer in video settings of the games. Should solve your problem.

C
coolaoliver
Junior Member
26
04-25-2016, 06:02 AM
#3
Well, Valve removed the D3D renderer back in 2013....
I guess it has something to do with OPENGL activating stereoscopic 3D by itself..
C
coolaoliver
04-25-2016, 06:02 AM #3

Well, Valve removed the D3D renderer back in 2013....
I guess it has something to do with OPENGL activating stereoscopic 3D by itself..

F
feryara
Member
105
04-25-2016, 06:21 AM
#4
TeamRED :
Shift from OpenGL to D3D Renderer in video settings of the games. Should solve your problem.
Well, Valve removed the D3D renderer completely from HL1 since 2013, we can no longer choose it.
It has something to do with OpenGL and Windows 10, since this bug wasn't there in Win8 and Win7....
F
feryara
04-25-2016, 06:21 AM #4

TeamRED :
Shift from OpenGL to D3D Renderer in video settings of the games. Should solve your problem.
Well, Valve removed the D3D renderer completely from HL1 since 2013, we can no longer choose it.
It has something to do with OpenGL and Windows 10, since this bug wasn't there in Win8 and Win7....

A
ADIR_4444
Senior Member
417
04-25-2016, 07:58 AM
#5
This response delves into the technicalities of graphics rendering, particularly relating to antialiasing and texture quality. It highlights a common issue – the “double vision” artifact – stemming from incorrectly configured transparency settings in older games like CS:1.6. The core explanation revolves around the interaction between antialiasing (specifically transparency supersampling) and how the GPU handles alpha blending for transparent textures.

The response correctly identifies that this issue is often linked to misconfigured antialiasing options, specifically those involving transparency supersampling (TS). TS attempts to simulate the rendering of transparent objects with higher precision, but when improperly configured alongside certain antialiasing techniques, it can cause visual distortions like a double-vision effect.

The text then provides a practical solution – disabling or adjusting transparency settings within the graphics control panel (often associated with Nvidia’s drivers) to avoid this artifact. It recommends switching from "Transparency Supersampling" to "Multisample" mode and explicitly states that “Antialiasing - Transparency” must be set to "Off".

Finally, it includes a relevant link to a forum discussion on the same topic, further supporting the explanation and demonstrating the prevalence of this issue across different games and graphics card configurations.
A
ADIR_4444
04-25-2016, 07:58 AM #5

This response delves into the technicalities of graphics rendering, particularly relating to antialiasing and texture quality. It highlights a common issue – the “double vision” artifact – stemming from incorrectly configured transparency settings in older games like CS:1.6. The core explanation revolves around the interaction between antialiasing (specifically transparency supersampling) and how the GPU handles alpha blending for transparent textures.

The response correctly identifies that this issue is often linked to misconfigured antialiasing options, specifically those involving transparency supersampling (TS). TS attempts to simulate the rendering of transparent objects with higher precision, but when improperly configured alongside certain antialiasing techniques, it can cause visual distortions like a double-vision effect.

The text then provides a practical solution – disabling or adjusting transparency settings within the graphics control panel (often associated with Nvidia’s drivers) to avoid this artifact. It recommends switching from "Transparency Supersampling" to "Multisample" mode and explicitly states that “Antialiasing - Transparency” must be set to "Off".

Finally, it includes a relevant link to a forum discussion on the same topic, further supporting the explanation and demonstrating the prevalence of this issue across different games and graphics card configurations.