News | Forum | People | FAQ | Links | Search | Register | Log in
Mapping Help
This is the place to ask about mapping problems, techniques, and bug fixing, and pretty much anything else you want to do in the level editor.

For questions about coding, check out the Coding Help thread: https://www.celephais.net/board/view_thread.php?id=60097
First | Previous | Next | Last
 
Well, now I wanna play your maps. 
Monster Clip? 
Noobish question, but how can I make one?
I can create func_wall covered with skip texture and owner:1, but that would block everything (except player), not only monsters.

I tried to duplicate random texture in wad and rename it with few variations of "monster_clip", "clip_monster". That didn't work. 
 
I don't know how to put this to you DW. There's no easy way to say it.... so, I'll just say it.

I'm afraid you can't. 
 
Monsters don't cross holes in the floor. It's usually a bug that needs to be fixed by the mapper by covering it with skipwalls or some other hack, but if you're willing to put in some stylish vents where you want to stop monsters they'll refuse to path over it, which is nearly the same thing. 
 
Yeah what lunaran said.

Example here: http://www.celephais.net/cv/image.php?ant2.jpg 
That Might Just Work 
Thank you.
I assume everything deeper than stepheight would be enough, correct?

That linked image confuses me a little. Wouldn't monsters try to cross using that thin bridges?
Maybe there is minimum floor size they can use for navigation? 
Infinity Walls / BSPs 
Hey guys!

I just started using Trenchbroom and I'm having some problems when I'm cooking/baking the map. Just for testing I created this one room with just an enemy some lighting and pickups as well as a player spawn. It cookes/bakes well and when I load it in-game the bsps seem to be invisible, so I can look out in the infinity. Yet I can still see the enemy and the pickups.

Anyone know how to solve this?

Cheers,

/ Stefan 
1) post a link to the .map because it could be a number of things

2) you don't need to sign your posts 
DWU 
It's to do with navigation - they won't cross a gap they think they can't.

In order to make it invisible to the player you can put a func_illusionary in the gap. 
One You 2 Many 
 
 
That linked image confuses me a little. Wouldn't monsters try to cross using that thin bridges?
Maybe there is minimum floor size they can use for navigation?


The way monsters navigate is mostly by blindly moving towards their enemy, turning randomly whenever they hit a wall or cliff. So technically they could cross those narrow beams but it's very unlikely . So if you want 100% impassible you probably need an unbroken gap with a func illusionary to fill in if desired. 
Monster Clip 
I wrote an article on how to program monster clip here:

https://tomeofpreach.wordpress.com/2015/11/18/selective-clipping/ 
Bonus Hack 
If you don't care that it won't work in COOP mode, you can hack monster clip by making a func_wall with clip brushes as described in the blog post above. Then add to that func_wall the key

"owner" "1" 
 
I don't think monsters could path over those thin beams as the monster would be considered partially in the air due to some corners of its bbox being off the floor. AI won't willingly move to this state. 
 
Ah, so it tests all 4 corners for ground contact? Then I agree 
4096+ 
My current map exceeds safe limit and I have HOM effect starting at 4096 (only size warnings in log, no leaks).

In this case I'll move few rooms to fit, but was wondering is it possible at all to make a map which is larger than 4096?
Why editor shows grid up to 65536 if I can't use it? 
 
It's a network protocol limit. You can make maps larger than +-4096 but they will only work in engines with a protocol that supports it, like darkplaces. 
Why Are Leaks So EVIL 
It might be explained a thousands times, but every time it breaks me up.
Why does a map start leaking while there is no common explain for it?
A kinky brush, a wrecked up detail, an unusual corner.
All I see is a red line that leads me to a *.prt file making me guess there will be a bad brush.
When I deteckt the bad brush and delete it another one shrimps up like a balloon pressure.

I can block them off with a cube and precise the dilemma, but I just don't understand the meaning of it.
Give me a looking box and I can tell when there's no hole to look in but.., aargh! 
 
Because math. 
Excuse 
me for alladin. 
On Leaks 
Is it because id wanted accuracy of geometry over usability? Or was this a limitation of the tech at the time?

Out of interest would less leaks occur with relative coords rather than a static grid? 
 
coordinates relative to what? 
 
to each other, or the first brush placed. 
2 posts not shown on this page because they were spam
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.