hyperPad Forum

Thanks @murtaza . I’m getting the below pop up when installing, would you mind resending the invite or share the code please? Thanks [image: 91c397a8-0b5e-4ed1-ba15-f1e0c2bf8369.png]

@Murtaza Thank you. I really appreciate you guys. I’ll wait I will just go back to making assets till then. 😂have a great day.

If you could make one it would be a great time saver.

ah so good, thank you!

I see, thank you, man

If Move to Object is being retriggered very frequently and it has a big enough duration, it can stop working since the move animation is being interrupted over and over again. If you try 0s duration for the Move to Object behavior, then it will work since the animation is instant and therefore cannot be interrupted.

If you need a payment, it’s okay… I am full now

@TutorialDoctor Perfect time to check in. Lots of big stuff on the horizon :)

I found a solution. The solution is to use a frame event (I forgot the name the first one, the others do not work) directly on tags To pull objects from UI on main layer for example, and if you want these object to stay there durably. Frame event, move to layer (with tag(s))

@Alexwolf01 said: The button is between my screen and I can’t move it or delete it and yeah, I found a lot of bugs like this it’s so annoying. You should create your own thread with the bug rather than reply to a 4 year old thread that is unreleated. But make sure you're on the UI layer. By default buttons are added to the UI layer, and you can't interact with them until you switch to that layer.

I've expanded the pixel editor to be a full art studio. It can now do larger graphics, and has various brush types like an air brush so you can create all sorts of graphics. I've also expanded on the animation tools by introducing Skeleton animation system. hyperPad doesn't currently support bones, so the plan here is that your created skeleton animation will flatten to a regular sprite sheet that works within hyperPad. Until we eventually offer bones. Screen Recording 2026-07-28 at 2.14.20 PM.mp4

Hmmm, this is pretty good idea. I think this can be split into 2 uses. Make a project setting of supported devices. This shares to the hub, and when you play it in the hub it also preserves the device it is desiged for (I think in this case it should auto default to the one closest to your current aspect ratio). An editor setting, to automatically select the desired aspect ratio when running the project from the editor. This way you can quickly test with out always having to switch aspect ratios. Of course in both situations the available aspect ratios will be selectable from the in game menu as it is now. Does this idea solve your problem?