hyperPad Forum

Try double tapping on the screen to reset the camera position. This should allow you to drag the screen again.

However, if your array is going to have variable amount of elements, then you will have to use a Loop to iterate through the array. First, you have a Value behavior and before looping, you make it empty so it starts with nothing in the value. Then in the loop, you would combine the value with the current element of the iteration. After the loop, the value behavior will have all the elements, separated by spaces.

You can use a Text Operation behavior and use the Text with Format mode. In the input text, you can enter a format. Every instance of %s is replaced with an element - so you can have your input text be %s %s %s and those would automatically be populated with one element each, showing the first 3 elements of the array.

We are fixing a bunch of scene-related bugs. But there are things you can check now to see if you can fix it.

1. Check your Load Scene behaviors - if they have refresh disabled, behaviors in your GUI objects and global behaviors don't reset. Try enabling refresh to see if that fixes your issue.
2. Right now, the On Scene Start event in Frame Event behaviors are pretty buggy and actually trigger in a scene when they are preloaded - this might interfere with boot up logic if you're using this feature. This has been fixed and it will be live in the next update.
3. Behaviors in UI and mirrored objects don't retrigger unless refresh is enabled in Load Scene behaviors.

If possible, can you share what logic is failing to run when switching scenes? Any screenshots of your code, explanations and videos will be helpful in fixing this bug.

I think you can benefit from using a wall object. You can apply a velocity on it using Set Velocity and it will continue moving forever.

Now to make it move in a specific direction, you do need to use a bit of math. The Set Velocity behavior has x and y input fields. What do you plug into those?

Calculate x by using the Sine function. Sine takes in an angle.
Calculate y by using the Cosine function. Cosine takes in an angle.

Here I take an angle (substitute it with whatever angle you want) and plug it into Math Function behaviors.

Now I take the outputs of the Math Function behaviors, and multiply them. The bigger the number you multiply with, the faster the object will travel.

Finally, plug the results of those behaviors into Set Velocity.

In conclusion, given an angle and speed you want an object to travel, you can calculate the x and y velocity to apply to a wall object with these equations:

x = Sine(angle) * speed
y = Cosine(angle) * speed

Here's an example on how to use the Boolean behaviors.
The Text Operation behavior can also work this way if you wanted to check the prefix of the behavior name instead or something like that.

In the Hit by Bullet behavior, you can leave the behavior blank to handle all bullets. The behavior outputs shoot_behavior, which is the name of the behavior that the bullet comes from. You can check the name of the behavior to see which behavior the bullet came from, and from there you could handle logic differently depending on what type of bullet hit you. You are also given shooter which is the object the bullet originated from. This also works for spawned objects - it will give the same name when the same shoot behavior is used across different spawned objects (in other words, no additional work is needed for spawned enemies).

If you named your shoot behaviors appropriately, it will be easy to distinguish between different types of bullets. Even if you have multiple shoot behaviors with similar names, you can use a Boolean behavior to check if the name contains a specific text. So something like "Fire" and "Fire1" will still work. The Boolean behavior outputs 0 (false) or 1 (true), and you can use an If behavior to only trigger specific logic when the output is 1.

Users are reporting this issue on Discord too. Team is currently looking into this.

I think the hardest part here is getting the x and y values to move the object based on the angle. I guess we can add a shorthand way of doing that at some point.

The shooting logic is located in the Joystick object. I'll briefly explain how it works.

1. Joystick Input triggers while using the joystick.
2. Debounce adds a cooldown so it doesn't shoot every frame. It limits how often its child behaviors are executed. In this case, it is set to 0.3s so you can only shoot one bullet every 0.3 seconds.
3. It spawns an object (the projectile), then it sets the spawned object's rotation to the angle from the Joystick Input.
4. We perform sine and cosine Math Functions on the angle to get the horizontal and vertical components respectively. These output a value between -1 and 1.
5. These components are multiplied because -1 and 1 is too small of a range. You'd probably want your projectiles to travel further than that.
6. Move By moves the spawned object by the multiplied values.

In conclusion, while holding the joystick, the player will shoot a bullet every 0.3 seconds angled at where the joystick is. Depending on the angle, the projectile moves in a particular direction.

In the spawned object, you can add whatever logic you want. In this case, I made the projectiles emit particles and destroy themselves when colliding with an object with the "Wall" tag.

Here is the project!
https://bit.ly/4x0FdQP

The update has not released yet, so you won't see this z order setting yet.

I'll quickly whip up a demo project where you can shoot objects (instead of bullets) at whatever angle you please. You can customize the behavior of the objects if you like.

Doing good! Nice to see you using this as a way to collaborate with others. Can't wait to see what you guys make! :)

We have a Discord server where you can chat with others if you're looking for quicker response times: https://discord.gg/RpXHJXq

1. You need to save and load the array.
2. When loading the array, you must reapply the tags.

Let's start with saving and loading.
After modifying the array (it should now contain all the tags you need), you can trigger the Modify Save File behavior and save the entire array. When the scene starts, you can trigger Load from Save File with the same key you used in the modify save file behavior.

Now you can load the array, but you must add the tags back, otherwise all the work you did for saving and loading was for nothing. Grab the loaded value from the load from save file behavior, and plug it into the Modify Tag behavior. There is an option to set the tags of the object (or append tags) which takes in an array.

A better approach would be to utilize the screen behaviors to move between images. This allows things to persist instead of the entire scene resetting every time.

1. App hasn't been updated yet.
2. The Z order property is editable in the shoot behavior itself.
3. I'm guessing you mean to have bullets ignore collisions of some objects - not possible at the moment. Treating bullets like objects would bring a lot of performance overhead. It would be a lot better to use actual objects instead since you can define custom behavior logic for each bullet.

Also, good news! This bug has been fixed. An object shooting a bullet will still be able to shoot bullets when switching layers. We've also added the ability to adjust the Z order of the bullets.

I'm assuming the screenshot you provided is from a tutorial.

What this is doing is getting the rotation of an object, calculating the x and y values to use based on the rotation, and then applying a force using those values. Effectively, this applies a force on a spawned object (presumably a bullet, a physics object) in the direction of the object.

Normalized x direction is a Math Function behavior that is using Cosine.
Normalized y direction is a Math Function behavior that is using Sine.

However, I see that the names are mixed up in the screenshot. So Sine is used for the x and Cosine is used for the y.

The multiplier is self-explanatory - you can adjust the power that is applied on the force. Larger multiplier means stronger force. It looks like it's using a health bar to adjust the power.

After some testing, I noticed I made some mistakes. You want to divide angle by 360 divided by how ever many angles you have. In my example, I used 8 since I have 8 angles. Then you round it - you'll get a range from -4 to 4. Range changes depending on how many angles you have. 0 is up, 1 is top right, etc. Note that when it reaches -4, it goes to 4 but it's still pointing in the same direction. It's just that the angle becomes negative when the joystick ball is pointing to the left. Here are screenshots that should help.