You should read the Quake mapping Holy Bible, the Q1 tooltips from aguirRe (http://user.tninet.se/~xir870k/tooltips.txt) 

I recite that before going to sleep. Everyday. Out of my head...! 

You are forgiven, sinner ! 

Don't remember that page, looks like a gem! 

And as it states, those portal cut away errors are not critical, you may end up with a total errorfree BSP that still has those errors when compiled.

Nowadays compilers aren't vulnerable to those errors, thanks to rebb and ericw!

Still you may find missing faces, small HOMs, nonsolid floors, all that jazz.

So better stackenblock* all on grid.

*stackenblocken 

Well, it's less the compiler I'm concerned about and more the engine. I'm sure those errors don't help with mysterious collision problems and such. 

As you said. Fuck. 

"Try a value of -epsilon 0.0125, raising in 0.0025 steps. "

As a side note, Eric's QBSP has never heard of "-epsilon" ... 

Eric? 

I'll add -epsilon to the next build though 

 

Hmm.... Warnings = no fucks given :P 

OBJ2MAP -> Warning generator 

seriously though, even if i was falling through the ground... i'd just put a func_wall with skip over the invisible hole rather than bother trying to fix anything. it's faster and just as effective, not to mention transparent to the player. 

 

Drop the teenage rebellion attitude and go finish that dragon fortress! 

I always build on grid unless it's some weirdly shaped or twisted construction and rarely get cutnodeportals warnings. Most common problems they cause are small invisible walls and falling through the floor.

If there's no way to stay on grid, converting the brush(es) to func_walls will fix it, or if already on grid just smooth over with a clip brush. 

Well I cheated a little, but I was able to get the level vis'd. I just built a box around the entire level, and then stretched the external walls from the level to meet the faces of the box's walls (that way all outer walls are closed, and are see-through when I noclip)
An amateur approach, I know, but it worked.

I'll ignore the clip warnings for now, but they are pretty annoying. Sorry mfx, I have a ghetto set up with no home internet so I'm using my phone to talk to you guys. I'll remember to send you the clipping warning when I get home. 

That expanding wall technique is a good approach, i do this too, especially on sky/closing brushes. 

Wait, so was qbsp writing a pointfile or not? 

It doesn't always. I've had leaks with no pointfile before. Those are SUPER DUPER fun. 

I'm just making double sure the new guys know about that sweet red leak-finding line. I didn't know about it for like the first six months of making Quake2 maps, and when someone told me about it on IRC it was like seeing the face of god.


Look for "load pointfile" under 'file' or somesuch menu, it varies by editor. Every compile that leaks (in theory) writes a yourmap.PTS or .LIN file that lists coordinates of the centers of all leaves connecting the edge of the grid to whatever entity the test hit first (it assumes all entities are inside the map, which they should be), in order.

That line (in theory, 99% of the time, unless you're doing REALLY wacky hyperdetailed slanty things) always goes right through whatever accidental microtunnel you left between brushes. If the leak appears to go through an otherwise solid brush, that brush may be fucked up somehow and getting tossed out by the compiler (there will be accompanying warnings), it may be an out of date leakfile and you didn't actually get a new one after all, or your brushwork is just amazingly dangerous.

It's also a good reminder when you just forget to build a ceiling. 

you can also use the command 'pointfile' in most Quake engines, and it will draw some points for you in engine (limited by particle counts)

it will likely also be useful to use 'gl_clear 1' when doing this too, since you'll want to noclip around to find it, and having a HOM void is annoying. 

I do use the pointfile cvar command on a regular basis, but for some reason, the leak file wasn't being updated at the time.

mfx - that's a really good idea, running qbsp after saving. A lot of the time I make too many changes in between compiling, which makes it near impossible to debug once there's a problem. I'll definitely make a habit of that.

The message is: WARNING: CutNodePortals_r:new portal was clipped away

Thanks! 

What am I missing here?