Non-Issue

Upload bug

Murtaza — Mon, 10 Jan 2022 10:45:54 GMT

@Alexwolf01 said: The button is between my screen and I can’t move it or delete it and yeah, I found a lot of bugs like this it’s so annoying. You should create your own thread with the bug rather than reply to a 4 year old thread that is unreleated. But make sure you're on the UI layer. By default buttons are added to the UI layer, and you can't interact with them until you switch to that layer.

Set label not working

RobinsonX — Thu, 06 Jan 2022 14:58:50 GMT

@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

Transparent images losing transparency

Murtaza — Sun, 29 Sep 2019 03:49:34 GMT

Glad to hear you figured it out!

Copying a project (not branching) causes files to be unable to open

Murtaza — Fri, 22 Mar 2019 19:41:04 GMT

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

Preloading Scene Causes Behaviors To Not Trigger In Global Objects

Hamed — Sun, 20 Jan 2019 14:31:45 GMT

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.

"Jump" Behavior seems to not function after opening an overlay

RobinsonX — Mon, 07 Jan 2019 21:27:10 GMT

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?

Rounding Error for Object Positions on iPad Pro 11"

Hamed — Thu, 06 Dec 2018 19:53:07 GMT

@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.

Rotate Behavior Bug

Hamed — Tue, 04 Dec 2018 16:30:19 GMT

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

Flipped objects with revised collision points

Aries29 — Tue, 06 Nov 2018 22:14:59 GMT

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... [image: 12fb7228-8699-4ce8-9bf5-977680528775.png]

HyperPad Crashes During Animations and Cloning

Davio — Sun, 07 Oct 2018 20:56:51 GMT

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

Subscription Error

Davio — Wed, 26 Sep 2018 15:02:36 GMT

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

Set Velocity Doesn't Work?!

Aidan_Fire — Sat, 25 Aug 2018 15:43:44 GMT

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

Collisions with tags affect single objects

RobinsonX — Fri, 06 Jul 2018 12:47:57 GMT

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.

Label Scales Improperly

Thecheater887 — Fri, 06 Jul 2018 06:23:42 GMT

@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.

Sounds not playing.

Epicmametchi — Sat, 16 Jun 2018 01:16:23 GMT

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

Weld Attach and Lock Rotation don't work together

Andrey Ghost — Thu, 07 Jun 2018 11:53:42 GMT

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

the "Change Picture" Option doesn't work in the Edit section.

Cyber_Death — Fri, 13 Apr 2018 19:39:38 GMT

@murtaza lmao im dying 😂😂😂

Health Bar Glitch

Yo-Buddy — Wed, 21 Feb 2018 20:04:22 GMT

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.

Dropbox Not Working W/ Hyperpad

GameCRAZY — Mon, 19 Feb 2018 21:27:25 GMT

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

Spawn Doesn't Respect Layer of Origin

Deeeds — Mon, 12 Feb 2018 18:30:46 GMT

@murtaza you said... If you want to respect the original objects layer then don’t use spawn on object, instead use spawn. i said... this also disrespects the original layer of the spawned object. Common sense AND convention of spawning's uses in all other environments trump your anecdotal experiences with a dozen users and naive newbs, regardless of the timeframe. Particularly because they're going to move on from your app to the rest of the world's creative products, most of which use the following conventions. Spawn AT (doesn't exist in hyperPad, is a specific point. Requires user fudging in hyperPad) Spawn [with]IN (geometric space inside a shape, and what you call Spawn On) Spawn [up]ON (geometric space along the edges of a shape. Doesn't exist in hyperPad) None of these alter hierarchical structure, they always respect the editor layering (by user) where it's available. Layering, sorting and other hierarchical choices of a user are always presumed deliberate and therefore respected. Layering is a completely different type of sorting, in a different place, for different reasons, none of which pertain to geometric space, except Z-sorting in 2D, in which case the layer sorting becomes imperative to the user, and should be respected by the engine for this reason, alone. That should be reason enough to consider respecting layering choices of an end user. But I see it's not. So let me make other cases: Your app is a gateway drug to the worlds of digital creativity. If you want to be fondly remembered, referenced, revered and referred to, your best bet is to match your tooling, paradigms and processes to where your best (and most influential) users will eventually find themselves. Then those 6 years of users experiencing your product might actually mean something to others, and help create exponential user growth. Most obviously and logically important, when layering matters most (performance optimisation), the processes of manually moving newly spawned objects between layers will further hurt already tight performance constraints the user is deliberately using layers to attempt optimising around. So your current approach confounds the very best possible use of layers. I apologise if my making of more than one point is confusing, or bewildering. Also, sorry if my appeals to logic, rationality and reason distort your constrained perspective.

Spawn On Object Doesn't Heed Rotation

Deeeds — Thu, 23 Nov 2017 23:07:54 GMT

@GameCRAZY You've made it so by claiming he's actually addressing the problems. He's not. He's isolated a single way to do a single thing with a single object on a single spawn. That is the very opposite of the reason for the problem being a problem. And, like your other comments, this seems to stem from a desire to not consider anything that's not what you want added to the next release. IAP,, I gather.

Move To Point: Duplication is broken

Murtaza — Wed, 08 Nov 2017 21:47:49 GMT

Ahh I see. So, so you want a way to keep the existing x and y coordinates even though you select a new object. Hmm, it's definitely possible on a technical side. I just need to figure out how the UI and usability would work. At one point we wanted to separate selecting an object and visually selecting the position. But couldn't figure out a good UI paradigm for this. Need to find a way to make this optional as well for when you do want the positions to change when an object is selected. Just brain storming as I'm typing this. But a button that says select position. That lets you move the target only. Then if/when you change object A/B, it will prompt asking if you also want to change the manually entered coordinates. Yes reverts to 0,0 of the object No would maintain your change. Does this sound like something that would work?

Broadcast message in a loop

Deeeds — Sat, 15 Jul 2017 18:17:30 GMT

@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.

BUG: Overlay/Scene Preload

Murtaza — Mon, 12 Sep 2016 06:05:11 GMT

There are some technical stuff behind the scenes, it's just easier to keep it this way. There is also help window the first time you open the scenes/overlays saying you must be pro to enable.