Monsters don't follow path_corner Created 16 years ago2007-12-15 16:07:09 UTC by veclast

Long-story short: monsters(but other entities as well, such as trigger_camera) don't follow their path_corner, but only if I give them a name.
If not, they follow it just fine.

Any idea why this happens?

so they follow their path only if you give them a name, but if you don't, they still do?... What is that supposed to mean?

No offence, but maybe you should read that again.

What I said was that they DON'T follow their path_corner if I give them a name.

Of course, you have to trigger them...

How do you do that?
I thought you just set the target(to follow the path_corner), and you're good to go.

Use a trigger_auto if you want the sequence to start when the map loads. Otherwise, use a trigger_once. If you don't know how to trigger stuff at all, read up on it here.

No, you need to trigger the object.

There are many ways to trigger stuff, think buttons (func_button), invisible triggers (trigger_once, trigger_multiple) or other entities that have a target keyvalue.

Add two func_buttons, and have one target the camera and the other the monster.

Note: If you want to have monsters follow a path, use scripted_sequence entities instead, they have more control over the monster then just path_corners, for example, you can have a monster, barney, for instance, knock on a locked door, then let it continue its patrol.

Take a look at my scripted_sequence example map to see how its done.

No offence, but maybe you should read that again.

My mistake. sorry

For the record, path_corners are probably the absolute worst way to go if you want a monster to follow a path. Sure, they're easy to work with, but they're also easy to break.
If anything, anything gets in their way at any point down the road, they stop moving. At that point, you won't be able to get them moving again.

Learn to use scripted_sequences, they are much more powerful. It might seem overwhelming at first, but it pays off soon enough.

if im not mistaken, monsters will move around obstascles to get to the next spot in a scriped_sequence, right?

Aye captain. That or they'll wait for the obstacle to be removed, and continue their path.

World Crafter, they must have used path_corners extensively in Half-Life, because I remember quite a few instances where Barney or a scientist simply would not open a door.

Well that doesn't matter because you obviously like guys

Decompile and check. But I've never had any problems with scripted_sequences. Nor have I ever seen an NPC simply stop moving toward their goal in HL, which is surprising considering the amount of time's I've played the game.

Ok, so what do I do if I have two scripted sequences(say point1 and point2) and I want a monster to walk between them?
If I understand MuzzleFlash's map right, I have to target point1 to point2, and vice-versa, but it doesn't work in my map.
What happens is, the monster moves to point1, then point2, but not back to point1. What am I missing here? Does it have anything to do with the fact that these points are in opposite directions?

Also, how do I work around between trigger_camera and scripted_sequences?
I set a few scripted sequences for the camera to follow, but nothing happens, the camera just sits there.
Now, I have read the tutorial on trigger_camera, and did everything written there as well.
I have a trigger_camera, func_train, path_corner's, multi_manager and trigger_once, all set in place. I didn't understand if I have to put the camera inside the train, or just target it, but it doesn't matter because the train is not moving.
He targets the path_corner(not the first one, but the one that follows, as the tutorial says), I added him in multi-manager, I trigger him, ..and nothing.
Any idea what to do?

You have to tick the 'Repeatable' flag so he can use it again and walk back.

Ok, we got that out of the way. Thanks.

Now, what about the camera?

It looks like I overlooked something from the trigger_camera tutorial.

Make a small cube, textured with the '{BLUE' texture. Place an origin brush in the centre of it and tie them together. Then hit 'To Entity' and select a 'func_train'.

What exactly is an origin brush, and how do I make one?

Yes, I read that, but it still doesn't answer my question.
How do I make one?

Well that doesn't matter because you obviously like guys

...what?

There is a texture specifically called "origin". Including it with any entity will make the entity use the center of the origin brush as it's origin, instead of the map's origin.

Thanks for clearing that up.

But now, another thing.
The func_train(with the origin brush inside, all tied up) is already at the destination(/last path_corner) when I start the map. I don't even get to trigger the thing.

its not getting triggered at all?

Nope, and I'm sure of that.

Also, the camera still doesn't move to any path_corner, when triggered.

srry said:Quote:
Well that doesn't matter because you obviously like guys ZOMG -

...what?

I dont like girls, or guys. I like dogs, too much .

l2quote

aaron_da_killa should get together with ZombieLoffe and have a beastiality party.

rofl

It's not even funny. Actually, It's repulsive that you even told us that. Go back to 4chan.

lol

Every now and than look around the room or out the window, to give your eyes a rest and allow it to focus on different distances, if you don't, you will need to wear glasses later in life.

Experience, I suppose?

As for the camera thing, you're sure you've gone through the tutorial step by step, and haven't missed anything?

the camera itself has a path too, right?

gah, triple post!

I'm pretty sure I didn't miss anything, and yeah, the camera has a path.

gah, triple post!

shutup!

If the camera has a path, is triggered, but still doesnt move, it would have to do with your entity settings for either. Make sure that the camera correctly targets the first point in the path, and that all other settings are correct. Make sure speed settings are set correctly on all the points, and make sure each correctly points to the next point in the path. And finally, make sure the trigger corectly targets the camera, and is indeed triggering correctly. This sounds like an obscure problem, it may help to upload the problem map.

shutup!

-->

Make sure you specify a speed or initial speed for the camera. A speed of 0 means its not gonna move at all.

Strange thing happened. I tested the map earlier today, and everything worked great (camera-wise; it seemed MuzzleFlash was right about the speed issue), and just now I decided to test it again, and.. you've guessed it; the camera isn't moving.
Note: This is the exact same .bsp map, not recompiled - nothing changed.

Guess I'll have to upload the map and maybe someone will find what's wrong with the camera.

Im pretty sure you're missing something obvious, like a key value or something.

Make sure you've specified a speed, a first stop target and a target (for the camera to focus at). Also make sure that you're path_corners are correctly linked (each one targeting the next).

If all this doesn't help, post the map in the Problems Vault.

I'm pretty sure I did everything right, since the camera did work a few times before.

Maybe it's something to do with the game?
I'm mentioning this because I tried running the map again, and the camera moved, but not to the finish. It's almost as if she stopped at the 3rd path_corner, and wouldn't go further.
Could this be a bug?

I uploaded it anyway: http://twhl.co.za/mapvault_map.php?id=4922

Sounds really weird, considering nothing changed, and you havent even recompiled. I never trust cameras, ill download the map and examine it when i get back home from school. My guess is that theres something with the entity settings, or maybe even the triggering settings, that is causing the weird, semi random bugs.

edit: This is why i dont trust cameras. I looked at the map, and nothing seems to be wrong, all the entity settings are okay, as far as i can tell. Yet, when i compile and run it, the camera stops at the first point. Very strange, considering all the settings look right. I would wait for a reply from a more experienced member, because this really has me confused

Ok, thanks anyway.