Thats probably 3d.
I peed my pants a little at :40.
Yeah thats pretty buggy.
Someone should submit a proper bug report tho...
OP's is not formatted correctly.
"Sine behavior: now reads initial state again when being set active, so it respects any changes in the state of the object"
Considering that the only previous state it knew was disabled, it may actually be working, ... sort of.
Its working, its just not using the preset values.
However you can set them directly after you enable the behavior.
Dont forget a key word here, instance.
You can create multiple instances of them, and use the variable for picking, ...for instance.
Develop games in your browser. Powerful, performant & highly capable.
Nope.
Can't confirm.
Standard check drivers prompt starting now.
I think, for this instance, you would be better off determining if the "snapped" touch xy is greater than, less than etc of the initial touch position.
The angle serves no purpose.
Just do a "is in touch"
sprite set angle to angle(self.x,self.y,touch.x,touch.y)
With the hotspot set to the 0 x.
System compare isn't the best way to go. Ideally you would do all the comparisons in the actions, rather than the conditions.
Maybe you could say what you are trying to do?
How would you decide the correct order?
Thus far I've just gone with the same order as they are put into conditions.
https://www.scirra.com/terms-and-conditions
Member since 12 Nov, 2008