Ignore "Bad surface Extents"? Created 8 years ago2016-01-30 20:17:22 UTC by EsprimoP

I know this might sound silly and I know what causes the error. But can I somehow make the compiler and the game ignore it? Maybe extend some limitations in the codes?

Isn't easier to fix your map?

Yeah, just alt+p and fix the problems.

Please answer the question.
Alt+p didn't help ("No problems found")

Too much vertex manipulation I guess... try to find tiny brushes and force to grid the most evident problematic brushes, also tie to entity those which aren't part of the world wall's brushes.

Ya better not to ignore them. I admit I sometimes do it myself but if you get to many of them then your map might crash at a certain point. Or Hammer all the sudden refuses to even compile the map and you don't know why at that time.

So ya fixing it might be annoying if it ruins some of your brushes again. But better to do it right than not at all. Also it makes your maps less laggy. Got a very complex map which lags beyond reason and fixing that is so frustrating. So keep your r-speeds low when possible my mapping clean.

I know how to fix it. I fixed it. I am asking one simple question.
Can I make the compiler and the game ignore that? Can I, or can I not?

Considering nobody knows of a setting to do so, and they're suggesting ways to actually fix your bad geometry, I'm guessing it's not possible.

Why exactly do you want bad geometry in your compiled map anyway?

You can't ignore this error, and even if you were able to do it, the (unforeseen) consequences would be fatal.

I know you fixed your error but I would like to remind to you (and also others) why this error can happen :

1) "Texture axis perpendicular to face" error (Urby mentioned the way to fix it which is Alt+P).

2) You have an empty solid entity (in other words, you have a brush entity that doesn't take any physical space on the grid and the editor/compilers have no idea how large/tall it is)

3) You have a solid with an invalid structure : bad Morphing/Vertex tool usage is the most scenario to have this problem (it's a concave brush instead of a convex one).

4) Texture scaling : imagine a texture with a 999.999 X scale and 1.0 Y scale, this error should happen.

All I know is that this problem will ALWAYS make the compiler crash, at least this is what happened with some of my maps. Why don't you post where in the compile process appeared the error?, it'll help. Also, if the map compiled completely, did the map lags, crash or show extrange behaviour in certain areas?, also have in mind that this is not a aesthetic problem like the HALL of mirrors problem, it's related with the consistency of the very world structure... I hope you can find the solution!!

Im assuming you want whatever effect makes the compile fail? What exactly are you trying to do