Global Moderators

Very cool to see you updating this! Impressive to see how much you've learned and able to improve the performance so much.

So, I briefly spoke with @Hamed about this. It's doable, but trickier than I thought it would be.
Showing the collision editor from within the behaviour editor is currently not possible, just because of the way we manage the editors. We'd have to change how it works behind the scenes. It's possible, but requires a bit of time.

Changing the collisions using an array of points is easier, but the issue here is there is currently no point of reference for users. Meaning, it would be a lot of trial and error for you guys since you don't really know where the points are.
We'd need to tweak the current collision editor to show the point coordinates, this way you would have some sort of idea where things are if you were to enter the points manually with an array.

Soooo, It's doable, but not for a little while as we're in the middle of 3 updates.
IF this is something you guys really want and will actually use I can try to prioritize this. But I don't want to spend the time on a feature that won't be used.

So how would you guys expect/want this to work as a behaviour?

Changing collisions is pretty visual. So are you thinking like a change collision behaviour, properties would be object you want to change collisions, and then a button to open the collision editor for that object.
When behaviour is triggered it changes to your drawn collision?

Or is there something else you were thinking.

@kamdroid said in RobinsonX (Game ChangeLogs):

@robinsonx How smooth does the game run on your device?
I'm getting pretty bad lag and now sound stutters. Bit conserened about hyperPad's performance.

What iPad are you running, what OS, and are you jailbroken?

We test hyperPad on iPads as old as the iPad 2. Obviously the iPad 2 won't be as fast as the latest iPads, but in our test it typically handles most smaller to medium projects decently well. It heavily depends on what you're doing as well. Large graphics, graphics with a lot of empty space/transparency, complicated logic (loops, spawning, etc.) lots of objects, and particles will all cause performance issues and should be used sparingly.

The graphics engine is not that bad, but it expects users to take some care in how they create their projects. Yes, we could implement features that handle a lot of stuff for you, but then it sacrifices power and you wouldn't be able to create awesome projects like this.

@robinsonx said in Turn towards, but while touching the screen:

@Murtaza I think this happens to other behaviors with the speed function too...

From what @Hamed has told me, there is some extra code in place to interrupt behaviours like move so it doesn't do everything at the end. He mentioned that some behaviours may be missing this tweak. So if you have experienced this with others let us know and we'll try to add it for the next update.

@leewsimpson
Yeah I agree its kind of hidden.

Another hidden thing that should be documented:
Switch the rotate with parent toggle, this will allow the particles finish stopping.

I think there may be a bug with this. @leewsimpson can you send an example project to us (contact@hyperpad.com) where it is only working after you lift off?

Thanks!

To stop a particle you can use disable object or behaviour off.
Check out the behaviour references in our manual, it mentions it there https://hyperpad.zendesk.com/hc/en-us/articles/115003341106-Start-Particles

To those that messaged. Invites were sent out. Check your emails.

We're getting close to wrapping up the next update. This one isn't a huge one (even though it's pretty delayed).

You can see everything that is part of this update on our roadmap:

If you're interested in helping us track down bugs and issues just post below and I'll send out a testflight invite to your hyperPad account email.
Basically just continue to use hyperpad as normal. And let us know about any issues that pop up, or any hub projects that no longer work.

Unlike previous betas, we're not going to lock out the hub. However, users not running the beta will not be able to play a project shared from the beta (it will say they need to update)