I think I found it,
- Code: Select all
Static prop models/props/gg_vietnam/light_noshade01.mdl outside the map (427.00, -488.00, -298.00)
Static prop models/props/gg_vietnam/light_noshade01.mdl outside the map (-205.00, -479.00, -298.00)
Static prop models/props/gg_vietnam/light_noshade01.mdl outside the map (-202.00, -4.00, -298.00)
Static prop models/props/gg_vietnam/light_noshade01.mdl outside the map (409.00, -9.00, -298.00)
Those props sticking outside your level will cause compile issues, I think its something to do with Hammer Editor being confused as to where the level is, whatever the case maybe this is like having a leak or maybe you do have a leak, which will seriously fuck your map up! So go to those coordinates by looking at the very top buttons and clicking view then you should see a go to coordinates button, paste the coordinates inside that dialog box that should show up (remove the "," between each coordinate, only have one space between them). Make sure the origin of each of those props are inside the level, or you can make a block to cover the origin of the prop and it should then count as being in the level (Yes, the origin of the props can be through the brushes that touch the void and still be in the level, just not outside the brush and into the void).
If this doesn't fix it then try loading your point file and seeing where the red line goes and close up your map, if you are unsure how to do that then go to the very top buttons and click map then go to the load pointfile button, if there is no point file to be loaded (should be where your .vmf(s) are saved) then run the map, still not, then you shouldn't have any leaks.