- Jul 4, 2012
- 31
- 4
Hi all,
I've been loading custom textures into TF2 for ages, but only recently have I run across this problem:
The front texture sometimes gives way to other textures behind it, even though my textures are 100% opaque and not a tool texture or anything.
Even if I re-texture it with a TF2 official texture, the weird clipping occurs. Changing the camera angle can trick it back into stop the clipping, but at the same time it'll trick other textures into the clipping bug.
Here's a sample .vmt:
Some of the textures have an alpha channel (all white); some don't. Some of them have the "$translucent" 1 tag, some don't. All of them have 8-bit Aplha, but that shouldn't affect it. One of them has a normal map, but the other don't.
The clipping happens for all of these textures.
Any ideas on how to fix this? I've been mapping on and off for years (only more recently for TF2) and I've never seen this before.
Thanks in advance! :wow:
I've been loading custom textures into TF2 for ages, but only recently have I run across this problem:
The front texture sometimes gives way to other textures behind it, even though my textures are 100% opaque and not a tool texture or anything.
Even if I re-texture it with a TF2 official texture, the weird clipping occurs. Changing the camera angle can trick it back into stop the clipping, but at the same time it'll trick other textures into the clipping bug.
Here's a sample .vmt:
Code:
"LightmappedGeneric"
{
"$basetexture" "custom/woodlogbeam"
"$surfaceprop" "Wood_Solid"
"$translucent" 1
}
Some of the textures have an alpha channel (all white); some don't. Some of them have the "$translucent" 1 tag, some don't. All of them have 8-bit Aplha, but that shouldn't affect it. One of them has a normal map, but the other don't.
The clipping happens for all of these textures.
Any ideas on how to fix this? I've been mapping on and off for years (only more recently for TF2) and I've never seen this before.
Thanks in advance! :wow:
Last edited: