Stealth update broke my map. Doesn't read custom textures from BSP anymore.

[Vig]

After doing nothing this works.

Test #4
VMT's and VTF's in tf2/materials/my_map/
Edited the VMT's "$basetexture" "my_map/mymat"

I was talking with a friend and it turns out that sometimes hammer will stop updating the material browser, unless you relaunch the SDK tools menu. So when I tested, I had the step up correct in test #4, but I should of closed everything down and launched it fresh instead of just closing hammer and relaunching it.

So loong story short. Everything works. Don't put your materials in tf2/materials, put them some place else like tf2/materials/my_map and link your VMT's correctly.

Unfortunately this means old maps with textures included in tf2/materials will forever be broken unless someone re-compiles them.

 

[temion]

Unfortunately this means old maps with textures included in tf2/materials will forever be broken unless someone re-compiles them.

Its sad... that we're stuck with this. :facepalm:


Sure using the root directory may not be good practice but it wasn't necessarily BAD.. was it?

 

[Terr]

Sure using the root directory may not be good practice but it wasn't necessarily BAD.. was it?

If this problem came up in my ticketing system at work I'd be filing it under "Bug".

 

[Terr]

Bump, due to being FIXED! .

Fixed materials compiled into a map not being loaded correctly if they're in the root materials folder.

 

[absurdistof]

Orange maps... >.>

Glad it's fixed though