bad surface extents?

hey tis moi trampus, im makng a hl deathmatch map all compiles well till it loads up half life and and box appears saying "Bad Surface Extents 128/18224"

wat does this mean and how can it be fixed?

thanx

Taken straight from the mouth of God himself - that is to say, Zoner, whose improved compile tools you should be using:

This is typically caused by having extremely large scales on faces, (typically far above 10, usually 100+). Otherwise it almost always shows up on a 'check for problems' in Worldcraft as a 'texture axis perpendicular to face' error.

So - fix any "texture axis" errors. If that doesn't work, look for high texture scales and reduce them.

insert correct answer here

kewl....thanx a lot although i havent got ne testures stretched above about 2 ill look for any which are and reduce them.

You need to do "Check for Problems" (Alt+P) then and fix your "Texture Axis Perpendicular to Face" errors. Worldcraft automatically fixes them when you hit 'Fix'.
And get ZHLT 2.5.3 here (Merl's build): http://www.snarkpit.com/editing.php?page=files&game=HL&type=editors

my answer was correct, just not one you wanted to hear :heee:

the answer to this is indeed in the search, cause it was posted just last week for sure..

No it wasn't.

Leperous said:
No it wasn't.

feigns indignation

yes it was! .. taps foot

if people are going to bypass the search option, then i for one will bypass assisting them.

either way, i was right, changing the definition of "correct" wont alter that!

this is probably a frequently asked q but... which is better hammer or worldcraft?.... atm i am using hammer, should i change??? i used the check for problems and nothing came up.wierd

trampus said:
this is probably a frequently asked q but... which is better hammer or worldcraft?.... atm i am using hammer, should i change??? i used the check for problems and nothing came up.wierd

they are basically the same program, switching won't matter.

and thats because looking with the "check for errors" wont find this, its an issue you will have to locate yourself.

in most cases that i have seen, where it was created without the author aware he made one, it was on a face that had been clipped at a sharp angle and is now hidden behind another solid that he clipped it for..

search behind things you have clipped, a bad surface extent does NOT have to be visible inside the map.

thanx a lot that prolly is wats happened as there is quite a bit of clipped objects.

i think, this "correct" and "incorrect" thing either needs fixed, or gotten rid of totally.

we all know, that there are sometimes many possible solutions to any editing question, only a few of which may solve any one, but that does not mean a future question could not be solved with the "WRONG" answer from a preceding time..

questions that are solved, should be rewarded, but any other possible answer, whether its currently correct or not, should revert back to a green response, NOT be made to look wrong because it now has a red box around it..

my answer was 100% correct, it just was not the answer one wanted to hear, it really pisses me off if i am forced to accept it as incorrect when i know otherwise..

this issue has arisen before, with no adequate solution found, till one does, the "correct" and "incorrect" should be disabled.. it is helping no future mapping issue to have any correct answer marked as INCORRECT..

Though it does help future mapping issues to have an incorrect answer marked as incorrect.

Gollum said:
Though it does help future mapping issues to have an incorrect answer marked as incorrect.

true, but any incorrect answer will have our corresponding answers making it clear that its wrong..

i dunno the solution, or if there is one, but any correct answer marked as incorrect is not helping.

i think the best/only solution is to have all answers revert back to a green border that are ultimately unaccepted at the time..

The answer to your question lyes here

http://www.slackiller.com/tommy14/errors.htm#badsurface

What happened to me was I was doing a reverse ctf map and ran into the same prob and felt a teer start to shed over tearing the map apart peice by peice. So read the above link to kinda get an idea. What worked for me was I selected the entire map and the magic number was to set all the brushes to 4.00 poof the map compiled :o

After that youll have to manually resize sect of brushes and compile till you run into the prob, You could also try to cordon stuff off but isnt as effeceint.

it just feels like thats going about it backwards.....maybe its just me....i will check my notes....

Doc B... :dodgy: