oosyrag's Forum Posts

  • The simplest way is to use instance variables.

    Arrays are also a good choice and could be more flexible and easier to work with when importing/exporting, but also more complex and prone to logic bugs.

    There are a lot of ways to do it, as you mentioned with arrays, general variables, instance variables, and dictionaries, and it really depends on what makes the most sense for you and what you are most comfortable with. This will result in the least problems down the line. Keep it as simple as possible while being able to do everything you need to do.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • You do not have permission to view this post

  • You do not have permission to view this post

  • You do not have permission to view this post

  • You do not have permission to view this post

  • You'll need to clone the objects you want to change as a separate object, then place the new one on your second layout.

    To remove the original object from your second layout only and not the first, delete it from the layout view, not the object/project bar on the right.

    Also you can filter your objects bar to only show objects that exist on the current layout by right clicking - filter objects.

    Objects existing globally across all your layouts can be very useful, but in your case if you want your layouts to have different objects, you should actually create different objects. You can make the new ones based on the old ones by cloning objects.

    Here are the relevant manual entries:

    https://www.scirra.com/manual/39/project-bar

    https://www.scirra.com/manual/41/object-bar

    https://www.scirra.com/manual/43/layout-view

  • I have no idea why the fullscreen isn't working then, sorry... maybe someone else can chime in.

  • I have no ideas based on that, it should work fine. Maybe there is something else, won't know without testing your project.

  • You can activate and disable event groups. Put the events that are responsible for firing in a group, and have it disabled by default. When the player presses start, enable that group.

    https://www.scirra.com/manual/80/groups

  • Basically I want to make sure your gamepad is actually connected and buttons are registering.

    In debug mode, on the bottom left look for the game pad object. Click it and you'll see a field that says "Last button" on the right. Now when you press buttons on your game pad, that should change. If it doesn't, that means your game pad is not sending any signals to the program, which would explain why on button pressed does not work.

    If it does change, then I'll have to think of another reason

    Edit: I meant trigger as in shoulder buttons on some game pads.

  • Instead of scroll to player.x, player.y, only scroll to player.x, and have y constant.

    Or add a condition to check that when player is jumping, then the scroll only scrolls to the x.

    There are a lot of little nuances people don't realize with platformer camera behavior! You'll need to add the exceptions and logic yourself for each situation.

  • How is your camera "moving"? Is it with the scroll to action, or are you moving the objects in your project around?

    Are you sure your HUD objects and backgrounds are on the correct layer with parallax 0? You can check in the debugger

  • That's a good plan.

    You can use an array to store your "waypoints" by using the push back action - this will add new values to the back of the array.

    Those waypoints will be in order in the array, so your object can get its move to locations from the array one waypoint at a time in order.

    https://www.scirra.com/manual/108/array

    Edit: In case you aren't familiar with arrays, you can just think of them as spreadsheets with cells you can write and get data from. Each cell is like a variable.

  • Can you confirm in debug mode that your gamepad is connected and registering inputs?

    Are you using triggers as buttons? Sometimes those are treated as analog axes rather than buttons.

  • https://www.scirra.com/manual/85/layers

    Set layer parrallax to 0 for your static layers.