When you share a project through email, links will last 365 days (1 year) rather than 7 days. Sometimes it takes me a little over that time to get to a project that you guys send us, and they're always expiring on me. I'm sure that you guys have this issue too... So I made it longer!
The email will still say 7 days until the next update, but it will actually stick around for 365 days.
I have finally finished the tool to clean up bloated projects. We're initially going to add a button to do this in the project options, and we'll do it automatically when we see that its safe to do so. For now, anyone that wants their project cleaned up, can send the project to contact@hyperpad.com and I'll email you back your cleaned project.
Guys, we know! We needed this feature yesterday. All I can say right now is soon.
Right now, unfortunately, is @Jack8680 way of doing it. I'll add number of decimal places to Round number behaviour.
Empty objects that are invisible are better, however, empty objects that are visible are worse for performance than a graphic.
It got removed because people kept “losing” their behaviours. But yes grouping it in this way is cool. What we want to do is create little functions that behave like JavaScript promises. Where you create a standalone function where it has a “resolve” behaviour to output when its done. And then make these functions shareable so you can import them across projects and send them to people.
A few things.
@Deeeds don't be disrespectful. I sent you a private message before about this. As you can see, everyone is just trying to help and you don't need to shoot them down and berate them. You're coming off as very aggressive and rude.
At this point, our users are way better at using hyperPad than we are and in this public forum, we rely on their help to answer simple questions. Like @Murtaza said, a lot of "bugs" are just user error so it makes sense to troubleshoot the issue with others before myself or @Murtaza can come in and declare it to be a bug.
Don't make assumptions about years of development when just coming into the platform. If you don't like something, let us know and we can have a public discussion of how things can work. Some things may look easy to add, but as most software developers know, NOTHING is ever that easy.
Somethings are indeed broken. We don't know about all of the broken things. When dealing with software with 1000+ features, its easy to forget about certain items and miss some things. We rely on user feedback to find these issues. e.g. I constantly forget about some of the behaviours you guys ask about... because we have so much functionality!
Everyone uses hyperPad differently, so we have to cater to how the majority uses hyperPad and not just you. appreciate our limitations and understand that we can't always cater to an individuals needs.
In conclusion, relax. We're working on it.
P.S, I can't re-create your issue... so I declare it not a bug. If you can create a little sample project with as few behaviours as possible, either I or someone on the forum can help troubleshoot it. like @Aidan-Oxley said, its not too hard to share a link onto the forum.
P.P.S Its really hard to find your issues / feature requests with a huge wall of text. Keep it short and to the point, and you're more likely to hear a quicker response.
Yes. We're adding it. It will be called Set Secondary Color
Have we released masks? Because I'm trying to figure out how you did this!
@bosswave said in Object rotation issues:
Upon closer inspection, it seems it might actually only be an issue when an object is being affected by the “propel object” behavior.
@bosswave we fixed an issue recently where if the screen is rotated, it was breaking propel object behaviour.
We might have not taken care of all cases. Can you make a simple project of what you're trying to do and send it to us so I can see if its broken?
@SplitMindGaming the problem here is that everything under repeat gets triggered every time. e.g if i have it repeating 100 times, the behaviour underneath is going to get triggered 100 times too. To see this in effect, add an Add to score behaviour under your repeating behaviours.
But looking at this behaviour that seems pretty wrong. I'm going to deprecate this behaviour and any new animation behaviours (after the update or beta) is going to work as expected
@SplitMindGaming said in 1.26 Beta:
@Hamed actually thats what that is. Comments attached to collision behaviors will not render the second collision once more. Basically All my behaviors have comments that are attached to them. Hence my entire game is broken at the moment with the current build. I will have to downgrade for now.
@SplitMindGaming You're going to have to either disconnect the comment behaviours or add new ones. We had to preserve the functionality of existing projects so we deprecated the old comment behaviours. You will need to do this before the final update.
Pushed up another build. We have a bunch more goals that we added for this update so might take a little bit longer than intended. Please test!
Fixed for propel objects.
Screen rotation and screen moving at the same time makes sense why it’s not working as you’d expect and I don’t think it’s something fixable.
The problem is that when you’re moving the screen and rotate the screen, you’re rotating it about a point. Normally that point is in the centre of the screen so it rotates about the centre. But when you’re moving the screen, your centre keeps moving.
If you’d manually control this through your own timer, it would recalculate the centre every frame, and not calculate the position once.
I see how this is a problem for Propel and the move camera behaviours. Can you guys make a list of all the behaviours that are breaking when rotating screen?
@bosswave how are you moving your player? I tried moving an object after rotating the screen and it moved as expected?
@Aidan_Fire said in Weird Colour Setting Bug:
en less sense. Why does this bug apply to the colour I was using (#66D5FFFF) and not basic colours like ffffffff or ff0000ff or 8080
Fixed. The hue was causing issues.
I like the first idea better. If you put it in the behaviour properties, it is hard to visually see your flow of logic