@Deeeds That is strange. Maybe send a picture?

@Jack8680 INCREDIBLE!!! THANK YOU!!!!!!!

There is a bug with the sound effects editor that we just haven't been able to track down. Where sometimes the sounds corrupt or don't play. :(. As for the website, we don't actually use this as part of hyperPad, we just based ours on it. But you can find the site here: https://www.bfxr.net/

Guys lets keep this civil. While we appreciate our passionate users trying to defend the app, we know it's not perfect. We also really appreciate the passionate users who are willing to give their feedback and information. We know hyperPad has tons of room for improvement. Somethings we couldn't do based on timing, or they rely on something else. Other features we decided not to include on purpose. But in the end when users give their feedback it really helps us prioritize, and helps us find things we missed. We're all here for the same reasons, and we all (hopefully) want hyperPad to be awesome. :).

@Jack8680 said in Get Bounce above 100%: HOW?: Yeah, it's an odd restriction, not having higher values for bounce. It's in every physics engine, but someone must have gotten "safety conscious" and decided against surfacing it to users. Could come with a warning. I'll "file" another feature request. Shouldn't have to use unreliable get and sets to increase bounciness.

@iTap-Development I enjoy finished things. And finishing things.

@Deeeds like Aidan says, I think while moving is meant for the physics engine (if x and y velocities are both not zero), like while falling (if y velocity is less than zero). It should activate 60 times/second while that physics behaviour is running. It could be a bug though, I've hardly ever used it.

@Deeeds You can make hidden variables. Under the Object tab look for Set and Get Attribute. (Also I usually don’t use Add to Score, I usually do it the long way by adding to the previous value which is stored in a box container).

@Deeeds yeah, Hyperpad recommends no more than 3 zero timers(for performance reasons), but I don’t think it would hurt to just add the if under one of your existing timers. Or if you want the if in another object from the timer, you use the behavior on or a broadcast message to trigger the IF.

@Aidan-Oxley Yeah, got this. This unit of measure was actually mentioned in the "docs"... and /60 is one of the few math-like things I can do. Cheers.

@Deeeds yeah, it's 60 times per second. It doesn't adjust with your physics speed, but the maximum fps is 60 so you won't need any faster for screen moving.

Here's an image describing the offset of the initial anchor point on the head, each subsequent tail section has its own anchor point moved the same distance in the corresponding inverse direction of travel: [image: 86cd8734-855d-47bf-9014-9b62ce4afe4f.jpg]

@Robertiii Just turn the drag behavior off instead of deleting the objects (once you get to the attributes)

@Deeeds Haha real dirty, also less efficient. Value for subtract values = amount you want to increase or decrease by ÷ (amount of seconds it should take × 60) (the brackets just meaning the times 60 happens before the division). Doing maths in hyperPad rather than your dirty method is usually much more efficient. But your way is heaps easier especially fur curve functions.

I appreciate your input, and definitely see where you're coming from. However, as it is now I don't see it as a huge deal. This issue affects a VERY small amount of hyperPad users. Unlike most companies, we're fairly open on our development plans and take community feedback very seriously. We typically do as the community votes/requests. As of right now there has only be a few complaints of hyperPad users who are not happy with the splash, and the majority of them have been about redesigning it to suite their needs. If more users come forward we'll implement a change. If you don't think this is a reasonable approach I'm happy to discuss it further via PM or email.

Yup. All iPads should be showing the exact same thing on screen.

@Aidan-Oxley Yes, that's the result. What's actually happening is the passing through of the transform of the parent (world space) to the children. So position, rotation and scale/skew of the parent always influence (or get passed through) the children. In most engines the transparency is also passed through, too.

this is a bug. Sorry! If you preload with a behaviour it will work

Yeah..... I can see where that would get annoying!

You can't do that. Each project is "sandboxed" into it's own environment. What you can do is create a scene within your project as a playground, then copy objects to another scene when needed.