-
@gamecrazy
I am not using a beta version.
Restart your device. If it still doesn't work, reinstall HyperPad. But make a backup of all your projects first! If it still doesn't work, the problem must be yours. It works for me without problems. -
@itap-development Ok, weirdest thing. We have the exact same projects. Same behaviors, same objects, same settings.
I downloaded your link and it worked!
-
@gamecrazy lol 😂
-
-
Set Velocity used to mean (in past versions of Hyperpad) that there would just be a constant rate of motion.
-
Whatever just happened... Weird!
-
-
So, the best way to fix a bug is to have someone else make the same change, and send it back! Lol bug fixing was never easier!
-
@itap-development haha xD
-
Thanks for the help!
-
@gamecrazy no problem! At least it was an easy (ridiculously dumb) fix 🤣🤣🤣
-
First beta release on the hub now! Been working on this all day!
Before school starts, I’m going to be publishing a lot to the hub. Some of my App Store material, other ideas in progress, and an example project for my contest.
Will perfect my App Store page as well!
—
Let me know what y’all think. I’m excited to show off my stuff this week!
-
@gamecrazy said in Set Velocity Doesn't Work?!:
- Set Velocity used to mean (in past versions of Hyperpad) that there would just be a constant rate of motion.
Set velocity has always worked this way. You’re setting the velocity of the object, however it will naturally slow down and eventually stop because of other forces. Gravity, friction etc. It’s just how the physics works.
However if you do set velocity to a wall object that should remain constant. Since wall objects are not affected by outside forces. But this has some downsides as the wall object isn’t really meant to be used this way and can have unexpected results (like going through other objects)Another way to go around this is set friction to 0 and gravity to zero. Now your object should remain moving.
-
@murtaza Woah I never even knew you could set velocity of wall objects!
