@deeeds Is it the beta I'm on now, or the last update that stopped the numbers rounding? I thought it was last update, but I guess you making that post means it must be the beta. For me, numbers stay the way you entered them no matter what you do, so that'll be fixed next update :)

@pensegi yep, same! Highlight a bunch of behaviours and copy them, including the connection between them and other behaviours, or just an option to copy all behaviours connected in that tree (I like highlighting better, sometimes my trees disconnect but still work together) would be awesome.

@shady91 There was a specific bug/fault with the manner in which physics pivots/origins responded to changing graphics sizes, incorrectly. Or, far less than optimal, if you'd gotten used to it.

Correcting this was/is/did break things in previous projects. The pay off, in this case, is that you can now change graphics as much as you like, and their sizes, and get consistent, predictable, non peculiar results.

@kamdroid
Very close. Just a few tweaks to be made.
We're adding a "probationary" period, where all new accounts will have projects go in review first. And any project that's rejected will add time to their probation period.

AND, OR, XOR AND NOT

@thecheater887 another work around, scale them up in editor, then make the first action ever done by them, in isolation, be to scale to desired size at game start.

The inverse works well, too, with objects too big that intrude on touch areas when editing.

@thecheater887 hub updates will be handled differently.
Mid you wanted to do something like this you can with the existing http request behaviours. But need to keep track of your latest version on your own server.

Actually, not sure if @Hamed has created an API for the hub yet. If he did and the version number is exposed then you could just use http requests.

Yep, that does the exact opposite of what I want. That’s why I didn’t look there!

There needs to be a way to kinda just freeze time on any non-ui layer. Very critical for debugging IMO.

Yeah... I can see the problem.

You're saying that the combine text behavior should act like how you combine values/text in the box container, it would save up space and time.

Would definitely help with stuff. :D

Ah! You mean that!

Well, I never experienced this so I have no knowledge.
But yes, this is easy to fix as there is a workaround. :3

@hamed this locking, from the reliance on CADisplayLink falling behind, is also why hyperPad drains batteries. It's 100% CPU usage essentially looking/waiting for the next CADisplayLink, but which isn't enough for it to get back in front of itself. A loop just flogging and thrashing the system, needlessly.

@deeeds what about it did I miss?

@thecheater887 I think the difference between behaviour on and execute behaviour is that execute behaviour won't run the behaviour if it is off.

Like Kamdroid said, broadcast and receive are similar to what you're suggesting, allowing you to send an array or dictionary and use it in child behaviours.

Edit: fixed typo.

Yea, I requested this feature quite a bit ago.

Ohhhhh I see what you're saying now.

So with your example, players are consuming content... They're playing a game. With hyperPad it's more to it than that. They have to actually use the app and create something. So right away it requires more involvement.

So a survey is ok in some situations. But depending on the stage of the beta. It's mainly use the app. And test the specific functions we've changed or features we've added. But really, we're just asking you to continue using the app and if it's broken then report it in the beta section of the forum (where you only have access to if you're taking part of the beta).

Also with the betas we're selective of who can take part. Because sometimes they're trying out new advanced features that a beginner wouldn't know how to use. Additionally. with the betas you can't share to the hub. So this adds an extra issue for some people.

The major issues we had with betas is that users were excited at first, but then they either don't install the beta, or don't install the following versions so we don't know if their issues are fixed.

As for incentives, we did reward all beta users with "Developer" tiers.

You're right that the betas feel like it requires more dedication. And I think only users who are experiencing issues will take it seriously enough to provide their feedback.

I also agree. This functionality can dramatically influence the performance of newer games that includes huge amounts of objects, would help a lot! :)

@deeeds said in Hyperpad for iMac and PC?:

@murtaza OpenGL deprecation now looming...

Yeah... With Apple you win some you lose some. 🤷‍♂️