old_var = new_var Doesn't work 

Paths cannot be moved while there is an instance following them.

After assigning path(in Create event):
CREATE EVENT

 //create variable for old position pos = path_position //take object off path path_end(); //move path to view path_shift(path0, 0, view_yview) //put object back on path, absolute = true path_start(path0,1,0,true); //move along path a bit path_position = pos + 0.004; 

STEP EVENT

 pos = path_position path_end(); //move path with view (in this case, y -1) path_shift(path0, 0, -1) //put object back on path path_start(path0,1,0,true); //move a bit path_position = pos + 0.004; 

Hope this helps other people. gawd knows i struggled with it.

I'm working on a project which uses a view, which moves from the bottom of the room to the top.

It needs to have an object follow a path, left to right across the view. The path is working, however because the view is moving up, it causes the object to appear to shift downwards, instead of staying at the view's vertical position.

I've tried moving the object itself up every frame (both with 'jump to position' and 'set vertical speed'), which has no effect. Not sure what else to try.

Is there any way to move the path with the view? I'm using GM Pro.

Thanks,
Simon.

I followed this tutorial, because it is 99% similar to what i want.http://gamemaker.wikicomplete.info/helprequest:how-do-you-make-the-mouse-act-as-point. I want to be able to have a turret that follows the mouse in a 90 degree angle and stop past that, after following this tutorial, it works however, if i go past 90 degrees its flicks back to the original frame.

Sorry if it isn't explained very well but i quite literally started game making about 2/4 weeks ago :P

Thanks. Ryan.

 In the create event: jumps = however many jumps you want to be able to do jumpable = jumps In the jump event: if jumpable < jumps +1 -do the code for jump- jumpable -=1 In the collision with ground event: jumpable = jumps 

I used this in a couple of games each with a different means of jumping but in all of them I was able to limit the number of jumps until the player hit the floor.
Be wary, though you have to make the ground object different from say a wall or ceiling. other wise you will have to find out which side of it you are hitting and that can take awhile, I find.

Sir_Willard: […] shouldn't some kind of tolerance be added to the code | if (direction == point_direction(x, y, OPlayer.x, y))

No, it shouldn't. I know what you're talking about, but that's not the case here. The main reason is that this particular game is some sort of platformer (as suggested by a statement made in a previous post that the Enemy units can only move LEFT or RIGHT), thus direction can only be either 0^o or 180^o. That takes care of one side of the identity; as for the other, you may notice that I have used __the same value (i.e. y) for the two 'y' coordinates required. This guarantees the vector whose direction is being evaluated is horizontal, thus its direction, again, can only be either 0^o or 180^o.

In conclusion, additional tolerances are not required simply because there are no "rogue" values that can be produced on either side of the identity.

Just to wet your appatite:

 if (direction == point_direction(x, y, OPlayer.x, y)) 

from my experience, this fails a good amount of the time, since the direction isn't rounded. You have to be pixel for pixel lined up in that direction for this code to work consistently.

Of course, I've been out of this for a while. Just an observation.