Adding New Broadcast and Receive Behaviours that operate across layers massively increases build time. For me.

@Hamed Oddly, I've found how they're not exactly in the same spot every time... just right around the start point of the level... they're paying attention to the rotation of the hero. So all 3 particle systems are somewhere in the proximity of the starting point, relative to some weird distance that shouldn't be there (they should start right where the hero is) and then rotating via the hero as their anchor centre around him, based on whatever distance they succumbed to from the hero at start. This might mean they are some kind of physics object that's falling before the start. Maybe. I don't know.

@Aidan-Oxley Thank you so much too sir!!! God this forum is so wonderful with talented programmers like you and Sir Jack!😄

Nope, not supported. SVG files are vector images. Vector graphics work differently, and not something we support. You'll have to use another app to import/export them as PNG or some other pixel graphic.

Thanks for the tutorial RobinsonX! Can you help me with some other game mechanics too? Like the scoring mechanics used for the sample tappy plane game? I tried to look into its game logic from the sample but being a novice teacher who is eager to use hyperpad to create and educational game for a research I am working on with less than a week, I really am in need of some good samaritans here to see this through...😭 I can't get what sir hamed did with the score and best score showing up every time the player is out which I believe starts with receive message (did lose). They are supposed to show different values and update themselves everytime the player tries again the game, right? But i can't figure it out...

@Colymoly Not sure why @GameCRAZY didnt respond, so I made an example. Here’s the download link: http://bit.ly/2mUH3Rt The red object is the player controlled by the joystick, the green objects are objects on your layer that you can run into, the purple/pink/blue stars are the parallax background objects, each on their own layer creating a bit of a 3D effect. Parallax behaviours are in each star. (in case you don’t know how to use the download link: copy the link, paste into safari then the project will download so you can open it in hyperPad).

@Thecheater887 Oh I see what you’re doing. As long as the angle units (degrees vs radians) is the same as the units the sine and cosine use, it’ll work (hyperPad works in degrees, so if your angle was in radians it wouldn’t work).

@Jack8680 Exactly!

Performance Tips: Put everything you don't need interacting with your main characters on different layers. Just do it. The performance gains are real. Make sure no images are stretched beyond 2048 pixels in any one dimension. Crop your images as tightly as possible in image editor to get rid of as much extraneous Alpha pixels as possible Use partial opacity sparingly, particularly on big images Try to make everything you can think of a spawned item. When in doubt, spawn and destroy the original Recycle particle systems by moving them to where you need them and restarting them instead of creating new ones Edit sounds in audio editor so there's absolutely no clipping. OpenAL/cocos2D tries to reduce clipping and does so in a very costly manner Don't be tempted to use the pitch change. It seems to be a live change and exasperates the clipping performance issue above. Record uniquely pitched sounds instead, and pick and play the ones you need Preplay your sounds, with silent volume if need be, so they're cached before they need to be played. I don't know why this works, but it seems to make a big difference. I thought we were beyond the time in history when we needed to do things like this for audio on iOS. Use Exponential eases on Colour changes with caution. They're costly. If at all possible, use Linear "eases". For colour changes, they're noticeably cheaper than others. Push everything you need to store into central arrays. Use them as global storage. Faster and lighter and more reliable than Value and Box Containers. Make everything you can into a Background image (not physics and not static/walls). Way less physics checking. If you can do this with things and not need to worry about them again, then you know these things are also suited to being put on another layer. So do that and forget about them. Use broadcast and receive for every single thing you can think of. All the time. This way you can centralise everything and find anything and everything you need in little managers. Animation manager, Sprite Manager, Sound Manager, Creation Manager, etc. Don't update labels frequently. They are unbelievably slow at any size that looks good.

@Aidan-Oxley btw, this is kind of normal for my experiences with hyperPad. I try something, and find something buggy, and then do a couple of restarts, and then move around it. Today's biggest accomplishment is that I figured out I can do this kind of rotation of a tag, so long as I don't do loops with Ease Out Exponential set as the curve type.

@Hamed no, no space. I duplicated the receiver to ensure it was exactly the same.

@Deeeds Yes, I’m stupid. Didn’t look at what I was doing. Erm, maybe this doesn’t work for rotations, but it does for Move to Object, or Rotate to Object.

@iTap-Development I always use set input field for things like this, rather than having a box container value inside the input field. Seems to be more reliable.

@Deeeds yeah it was just off the top of my head...there is probably a better way, but i don’t have anything in mind right now🤷‍♂️

@Hamed In some cases, very rarely, I've seen massive numbers being reported. By massive, I mean those kinds that have "E" in them. Billions, or bigger. Further, I've tried checking both sides of a collision. Both doing the same, reporting zeros, 99% of the time. Sometimes the enormous numbers.

@Aidan-Oxley Yup, got it working.

@Deeeds ok👍