[CS:GO] Hammer - Enclosed map suddenly started to leak

[Fjoggs]

Hi, I've been struggling to fix a leak in my map that basically started occuring out of nowhere after I rescaled some parts of my map. 

Relevant error log from the compiler :

FindPortalSide: Couldn't find a good match for which brush to assign to a portal
 near (-112.0 976.0 -144.0)
Leaf 0 contents:
Leaf 1 contents: CONTENTS_SOLID
viscontents (node 0 contents ^ node 1 contents): CONTENTS_SOLID
This means that none of the brushes in leaf 0 or 1 that touches the portal has C
ONTENTS_SOLID
Check for a huge brush enclosing the coordinates above that has contents CONTENT
S_SOLID
Candidate brush IDs: Brush 68160:

FindPortalSide: Couldn't find a good match for which brush to assign to a portal
 near (-112.0 976.0 -144.0)
Leaf 0 contents:
Leaf 1 contents: CONTENTS_SOLID
viscontents (node 0 contents ^ node 1 contents): CONTENTS_SOLID
This means that none of the brushes in leaf 0 or 1 that touches the portal has C
ONTENTS_SOLID
Check for a huge brush enclosing the coordinates above that has contents CONTENT
S_SOLID
Candidate brush IDs: Brush 68160:

 I've been looking at various sources online, https://developer.valvesoftware.com/wiki/Leak being one of them, and it looks like I'm having some troubles with my areaportals. My map currently contains no textures with areaportals, so it's all handled by the compiler.

None of the links I've found have provided a solution to this problem, and I'm a bit stumped really. Loading the pointfile just shows a redline from an entity that goes through my solid skybox.

I've included the .vmf for anyone interested.

de_flashbeng.vmf

[El_Exodus]

Something in your vmf was broken. C&P to a new file worked for me. I uploaded the fixed file for you.

But start optimizing your map early. Use func_detail!! The map already takes ages to compile in that early stage. This shouldn't be the case.

de_flashbeng-fix2.vmf

[Fjoggs]

Oh wow, that trick works for Hammer too huh?  GtkRadiant used to randomly break maps as well, and a copy paste would solve it. Thanks a lot!

Regarding func_detail: This is just how make my maps. I always leave optimization until the end. That's just what I'm used to after 15 years of mapping.  I just use -fast when compiling vis as the map is so simple it'll give max fps anyway.

Thanks again, really saved me a lot of tinkering.

[Bastion]

Couple of things to always keep in mind as you work on maps to prevent these leaks, they're a common problem and the fixes can be quite simple.

• C&P to a new file, although that makes problems for version control
• Make sure that nothing sticks out of the skybox, if a entity is exposed to the void you will not get to compile, check the exteriors of your map, even if the entity is inside the skybox brush slightly.
• Displacements cannot be used to seal maps, always have a brush bellow it to back it up

Although it is mainly just hammer messing with your head.