hyperPad Forum

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.

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?

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))

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

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

ah so good, thank you!

It works perfectly, thank you!

Yes, I try to double tap like 1 million times it didn’t work I tried 1 million and one time and it worked But this time it was scary….

I think you can benefit from using a wall object. You can apply a velocity on it using Set Velocity and it will continue moving forever. Now to make it move in a specific direction, you do need to use a bit of math. The Set Velocity behavior has x and y input fields. What do you plug into those? Calculate x by using the Sine function. Sine takes in an angle. Calculate y by using the Cosine function. Cosine takes in an angle. Here I take an angle (substitute it with whatever angle you want) and plug it into Math Function behaviors. [image: IMG_9329.png] [image: IMG_9330.png] Now I take the outputs of the Math Function behaviors, and multiply them. The bigger the number you multiply with, the faster the object will travel. [image: IMG_9331.png] [image: IMG_9332.png] Finally, plug the results of those behaviors into Set Velocity. [image: IMG_9333.png] In conclusion, given an angle and speed you want an object to travel, you can calculate the x and y velocity to apply to a wall object with these equations: x = Sine(angle) * speed y = Cosine(angle) * speed

Okay seems to be completely fixed now. Thanks!

Here's an example on how to use the Boolean behaviors. The Text Operation behavior can also work this way if you wanted to check the prefix of the behavior name instead or something like that. [image: IMG_9257.png] [image: IMG_9258.png]

Wow cool thanks

Nice I will join with you guys!

You need to save and load the array. When loading the array, you must reapply the tags. Let's start with saving and loading. After modifying the array (it should now contain all the tags you need), you can trigger the Modify Save File behavior and save the entire array. When the scene starts, you can trigger Load from Save File with the same key you used in the modify save file behavior. Now you can load the array, but you must add the tags back, otherwise all the work you did for saving and loading was for nothing. Grab the loaded value from the load from save file behavior, and plug it into the Modify Tag behavior. There is an option to set the tags of the object (or append tags) which takes in an array.

A better approach would be to utilize the screen behaviors to move between images. This allows things to persist instead of the entire scene resetting every time.

@pizzaking-i Is your system language changed? hyperPad should be going by system language.