Forum posts

Thanks guys. At least now I know it's not just me. Yes, I do know what a leak is, but what I don't know is
1) Why Hammer calls my "light" entities leaks.
2) What makes a solid "empty" when you tie it to an entity?

I've searched and have found various explanations, all different.

Someone please enlighten me on this F*'n program v3.4! I have been playing around with this for a couple of weeks now and have had to scrap several maps that I've put many hours into because this program calls every freakin entity I put into it a leak. I can build a cube, hollow it out and leave it as is, put a light in it and after serveral test runs the light becomes a leak even if I don't touch it. Can you feel my exasperation? Hell, now I can't even get the console to come down when I hit ~. When I "run" the map I have "-dev -console -cstrike +set -deathmatch 1" plugged in. I even tried +console to no avail. When I build I keep the "snap to" option on to avoid leaks. Map runs fine, now it doesn't. WFT!? I spend more time looking thru the FAQ's/tutorials and still can't find this "func_entity empty" crap, "func_pushable empty", hell I didn't even have a pushable object in the level. Is there a newer version out there? BTW, I AM using zoners tools too.

Okay, let's assume I create a block. I want it to rotate. So then I create a smaller block and apply the origin texture. Now I group them together and tie them to the func_rotating entity. What did I delete? My entity is still empty.

First post. Can someone tell me what the hell that means? Lights, walls, barney's, all empty. Had one map of fair size that I had to scrap because of this. I'm new to this and getting a little tired of starting from scratch because deleting the entities doesn't fix the problem. Thanks. :