Prob w/ Custom Animating Textures Created 18 years ago2006-03-21 23:51:43 UTC by TawnosPrime

I created some custom animating textures to make the Matrix code on some walls and such but they appear as pink and black tiles in game. I've posted it as a problem map for ppl to have a look at. Hers's the link:

http://twhl.co.za/mapvault_map.php?id=3788

Added info (and bump ;): When I compiled the map, I inculded the wad so I wouldn't need to transfer it to cstrike. I don't know if this is causing my problem or not. I included to wad in the zip so ppl can look at the file.

The pink and black pattern represents a missing texture. You've done something silly.

Wouldn't suprise me... -_-;

can be casued by spaces or invalid characters in the Texture's name (although i think wally automatically prevents evils)

and also by the .wad being in the wrong folder.

it should either be in

1) half-life/valve (HL1)
2) counter-strike/cstrike (CS)
3) Day Of Defeat/DoD (DoD)

etc etc etc

Ok...I've got more additional info...

1 - I used -wadinclude TP_Matrix on the csg so I wouldn't haveto worry much about the wad

2 - I'm unsure if this is important: I custom named the textures myself and used a mix of upper and lower case letters, (like in my name), to label the large and small versions of the Matrix code

get rid of all capital letters including the capital letters in the .wad name

I've at least tried making the names of each texture small while leaving the file name the same (not my first custom wad) and that didn't work.

Apon testing the map, my console logged the line 'WARNING: failed to locate sequence file matrix'...is this the culpret...shit I g2g for now. I'll check back in l8r.

Do the textures show up in hammer but not in-game?

Yes, I get them in the 3d view in hammer but not in game

try not wadincluding... put the .wad in the correct folder.. its possible you arent wadincluding properly.

Check your compile log for a bit like this

--Wadincluded Textures--
zhlt.wad
custom.wad

If your wad doesnt show up in that list, its not wadincluded properly.

When I had that problem, it was because i was trying to -wadinclude in normal compile mode, not in expert.

(p.s, i sooo deserve a forum award :P)

Although I'm not sure I approve of hunter's 'shameless' plug for an award, his suggestions turned something up, indirectly though.

To start, it was including my custom wad and an attempt to use the wad w/in cstrike and not include it in the compile failed.

But, through the wad confirmation, I discovered this:

Using Wadfile: c:program filesvalve hammer editorwadshalflife.wad

• Contains 0 used textures, 0.00 percent of map (3116 textures in wad)

Using Wadfile: c:program filesvalve hammer editorwadstp_primuslab.wad

• Contains 0 used textures, 0.00 percent of map (28 textures in wad)

Warning: ::FindTexture() texture +0BIGMATRIX not found!
Warning: ::FindTexture() texture +0SMALLMATRIX not found!
Warning: ::LoadLump() texture +0BIGMATRIX not found!
Warning: ::LoadLump() texture +0SMALLMATRIX not found!
Texture usage is at 0.00 mb (of 4.00 mb MAX)
1.16 seconds elapsed

See, I have a couple of custom wad files in my Hammer folder, all w/ the prefix TP_, (as will my maps, if i ever actually finish one ). Anyway, Hammer is only supposed to use the halflife and TP_Matrix wads that I've told it to, but it seems to have replaced the Matrix w/ another one, PrimusLab.

Do any of u guys know why and how I can fis this?

Warning: ::FindTexture() texture +0BIGMATRIX not found!
Warning: ::FindTexture() texture +0SMALLMATRIX not...

Do you use HLFix?

Not updating your wad.txt file--needed for HLFix--is one way I know to produce this error.

yes i use it but I don't even know wnything about the wad side of it...i don't even have a wad.txt.

Try adding a "wad.txt" file to your valve hammer editormaps folder.

My wad.txt file:

s:half-lifevalvehalflife.wad
s:half-lifevalvexeno.wad
s:half-lifevalvedecals.wad
c:program filesvalve hammer editortextureszhlt.wad
c:program filesvalve hammer editortexturesdm_lars.wad

If I remove say the dm_lars.wad location, I'll get the same error you're getting. I think this is probably your problem.

I added my wads to that, however I'm not sure if it's the issue or not. When I tried to run the map after compiling it, I got this error:

ED_ParseEntity: closing brace without data

I have no clue what it means, so once again, I'm turning to the ever helpful TWHL community to aid in solving one of my many problems (as seem to always be present in my life ).

There's an } somewhere that's closing an empty brace set? I don't know what would cause this.

I added my wads to that, however I'm not sure if it's the issue or not.

Your not sure, I see... well are you still getting the "..FindTexture()..." error !? I guess that would be one way to be sure if that part of the problem was fixed or not

Make sure your including the wadinclude switch under the CSG paramater. You can also try specifying the path if the "lives" somewhere other than your valve folder... If the path name has spaces, include the path in quotes.

For kicks you might try a brand new map from scratch--I'm reaching now :

If none of this works, try checking the chair-keyboard interface

OK...the final post as I've figured out my problem for the most part.

Yes, the FindTexture() and LoadLump() errors were fixed by adding the wads to wad.txt, and I was including the wad correctly as stated w/in the Custom Textures tutorial. Testing a series of brand new maps is how i discovered my problem.

The ED_ParseEntity error was caused by...having over 8 wads in the txt (fyi I've got 21 and could grow still). After trimming the file down to only what I needed at the time, it worked properly. Let this be a lesson to other n00bs...DON'T USE TOO MANY WADS!

(good thing I was able to figure it out b4 the chair(or char?)-keyboard interface...no idea what i would have had to do there )

Correction...this is the final post for the thread.

I forgot to thank everyone for the help they gave to me in solving my problem, and I look forward to stumpping u w/ my future problems which I'm sure will be just as tricky and completly unintentional, I just have REALLY bad luck.