removed

Izotope

Sourcerer
aa
May 13, 2013
698
764
You have a leak.
Load your pointfile and fix it.
 

NateTDOM

L1: Registered
Sep 3, 2016
29
2
For future reference, http://www.interlopers.net/errors is a website were you can paste your compile log and it will tell you errors wit hyour map, and what they can cause. A large amount of compilation interrupters have been from displacements(i find), so look out for wat interlopers tells you on that.
 

Startacker!

WANT ME TO BE REAL? MAKE ME.
aa
Jun 15, 2013
647
1,197
The pointfile should create a red line, which leads from the object that's leaking to the void, follow it and find out where it goes.
 

Startacker!

WANT ME TO BE REAL? MAKE ME.
aa
Jun 15, 2013
647
1,197
I have done that, hammer is no longer creating a pointfile and It was also making me things that were allready in the map
I'm not exactly sure what you mean by this.
 

Vel0city

func_fish
aa
Dec 6, 2014
1,947
1,589
EDIT pretty much what killohurtz said
 

killohurtz

Distinction in Applied Carving
aa
Feb 22, 2014
1,016
1,277
You're absolutely sure you turned off radius culling? No red circles in the 2D views? The fact that things are cut off abruptly in those images tells me it might still be on.
 

Vel0city

func_fish
aa
Dec 6, 2014
1,947
1,589
If you click on Alt+P in Hammer which brings up the problem checker, does it tell you of any invalid brushes? Because that's what "WARNING: BSP node with unbounded volume (material: <NO BRUSH>, near (-511.142761, 1024.000000, -514.298035))" usually means and it's a compile crasher.

If it does find any, you can either fix it via the Hammer problem checker (which is Alt+P) by clicking on fix, or make it go to the invalid brush(es) to fix it yourself.
 

Vel0city

func_fish
aa
Dec 6, 2014
1,947
1,589

Vel0city

func_fish
aa
Dec 6, 2014
1,947
1,589
You have to rename the new vmf to something else, otherwise it will try to use an older bsp.