[Solved] Props "leaking" from sealed map

Werewolf

Probably not a real Werewolf
aa
Apr 12, 2011
873
309
When I try to compile my map, it keeps telling me that various props are outside of the map:
Code:
Static prop models/props_lights/light_fluorescent_basement.mdl outside the map (3152.00, -4280.00, 224.00)
Static prop models/props_spytech/control_room_console02.mdl outside the map (3112.00, -3776.00, 32.00)
Static prop models/props_spytech/control_room_console03.mdl outside the map (3112.00, -3696.00, 32.00)
Static prop models/props_spytech/terminal_chair.mdl outside the map (3144.00, -3736.00, 32.00)
Static prop models/props_lights/light_fluorescent_basement.mdl outside the map (3152.00, -3736.00, 224.00)
Static prop models/props_spytech/terminal_chair.mdl outside the map (3144.00, -3992.00, 32.00)
Static prop models/props_spytech/control_room_console02.mdl outside the map (3112.00, -4032.00, 32.00)
Static prop models/props_spytech/control_room_console03.mdl outside the map (3112.00, -3952.00, 32.00)
Static prop models/props_lights/light_fluorescent_basement.mdl outside the map (3152.00, -3992.00, 224.00)
Static prop models/props_spytech/terminal_chair.mdl outside the map (3144.00, -4280.00, 32.00)
Static prop models/props_spytech/control_room_console02.mdl outside the map (3112.00, -4320.00, 32.00)
Static prop models/props_spytech/control_room_console03.mdl outside the map (3112.00, -4240.00, 32.00)
Static prop models/props_lights/light_fluorescent_basement.mdl outside the map (3152.00, -4536.00, 224.00)
Static prop models/props_spytech/control_room_console03.mdl outside the map (3112.00, -4496.00, 32.00)
Static prop models/props_spytech/control_room_console02.mdl outside the map (3112.00, -4576.00, 32.00)
Static prop models/props_spytech/terminal_chair.mdl outside the map (3144.00, -4536.00, 32.00)
The thing is, they aren't.

I have checked that I haven't accidentally set a world brush as something like a func_detail, by hiding everything in the visgroups then only selecting World brushes. The map IS sealed.

When I ask Hammer to load the pointfile, it can't find one to load. I usually take that as an indication that that the map is in fact sealed as it only generates a pointfile if there is a leak.

For some reason though, Hammer insists those props are leaking yet does not provide any evidence of how or where they are leaking though.

Does anyone have any ideas what is happening or how to fix it?
EDIT: All fixed now.
 
Last edited:

MOCOLONI

L6: Sharp Member
Dec 16, 2014
373
89
I once had that problem with a recompiled version of Hydro (using the official .VMF), and although I don't really remember what it was, I recall something like having props inside of brushes *somehow* leading to the void.

There's also a thing I had to do on a decompiled map, which may not be useful for you but still: https://tf2maps.net/posts/416147/
 

Werewolf

Probably not a real Werewolf
aa
Apr 12, 2011
873
309
None of those props are clipped into brushes. Half of them are light props correctly aligned on the ceiling.

EDIT: Turned out, they were!
 
Last edited:

Werewolf

Probably not a real Werewolf
aa
Apr 12, 2011
873
309
No it wasn't that, but it was another dumb little mistake I had made.

Turned out I had a 'tools/trigger' textured brush that wasn't assigned to an entity. A nobuild zone I hadn't actually set as a func_nobuild. And it covered all the mentioned props.

The only reason I didn't notice was because I was only compiling with VBSP and VVIS (to check for leaks) instead of doing a full compile. The first time I tried a full compile I spotted it, fixed it, and what do you know the error stopped.
 

MOCOLONI

L6: Sharp Member
Dec 16, 2014
373
89
No it wasn't that, but it was another dumb little mistake I had made.

Turned out I had a 'tools/trigger' textured brush that wasn't assigned to an entity. A nobuild zone I hadn't actually set as a func_nobuild. And it covered all the mentioned props.

The only reason I didn't notice was because I was only compiling with VBSP and VVIS (to check for leaks) instead of doing a full compile. The first time I tried a full compile I spotted it, fixed it, and what do you know the error stopped.
That was it then. Relating to my previous post, this is the thing that happened in a decompiled version of Barnblitz where a SKIP/HINT volume had faces with textures other than the latter two, potentially breaking the perf volume's function and leading props into the Void.
 

Freyja

aa
Jul 31, 2009
2,995
5,813
This error means a prop is entirely inside a brush. It's not a "leak" per se, so your map will work fine with it.
 

Werewolf

Probably not a real Werewolf
aa
Apr 12, 2011
873
309
This error means a prop is entirely inside a brush. It's not a "leak" per se, so your map will work fine with it.
Yeah that's what it was. As I said to crash, it was a 'tools/trigger' textured brush which I had meant to set as a func_nobuild, but had forgotten to.

If it's a large map, this might be caused by having Radius Culling on (basically anything not in the Hammer 2D camera viewport gets clipped off, causing weird semi-leaks.

Why such a button exists I have no idea.
Er... see above?

I mean thanks to both of you for seeing this thread and adding answers to it, but uh... it was already solved/fixed.