@Thecheater887 Oh I see what you’re doing. As long as the angle units (degrees vs radians) is the same as the units the sine and cosine use, it’ll work (hyperPad works in degrees, so if your angle was in radians it wouldn’t work).
@Aidan-Oxley btw, this is kind of normal for my experiences with hyperPad. I try something, and find something buggy, and then do a couple of restarts, and then move around it.
Today's biggest accomplishment is that I figured out I can do this kind of rotation of a tag, so long as I don't do loops with Ease Out Exponential set as the curve type.
@Deeeds Yes, I’m stupid. Didn’t look at what I was doing. Erm, maybe this doesn’t work for rotations, but it does for Move to Object, or Rotate to Object.
@iTap-Development I always use set input field for things like this, rather than having a box container value inside the input field. Seems to be more reliable.
@Hamed In some cases, very rarely, I've seen massive numbers being reported. By massive, I mean those kinds that have "E" in them. Billions, or bigger.
Further, I've tried checking both sides of a collision. Both doing the same, reporting zeros, 99% of the time. Sometimes the enormous numbers.
@Hamed In the most basic version, just force users (me) to use square images, in square values (64x64, 128x128, 256x256, 512x512 etc) as this is a pretty common limitation. Most designers and artists for games are used to this limitation.