Hi, yet another problem, and a strange one, this:

I have two characters both using the same functions. One controlled by joystick, one by keyboard. Collisions work fine usually, but if you turn both characters to face one another and press the forwards button for both of them, they pass right through one another - huh? I'm using the move_gravity from movement.wdl, and everything works fine apart from this.

Any suggestions about what's going on? "You" is set to null, origin is at the centre of the model, I've tried changing push values etc and using ent_move instead of move, but always the same thing happens.

Thanks,
Keith

P.S. I did a search on the forum and saw that a few people have had this problem before, but couldn't find a solution - though the search function is down on the Beginner's forum so I couldn't search there. Cheers.

Anyone? This is really annoying - one minute you're beating the pulp out of an opponent, the next he's walking right through you...

Thanks,
Keith

I don't mean to be a pain, but this really is driving me crazy... Here are some screenshots to show you what I mean - the last two were taken while both the characters were moving forward - and they pass right through one another!
http://vulcan.spaceports.com/~lethargy/collision.html

Thanks for any help,
Keith

P.S. None of the visuals are mine, btw - the models are from the old Quake II Gauntlet project - I've just been using them as dummies so I can get the programming done before creating my own models.

try fat hulls..

did you set scale_X/Y/Z in your function?

Hi, thanks for your answers. I was already using fat hulls, but this shouldn't make a difference as the problem occurs only when two entities are moving towards each other - collision is fine with map entities. I tried setting my.scale_x, but that didn't do anything. I also just tried reducing the speed at which the characters are moving, but the same thing happens...

In fact, exactly the same thing happens in the Office level too. If you go into 3rd person mode and get the old wizard dead in front of the guard and press forwards, sometimes he'll pass right through him (although this happens a lot less frequently in the Office level than in my level). I've put a small picture of this happening on the webpage I linked to below.

From what I've read in another thread ( http://www.conitec.net/ubbcgi/ultimatebb.cgi?ubb=get_topic&f=6&t=000320 ), I think the problem lies in the fact that both entities are performing a move instruction at the same time - any suggestions on how I can work around this?

Thanks again,
Keith

Hi Ambit,

put in a WAIT 1 either after your move or at the binning of your event action, this makes sure the move can complete ....

greetings Ronny

Hi Ronny,

Thanks for your help again. I just tried this out, though, and it still seems to have no effect. Like I say, it's only when both entities are facing each other square and moving forward (or one behind the other moving forward as the other moves back) that they pass through each other. I guess because the move is happening at the same time for each they just get pushed into one another...

Cheers,
Keith

Hi Ambit,

were did you place the wait instruction ?

greetings Ronny

I tried placing it right after move_gravity() (I'm using a modified version of the the template function, though I'm not actually using movement.wdl at all). I also tried placing it directly after move() in the move_gravity section (thought it has to go after the my_dist section, otherwise the character's walking animation gets screwed up). I couldn't see anywhere else to put it...

But then, the problem exists in the Office level (though it takes a little trying to see it there), so the problem obviously exists in the template scripts too...

Actually, I've just done a quick check and discovered that the problem does indeed lie in the template script... If I just do a quick and rough move not using move_gravity, collision is fine. Guess I've got to dig deep into the template script to find the problem then.

Thanks Ronny, your suggestion helped me realise this...

Cheers,
Keith