Is this what you want?: fileport.io/fsZZQHae2MpF
I'll look forward to it
Check it out now: fileport.io/RfxzuvMUXVWG
There is a nuance. When there are many objects (in my case 20) The angle of motion and speed changes
There is a nuance. When there are many objects (in my case 20)
The angle of motion and speed changes
I didn't know you'd need more than two objets. I'll think of another way to do it for many objets.
dop2000 That will never happen again if you use this simple code:
Here is the new .C3P sample project file: fileport.io/rkDSu2KFmmTq
If you want a mega-ultra-hyper-super simple and easy solution, use the Physics Behavior and this single event:
Then, you will get this result:
Here you have the .C3P sample project file: fileport.io/4nfWCb2NdtnN
There are many situations where it is not desirable for particles to follow their emitter, so this option should not be mandatory, but rather a user-selectable option.
Develop games in your browser. Powerful, performant & highly capable.
So, I guess you'll have to choose between illusion and productivity.
SOLUTION: Don't start creating a new game until you finish the previous game.
Can you post a .c3p file with a basic example of the problem?
I confirm the problem. It happens to me too.
Simply, add these two events to your code: imgur.com/x08GkDf
Here it is: fileport.io/69NyD4zf95Vd
No arrays/dictionaries. Only global/instance variables. A more basic logic. Still few events.
Check it: fileport.io/nQzNp85tmPKd
That is really good! Do you want me to use that for the next part of my game?
Yes, of course.