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

This is the only warning I'm getting. No more warnings about leaks, but it still won't vis. It's not writing the prt file, but it's also not writing a .por file either, so I can't pinpoint the clipping portals, or the leaks.

Sorry it took me so long to write this. 

Is not stopping Vis AFAIK... 

use pastebin. 

I get about 5,000 of those warnings every time I make a map. I wouldn't worry about it. I can't remember the last map I made that had clean output from QBSP... 

I usually fix those, because i can. 

How? I'm willing to learn but I have no idea what it's even talking about so ... 

Well, i had the intent to document my experiences with all those errors (and how to fix them) anyway.
Thing is, i probably need visual examples, be it drawings or map snippets to explain this in detail.

But, for those errors to appear in thousands, you prolly have to raise the machine epsilon first.
Try a value of -epsilon 0.0125, raising in 0.0025 steps.

I compile often, just to look at the output, not loading the map in engine. I do this regularly, after adding rooms, rockwork, special detailed structures..

So i am able to nail those errors down very early, not having to check whole maps afterwards.

Next thing to check are those suspicious coords like having a vertex at 800 -64 - 128.0000023.

Those are the bane mostly, locking them to grid fixes portal cut away errors, at least for me.

When i find a portal error i cant fix with above methods/precautions, i make a new small brush at the specified coords, and look to "expand" existing brushwork to cover that brush.

Can be anything, pillars, more rocky wobbles, anything. Usually this all leaves me with no errors in the end.

I admit, the "real" reason for those is cloudy to me too, looking at the src left me shaking my head til dizzyness. :)

More later, must consult a friend. 

floating point stuff is the main reason for those errors to appear, just reassured. Build stuff on grid! 

Thanks a ton, man! I'll try to put that into practice on my next map and see what happens... Clean compiler output would be nice for a change. :P 

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!