bad surface extents- game console error

Right, first I'd like to thank WC for helping, although I see his attempt at helping my noobish self was locked.

Anyways, as you may well know by now, I've had a "bad surface extents" error - specifically
"Bad Surface Extents: 32/704"
This DOESN'T happen in the radiosity process, but actually happens when the map is loaded by Counter Strike. Can I also say that I got exactly the same answers from the internet as I did from the forum and tutorial search, which were "there must be an over-stretched texture or brush", and all of my searches for this have been in vain. I only want to know one thing:

• Does anybody here know if the two given numbers are helpful, and if so how can I use them to help me find the erroneous brushes?

Thankyou for your time.

i am not sure, possibly grid coordinates, or brush numbers.. but if you cannot see it, it will definitely make it hard to locate.

in my experience, this error is cause by clipping off a side of some object, it stretches the unseen side by several times..

try to remember, when it occurred (the message) and then try to recall if you had clipped something recently.. a set of steps, a rock, a pipe, any ol' thing... but most especially, something with a side, you cannot see by walking around the map.

i have seen these errors go unresolved and cause maps to be scrapped.. i always stress frequent compiles, so you will always get the most recent errors, not something you made a month ago and now... are f**ked..

good luck :/

Not sure, but if you get really stumped just cut bits of your map out/block it up and try and narrow it down that way.

Maybe I should have made my question more clear. I did, by the way, look up the database, but found nothing usefull.

I think you guys were a little jumpy there :sad:

Wild Card said:
I think you guys were a little jumpy there :sad:

perhaps you are correct, but the question you asked, the way you asked it, had an answer..

the question sde asked, was the same, but with more info added

perhaps, you should allow him to ask his own questions, since he has the pertinent info available.

he is a member too :razz:

besides... how else can i get you back for telling everyone i sit down to pee :dodgy:

Orpheus said:

Wild Card said:
I think you guys were a little jumpy there :sad:

perhaps you are correct, but the question you asked, the way you asked it, had an answer..

the question sde asked, was the same, but with more info added

perhaps, you should allow him to ask his own questions, since he has the pertinent info available.

he is a member too :razz:

besides... how else can i get you back for telling everyone i sit down to pee :dodgy:

red text: I know, but at the time he didnt want to ask the question so I tol hime I would.

blue text: You bastard lol. :biggrin: Came kinda harsh though, I left, came back and the topic was locked, lol. Meany. And now, you deleted it. Is that what I am for you? File 13

WC, incase you slept recently, my mod powers are null and void, i cannot lock, delete or anything else anylonger.. seems i was uncooperative.

maybe all i am good for is sitting and peeing and causing a certain canadian some grief :/

Orpheus said:
maybe all i am good for is sitting and peeing and causing a certain canadian some grief :/

Duh, why else do you think you were put on this Earth for :razz:

Heh, well, aaaanyway... renamed this topic anyway in case anyone should have this problem in the console, and gave the search a bit of a tweak to make it more useful, so some good did come of this :smile:

Leperous said:
Heh, well, aaaanyway... renamed this topic anyway in case anyone should have this problem in the console, and gave the search a bit of a tweak to make it more useful, so some good did come of this :smile:

don't you just love it when a plan comes together :smile:

So we're all happy then?

Wild Card said:
So we're all happy then?

well, i would be more so if we knew what the answer is, but yeah this is going in the right direction :smile:

someday, my hope is, if another question such as this arrises, sde will be the one to answer it for them :biggrin:

And then you and me come in for our duet together

Wild Card said:
And then you and me come in for our duet together

you make up songs too?

i have one you might like.. :biggrin:

thinks on it a moment

better not, could end with my IP being lost :wink:

Orpheus said:
better not, could end with my IP being lost :wink:

And of course we dont want that... I arent much use around the Snarkpit without someone to laugh at me.

The 32/704 might mean entity 32, brush 704, which you can search for in Hammer from the Map menu with "Go to brush number."

Is your Alt+P problem list entirely clear?

Heh, forgot about that..Yeah, I tried 32 and 704, each as both Brush and Entity number, but no result :sad: (they just didn't exist). All that is on the Alt+P list is "Entity has unused keyvalues", and that's nothing to be worried about because I know what is causing it and it is meant to :wink: And Orpheus, that's sorta right, but it doesn't quite answer my question...since I know you hate red so much, and it isn't exactly wrong, i'll leave it yellow :razz:

Any more ideas?

my answer is correct, it just may not be this time..

may not be.

you won't exactly be sure, till you find yours :sad:

mark it how you wish, but till its solved i would leave it yellow, cause i would really like to know.

if there is another way of creating this error, we all stand to gain from knowing it.

I've had the error just -appear- before. After compiling a level a good 200 times, I had that error appear on a brush that was there the whole time. But mine actually showed up in Hammer, so I was able to fix it.

I know the cause of the error - "overstretched textures, often caused by clipping, or brushes"! What I want to know is what those two numbers mean (Bad Surface Extents 32/704)! The point is, the answer Orpheus gave doesn't quite answer that question.

Anyone?

so, you have ruled out grid coordinates then?

i suggest, you use leps suggestion then, chop the map up, i suggest in an orderly fashion, and stop up the ensuing holes, recompile each till the error occurs

you are in the unique position of teaching us...

Use the cordon option, no holes to fill or make.

I think I was taught the suggested solution to this in three simple words:

Big. Block. Method.

Could take some time if your maps huge though.

Loco said:
I think I was taught the suggested solution to this in three simple words:

Big. Block. Method.

Could take some time if your maps huge though.

how about 3 other words..

WON'T WORK BUD

you are thinking of leaks, this error deals with textures, and doesn't have to be seen to be reported.

hmmm, at least thats my understanding.

Try doing a brush entity search and putting either 32 or 704 in the brush number. Give that a try.

If not, as it was sugested, split you level in half, save each half in 2 different files. Compile the first one, if there is no error, compile the second. The one with the error, open it in VHE and split it again in half and save the 2 halves. Compile and keep going.

However, SDE, I sugest we finish looking at the screens I showed you first. Who knows, maybe somewhere, your problem will be solved. lol. Maybe not.

Either way, the choise is yours.

Orpheus said:
WON'T WORK BUD

you are thinking of leaks, this error deals with textures, and doesn't have to be seen to be reported.

hmmm, at least thats my understanding.

I think it will, as the brushes shouldn't be created by the compilers...

Leperous said:

Orpheus said:
WON'T WORK BUD

you are thinking of leaks, this error deals with textures, and doesn't have to be seen to be reported.

hmmm, at least thats my understanding.

I think it will, as the brushes shouldn't be created by the compilers...

i thought of that too, but each time i had this error, it was in an unseen location.. doesnt the compile ignore the area where brushes touch? i dont mean as in breaking up and causing r_speeds, i mean the parts actually touching??

anyways... this could be a teaching experience for some of us.. myself in particular..