My map worked wonders earlier… absolutely no leaks at all.
Then I add one trigger_teleport and compile the map, boom: It whined that the misc_teleporter_dest -entity leaked, and I also recieved MAX_MAP_LEAFFACES =no BSP file.
WTF?
My map worked wonders earlier… absolutely no leaks at all.
Then I add one trigger_teleport and compile the map, boom: It whined that the misc_teleporter_dest -entity leaked, and I also recieved MAX_MAP_LEAFFACES =no BSP file.
WTF?
sometimes i get similar warnings, like “entity leaked”, but there is really no leak. It is just a bogus message sort of.
At other times, I have placed a model, such as a light model, too far inside the brush, and that too gives a similar “entity leaked” message.
Map works fine though, so I often ignore the warnings.
However, you get a second warning, and it is much more of a real warning, max map leaffaces. I have no clue what it is. Search google, I would do.
Yoda, I talk like, now.
//Loffy
Hmm funny… I restarted radiant a few times and then at one point the misc_teleporter_dest appeared in the void… So I moved it back to its place and now everything works again.
I’ve noticed this happens with a few different entities. It seems like entities that have an origin key sometimes get out of sync and look like theyre in a different place then they really are.