hyperPad 1.26 Beta
-
This actually just seems to be a bug with how iPad Pro positions the graphics in general. @Aidan-Oxley you can confirm this with your background wrap project. Open up your project and switch to iPad Pro. You will notice all the images are spaced out. You probably have a better way of explaining what is going on.
@SplitMindGaming That's not a bug with hyperPad with the black spaces in my custom wrap project. That's a bug in the way I made it work. The images are the exact size of my iPad screen (normal iPad Air, ratio 4:3). When you change to anything other, they get moved into places they shouldn't be in (since they all position themselves with relative coordinates). I think I know how to fix it properly, and I also know a quick fix: change all of the background objects to absolute coordinates, but leave their behaviours the same (they will keep using relative coordinates in the behaviours). You shouldn't need to worry about the background objects using absolute coordinates because they take up so much space there's no way a device exists with a screen big enough to still see outside the range they cover.
-
@SplitMindGaming That's not a bug with hyperPad with the black spaces in my custom wrap project. That's a bug in the way I made it work. The images are the exact size of my iPad screen (normal iPad Air, ratio 4:3). When you change to anything other, they get moved into places they shouldn't be in (since they all position themselves with relative coordinates). I think I know how to fix it properly, and I also know a quick fix: change all of the background objects to absolute coordinates, but leave their behaviours the same (they will keep using relative coordinates in the behaviours). You shouldn't need to worry about the background objects using absolute coordinates because they take up so much space there's no way a device exists with a screen big enough to still see outside the range they cover.
-
@Aidan-Oxley your talking about this right?
@SplitMindGaming because according to apple your project now has to both work with the regular iPad and iPad Pro. Now although it works. There’s an obvious screen rendering issue where the objects are not being aligned where it should be. This scales up and down with other screen sizes properly. It’s only like this with the iPad Pro.
-
@SplitMindGaming because according to apple your project now has to both work with the regular iPad and iPad Pro. Now although it works. There’s an obvious screen rendering issue where the objects are not being aligned where it should be. This scales up and down with other screen sizes properly. It’s only like this with the iPad Pro.
This post is deleted! -
I was so confident it would work, and somehow it doesn't. I still know there's something wrong with the way I programmed it though. Because of the image sizes it only works for screens with the same size I think. I think I can fix it though.
-
@Murtaza has there been changes made to the beta? If so do i have to redownload it from testflight or does it automatically update. Not sure how this works.
-
@SplitMindGaming no changes yet. I believe you get a notification in the TestFlight app.
@Hamed sas hoping to have a new beta out by now, but one of our employees got sick so he’s working overtime trying to cover his work.
@Murtaza i see. Hope he gets better.
-
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!
@Hamed whoa play my game i sent to you today on the new beta. The falling coins are spinning out of control.
-
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!
@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 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.
-
We're aiming to push out a new beta on Sunday.
Includes some really cool new features. Render to texture, shaders, and more!@Murtaza Render to texture sounds cool, would this be creating a single texture out of multiple game objects?
-
We're aiming to push out a new beta on Sunday.
Includes some really cool new features. Render to texture, shaders, and more! -
@RobinsonX yes. How it works is you create a “render texture” behaviour. And a draw behaviour where you can draw primitive shapes or stamp an image from a load image behaviour. Then there is an option to choose from a list of effects (shaders)
Render texture can also be chained with other render textures so you can cascade effects
@Kamdroid yes. We can add string manipulation behaviours not in this beta but the next one sure.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login