Either my card doesn't support it, or ... o.O
Posted: Tue Feb 02, 2010 9:16 pm
Just found that UseMultiTexture = TRUE on a MX440 causes the whole world to become slighly translucent, noticiable only when you get close to surfaces, which ends up forcing the render to render everything that shouldn't be seen trough walls.
Happens in OpenGL. In D3D9 doesn't seem to happen, odd.
According to gpu-z and ued log the card does support gl_arb_multitexture.
Still testing what causes fog to be rendered "behind" water, like in the intro map, the fog when the camera flies under the bridge seems to "clip" behind the water. Also in some maps I see fire textures being rendered behind masked textures, like grates. Something with z-buffer I think.
Found that disabling multitexture causes fog to be rendered "behind" zone portals, however, enabling multitexture still makes no difference in fog being rendered "behind" fake backdrop surfaces.
D3D9 renders darker, like opengl with OneXblending enabled. But I don't use D3D9 because I see ugly color banding on the menu and because gamma seems to lock under D3D9.
Happens in OpenGL. In D3D9 doesn't seem to happen, odd.
According to gpu-z and ued log the card does support gl_arb_multitexture.Still testing what causes fog to be rendered "behind" water, like in the intro map, the fog when the camera flies under the bridge seems to "clip" behind the water. Also in some maps I see fire textures being rendered behind masked textures, like grates. Something with z-buffer I think.
Found that disabling multitexture causes fog to be rendered "behind" zone portals, however, enabling multitexture still makes no difference in fog being rendered "behind" fake backdrop surfaces.D3D9 renders darker, like opengl with OneXblending enabled. But I don't use D3D9 because I see ugly color banding on the menu and because gamma seems to lock under D3D9.