Snarkpit Forum Index » Source engine editing » Hammer lost a single texture, while Half-Life still has it.
Hammer lost a single texture, while Half-Life still has it.
1
Post Reply
Quote
 Re: Hammer lost a single texture, while Half-Life still has it.
Posted by Joe-Bob on Sun Feb 13th at 2:29pm 2005

The map I'm working on uses the water texture water_wasteland002a. That is, by the way, the texture of the ocean in the single player coast levels. Just recently though, Hammer lost all 4 wasteland water textures and replaced it with its wonderful pink checkerboard of d00m. Everything still looks right in the single-player game and in a deathmatch map I've seen that uses it. However, since Hammer can't find the texture, RAD assumes it's opaque. Unless I somehow weave in a black hole colliding with the ocean, the effect I get isn't going to work for my map.

I've tracked down the problem a bit by looking up the VMTs in the Source Materials GCF. I figured out that the texture the tools are trying to use is named "nature/water002a". Befittingly, my compile log states that " "materials/nature/water002a.vtf": cached version doesn't exist". After searching the materials GCF, I found that it wasn't kidding around. It just plain isn't there!

Refreshing the SDK content doesn't work, checking the GCF with Steam reported that they were all good, and I still can't find that bloody texture. Does anyone have an idea exactly what the hell is going on?

Hammer View: (Note, I get the same thing when I load the SDK coast level)


In-game, you can see that the water works, but RAD has treated the water as opaque:





Quote
 Re: Hammer lost a single texture, while Half-Life still has it.
Posted by StickFigs on Sun Feb 13th at 7:34pm 2005

Hey it's you!



Quote
 Re: Hammer lost a single texture, while Half-Life still has it.
Posted by Joe-Bob on Sun Feb 13th at 7:43pm 2005

And it's you!
But anyway, I'm reinstalling Half-Life. Maybe that'll do the trick.




Quote
 Re: Hammer lost a single texture, while Half-Life still has it.
Posted by Rof on Sun Feb 13th at 8:27pm 2005

Looking at the .vmt for that material, it has this:

// "$basetexture" "nature/water002a" // The main texture for the water surface.
"%tooltexture" "nature/water002a" // This is the texture that shows up in the Hammer browser.

The $basetexture line is commented out, which is kind of strange. The tooltexture (which is what is shown in Hammer) isn't commented out, but refers to the same non-existant .vtf file, which is probably why it shows as pink checkerboards in Hammer. If you decompile de_aztec, you'll see the same problem with missing tooltextures.

Not really sure what the compiler will make of a missing texture like that. It obviously does something, because you can see a water texture, but I'm not sure where it's getting it from. Theres this bit at the top:

"Water_DX60"
{
"$fallbackmaterial" "nature/water_dx70_opaq"
}

I wonder if since it can't find the texture it falls back to this one, even if you're in a higher DX mode.
[addsig]



Quote
 Re: Hammer lost a single texture, while Half-Life still has it.
Posted by omegaslayer on Sun Feb 13th at 9:53pm 2005

I have this same problem, it doesnt show up in hammer, but it shows up in-game. So its just not you. [addsig]



Quote
 Re: Hammer lost a single texture, while Half-Life still has it.
Posted by Leperous on Sun Feb 13th at 9:57pm 2005

Strange that it looks like that in Hammer, looks to me like you've got an invalid sky selected or something :/






1
Post Reply