I haven't had a chance to check the project out yet.

But I can't quite understand what you're saying the issue is. In the global properties we have 2 settings, physics refresh rate, and physics iterations. These basically calculate how much physics calculations happen, and determine the "precision". This can remove that "jelly" like feeling. But it does come at a performance cost.

@jack8680 We have a winner! Worked like a charm.

I thought the behavior is supposed to be like this...

But I can understand, I want a behavior where it detects if your persisting touch goes off the object's boundaries, it will be perfect for UI buttons.

I've never had issues with looping behaviors, (other than getting a bit confused with it.) but I think it has been fixed in the new 1.2 update. :3

After pinbox opens.

It’s like the box lowers due to the keyboard closing, except there’s no keyboard, so it never raises.

Latest hyperPad, iOS 11.2.

Issue is recurring, and requires a force quit to fix

@hamed I don't think there's any magic to reproducing this. Every scene loaded by another scene seems to default back to 60Hz physics.

If you want to see it for yourself, that project I sent you, that you pruned out all the suspended objects from, that does it. It's supposed to be at 240Hz, but the pruned version is at 60Hz.

The original, I sent you, runs at 240Hz when you run/play a scene from the Editor. When you use the first scene to load a scene, however, it runs at 60Hz physics. And the problems begin instantly.

Collided doesn’t trigger when an object collision is spawned on top of the collided check, so I don’t understand why something so simple dashboards.

@Murtaza here's an example project: http://bit.ly/2rB7BMp (the behaviour is inside the thin white bar).

I'm guessing it happens when the object is too thin to actually draw any pixels inside the preview. Maybe replace it with the "Object" text that appears when an object's asset is deleted.

I don't think there is a bug here, at least not with move screen. It looks like something
could be interrupting your wait. Or for some reason it doesn't reach the move Screen.

As a test. What happens if instead of move screen you put an add to score behaviour. If the "score" is more than one. Then that means something is triggering your behaviour multiple times and interrupting the potential screen movement.

@Deeeds what I’m saying is that music can be activated inside Hyperpad and take over the audio. Then you have to close hyperpad to get it back.

This is an issue that’s been in the app for eons, and I’ve reported on a few times.

Affects anything that scrolls and selects.