Hi All,

I'm having some trouble with c_move  and negative values, and I'm hoping this is a really simple oversight on my part because I'm starting to think I'm better off working on my own collision-detection then relying on this inconsistent function.

I made a level in WED with a ball and a paddle (both MDL models) and attached a script with actions for both models, then built the level.  

Paddle Action Code:

action move_paddle()
{
var pspeed = 4;

while(1)
{
If (key_a)  //move left
cm_move(me, nullvector, vector(-pspeed*time_step, 0, 0), GLIDE);

If (key_d)  //move right
c_move(me, nullvector, vector(pspeed*time_step, 0, 0), GLIDE);

wait(1);

}// end while

}// end action


The 'd' key works fine (moves to the right), but the 'a' key does nothing or will randomly move to the right too if I toggle the bbox flag in WED.  I've also tried replacing the pspeed variable with the value "-4" in the c_move function and I get the same results.  Same story with the ball action, won't move if a value is negative.

Most other c_move topics I've seen involve setting one of the _PASSABLE flags but I've tried a few of those too with the same result.

Can anyone help me with this?  There has to be something I'm missing...

-Q

I cant see anything wrong with this code as such, so I think it is just an
"un-expected" collision causing this problem.

As a test, try using all these flags, and it should move fine.
If this is the case, try them one at a time till you find the one that makes the problem go away.
Then you'll know what type of object is causing the problem, and that should point you the the problem object.
Then you just have to decide what to do about it...
IGNORE_WORLD | IGNORE_MAPS | IGNORE_MODELS | IGNORE_SPRITES | IGNORE_CONTENT | IGNORE_PASSABLE

Another thing you could try is this(untested)....

The object it is colliding with should sort-of flicker enough to be seen.
This will work if it is an entity, terrain or model I think.

All you need is something like this(its extracted from a script I wrote for a workshop for kids):



I can't see a wait(1); in your code.
If you actually didn't have any in your script, I wonder how it worked, anyway.

@EvilSOB
Wow. That flicker/collision thing is genius! I completely forgot that I placed the paddle and ball in a giant hollowed-out cube (model). A simple IGNORE_MODELS flag is all I needed after that to get things working properly, and that was a great example of how the YOU pointer works. Thanks for the help!

@Pappenheimer
Sorry, I retyped the code from memory and left out the wait(1), but the original code had it in there (I'll edit original post). Also, thanks for the c_move suggestion. A slightly modified version of that could come in handy.

- Q

Glad to be of help.