I dont think that event system works in 'on start of layout'.

Do it simple. Set X to choose(100,150,200,250) in the creation action.

You can duplicate a layout by rightclicking it ?

If they are supposed to land on the platform, you need the collision system. What you see is the Platfom plugin dooing 'push out' calculations.

I dont think collision filtering is supported at this moment.

So you have 2,5 options.

1/ Do not spawn objects in a way so that they overlap !

2/ Code youre own Platform with Chipmunk. A plugin by — It supports collission filtering.

Afraid the dotted circle was a lazy representation of the facts, i read that the user draws the dotted line. Can be a circle, can be anything, if users are allowed to draw its usaly a ....

Hi. I have a layout , which loads a tilemap tile by tile < copy those events to the next sheet

https://

drive.google.com/open?id=0B1SSuCVV8v74S2duZUFhWnJCUWs

& with an animation ofcours. Or pure animation, you could have done that.

You need to get your math up too.

https://www.google.be/search?q=capture+ ... e+with+vlc

Yes, individually.

Create (or spawn) creates no matter the Selected Object List. Read: No matter what you pick in its event/condition.

Therefor: you can not influence the create action in wich object it wil create by a condition.

But. As usual rexrainbow created a plugin that might help you by nicknaming instances and members of a family.

https://

drive.google.com/open?id=0B1SSuCVV8v74dTdQU0FOLWowUTg

Not using a 'every' is still every tick. I know that. Anywayz.

Try this. Just an idea.

Measure wallclocktime in a 'every x seconds' condition. You will see that the measured time will not be 'x' seconds. But a little shorter. How less Frames/second, how more wallclocktime will pass.

The 'real dt' should be 'measured wallclocktime / x'. Warning: u can not use this calculated dt to make pixel movements frame independed, dt (the construct one) is limited (some square function) and therefor more reliable.

The resolution (amount of x) you will have to experiment with.

Frames per second (updated every tick) should be, when you measure wallclock for 1 second / measure wallclokc every tick .

Is that a 'every tick' log ?

Did you pick the right tower ? Using tower.turetRange is fine. It just needs to know wich tower.

Same for the bullets. You need a instance variable that identifys the bullet as shot with a particulair tower.

Then you have to pick the right bullet.

And it will not be an '=' comparing, but an '>" comparing.

But i am not sure if that is practicable. You can also use the expression > distance(bullet.x,bullet.y,tower.x,tower.y)

More about the picking:

First you need a for 'for each tower'. That will make the picklist contain one and only one tower.

Then comes a sub event that picks all the bullets shot by that tower. Since it is a subevent and it picks differend objects then the tower, it will add the bullets to the picklist. So now you have in that picklist one tower and all the bullets shot by that tower. Then comes a sub event under the last subevent ''bullet distance travelled' > 'd'. That is also in fact a pickcondition. Since it is a sub event, its takes the previous picked objects and filters them. So now in the picklist there is one tower and the bullets shot by that tower that traveld a distance biggeer then 'd'.