@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.

@Aidan-Oxley Yup, got it working.

@Deeeds ok👍

@Thecheater887 https://hyperpad.zendesk.com/hc/en-us

@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.

@Hamed 👍 thanks!

@Deeeds thanks!

@Deeeds if you turn a behavior on that has behaviors connected above it, it won’t trigger immediately. But if you turn on skip events, it will.

In the reply box there is a small text in the top right corner that says "Compose ?" click the ?. It will bring up a popup with formatting link. Or just go here: http://commonmark.org/help/

@Deeeds just turn the ignore collisions off.

@Thecheater887 Have we met? You sure sound like a pot calling a kettle black.

@Deeeds Only if the Behaviour On doesn’t have Skip Events toggled on, and the behaviour you’re turning on is connected under another behaviour (or if I’m using the right terms, it’s a child behaviour).

@Thecheater887 Play suffers much the same problems as Start. Activate Initiate Launch All suffer the same problem. They convey a false sense of an instruction having been sent and that's it, that's all. But that's not it, not all and fails to come close to conveying the extent of what's going on, and what this behaviour is doing, and will do.

I’m willing to bet a big variable is the timer halting off bug you found.

[image: 5602d818-d94c-4483-91b4-5af1a8fc4966.jpeg] Nothing goes wrong when I do this. The only problem I get it that I can’t name objects to that of an object that’s either in an existing scene or was in a scene after it has been deleted (as mentioned in my bug report somewhere).

Have now mirrored the items I need into a new scene. Then copied them, and deleted the mirrors. The problems persist. The camera in the subsequently loaded scene takes on the properties of the camera in the default scene. Not using Global or Scene layers. Appears to be a bug.

@Hamed The Receiver Behaviour that had this problem, once it stopped working, no longer cared how I set the key. It simply stopped working. I had, quite literally, two keys with the same Event Key, and could turn one off and the other on, and see that only the new one worked, that the old one had bitten the bullet. Could never be reused, in any way. This is the first time I've seen this particular type of bug, where a behaviour node has seemingly lost contact with the hyperPad world. It took an enormous amount of time and testing to isolate it to this being the problem. It was about the last thing I thought could happen...

@iTap-Development No. It isn't possible to get them to stop and stay in sync with other objects. So it's not possible to restart them, and keep sync, either. These are all workarounds for the lack of sprite sheets, the lack of bitmap fonts and the lack of image swap transitions... oh, and the lack of referencing and addressable instances.