It is a crap system. It is completely unusable because why would I ever want my units to move just close to the destination?

Why does the pathfinding send an object near the destination and not exactly to the destination?

It seems to just stop right before the coordinates instead of exactly on the coordinates. Why is this?

Can it be fixed without having the object awkwardly jump to the destination after stopping?

For every game I have made or am working on I have to destroy a bunch

of sprites in the beginning that are created later during play. Is there a

better way to have sprites in the game that do not have to be in the layout

from the beginning? Is this the way everybody does it or am I missing something?

Thanks.

i.e. Bullets and missiles that get created by firing them when playing the game.

Where is that? I cant find it.

After about 20 minutes or so I will go to click on something in Construct 2 (not in a preview or game). and for seemingly no reason it will take forever to open the menu I clicked on. If I Ctl-Alt-Del and just cancel it it helps for the next thing I want to click on (basically the X and save file to close the program). If I close the program and reopen it it will be back to normal for another 20 minutes or so. I have searched forums and cant find anything. Is this a known issue? Am I the only person experiencing this? I've tried turning off autosave.

How to Reproduce.

1. Open Construct 2

2. Open file

3. Wait approx. 20 minutes

Windows 7 SP1

Ver. 184 64bit/Steam

Sprites in my debugger show their angle in 0-180. Negative when pointing up and positive for pointing down.

My problem is that one sprite will continue to increase of decrease depending on direction. while the other

will hit 180 and go negative or -180 and go positive to 0 then restart.

I've been able to convert the angles to a 0-360 format using % and variable.

Now I am stuck trying to get one sprite's bearing from another sprite. For example sprite A off

the nose of sprite B would return 0 degrees irrelevant of the angle of Sprite B. 270 degrees

off the direct left. 180 degrees off the tail. 90 degrees off the direct right.

In my project I have different sprites. If I go into debug mode and look at the angles

of 2 specific sprites one will go from 0 to -179 then skip to 179 and continue to 0 at

which point it will go negative again and start over (it is spinning counterclockwise).

i.e. never gets higher than 180 or lower than -180.

However, the other sprite in question, when spinning counterclockwise, will start at

0 and simply decrease to negative infinity. i.e. it goes to -4056 (or whatever).

I need them to both act like the first example. I am not sure why they are working

differently. If anyone can shed some light on this I would really appreciate it.

Update:

      I found a workaround. if I give the sprite a path then set Accel and Deccel to 0 it will turn almost completely toward the angle but not move forward or back. the "sprite.movingangle" will be as desired.

Condition: Blah Blah. Action: Sprite-> Set (path) Acceleration to 0

                      Action: Sprite-> Set (path) Deceleration to 0

                      Action: Sprite-> Set (Path) Rotate Speed to X

                      Action: Sprite-> Find path to (X,Y)

                      Action: Sprite-> Move along path

Hope it helps anyone else who needs it.

Ok i have made some progress and I determined that the pathfinding behavior saves the angle that the sprite is moving at. when the sprite arrives at the end of the path and begins to rotate its (pathfinding) "moveangle" does not stay updated to the current "sprite.angle". so when the sprite has to find a new path it starts its path at the last (pathfinding)"moveangle". my problem now is how to change the "sprit.moveangle".

Bump anyone?

I have a sprite follow a path then stop and rotate then stop rotating. afterward i have the same sprite move forward then find path and follow. the problem happens right when the sprite follows the new path. it glitches back to the same angle it was last pathfinding at then turns around and begins on its new path. How can I make it not revert back to the angle it was at the last time if was pathfinding? thanks for any help folks.