@RobinsonX nvm the bug is fixed
Thanks

@TutorialDoctor Yeah, if a behavior fails to execute, then it doesn't execute the behaviors below. This isn't a bug.

So if modify array doesn't find a behavior to modify, then it encounters an error and doesn't execute behaviors below

Glad to hear you figured it out!

Not actually a bug.
hperPad has some built in checks and stuff that prevent this kind of stuff for project integrity and security.

This is actually intended. Global behaviours only get executed once unless you restart the scene and check restart behaviours.

Global behaviours continue through out each scene.

Oh nevermind... 😬
Found the reason, this is not even a bug at all.
It's just the way my behaviors were wired up.

Any way I could delete my own posts?

@davio said in Rounding Error for Object Positions on iPad Pro 11":

1- Set an object's y position to height/2

@Davio you really shouldn't be doing this because there will always be floating point rounding errors like this.

If you really need to check positions like that, I suggest checking for a range of values eg. If y > height / 2 + 2 and If y < height / 2 - 2.

@Dave007 It's because you're welding the objects and rotating them. Instead, you should be using like pivot attach

I tried playing it and it is working! Though in line with what @aidan-oxley pointed out, it has a strange “connection error" overlay on top...
0_1541810559886_0328BA85-C320-4BD9-999E-FFAD67AEE691.png

@hamed Thank you so much!
I'll try both of these out

@hamed Yes, it just worked right now. We found it in the user settings. Thank you!

@murtaza Woah I never even knew you could set velocity of wall objects!

I think I know why this happens...

HyperPad may see this as an intent of the object itself since the object is in the tag's group. Similiarly to using the loop behaviors to iliterate each object, it does it to only one object at a time.

In this case, the collision behavior will activate the following events because of each object that is collided within it's tag, it will have the intent of that object that it has collided to.

For example, two objects are going to be used. Object 2 is in a group. Object 1 has a behavior where when it collides within that group to change the color of it's tag. If object 1 collided with object 2 with the tag, it will change the color of object 2 as object 2 was the intent of this case.

This may be confusing, but I learned from experimenting with tags and looping properties.

@jack8680 It’s possible, but I believe it’s more likely that it’s not supposed to change the size, it’s supposed to change the text culling boundaries.

Hmm. This is odd. The sounds seem to be working again. I don’t know what caused it though.

Never mind, I managed to fix this by locking rotation of only the main object. Sorry for useless topic :P

@jack8680 I hadn't realised this before... but this seems to mean it's possible to send unique messages to unique objects, like iterating over them.

Which is kind of cool.

Very messy to setup and test, but potentially powerful.

@murtaza lmao im dying 😂😂😂

@murtaza Yes, we went over that today. Thank you for your time.

LOL it’s ok now, I fixed it. Not the actual glitch itself, but I just put a started touching behaviour on the background and that worked. Still don’t know why it was doing that, it was odd.