brunopalermo's Recent Forum Activity

  • For triggered events like "on button pressed", I'm afraid you need to create 4 copies of such events. But don't do anything inside these events, move all your logic to a function, which will take gamepad ID and button code as parameters:

    Hey dop2000!

    I've never actually used Gamepad, but, couldn't he just have an "or block" with all "any button" events?

    On Gamepad 0 any button pressed 
or
On Gamepad 1 any button pressed 
or
On Gamepad 2 any button pressed 
or
On Gamepad 3 any button pressed 

     Function Call "ButtonPressed" (Gamepad.GamepadID, Gamepad.lastButton(Gamepad.GamepadID))
[/code:3cb9xmrx]

Not even sure if that makes sense, actually, but it got me curious... 

Cheers!

  • Share the capx and I'll take a look at it...

  • Not an image. Save your project as a single file and upload it to dropbox or some similar service, then share the link here, so people can take a look at it...

  • There are many ways to solve this, depending on how, exactly, is your code. It would be easier if I could see the capx. Can you share it?

  • Could you share a capx? You're probably setting the animation inside a "is down" event, which makes Construct set the animation every tick the keys are down, so it's always going back to the first frame...

  • Hey robertg92!

    It's just like dop2000 mentioned above, but, since you want it to respond to dragging, you'd have to give the sprite the drag behavior and use an isDragging event, instead of Every tick. Here's a capx:

    https://www.dropbox.com/s/34p9qj7gg4qw4 ... .capx?dl=0

    Hope it helps. Cheers!

  • You're probably not telling the host correctly about who's moving who. Could you share the capx?

  • Just a reminder... As a best practice, if there's a physics equation that does something, don't try to reinvent it. Just use it. Most types of movement are already covered by physics (the science, not the behavior), you just have to implement the equations.

  • Event 6

  • Exactly.

  • Hey —!

    Is there a reason you're setting the angle inside a "Every tick" event? Do you understand that, in this case you are re-setting the angle every tick, for every Shot, even when the angle is already set? Also, the action to set the Shot's size repeats itself a lot.

    Maybe you should consider a "On Created" event for the Shots, which would do all this (set initial size and set angle), which would make it happen imediately on creation, and leave the "Every tick" event just for adjusting the size dynamically.

    Hope it helps! Cheer!

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Ok I did it. I had problems with IP, because game is in port 81, not 80 <img src="{SMILIES_PATH}/icon_e_wink.gif" alt=";-)" title="Wink">

    You can change it on Construct 2 settings.

    Or you may specify the port on your mobile phone url by typing:

    http://here.goes.the.ip:port

brunopalermo's avatar

brunopalermo

Member since 7 Jun, 2013

Twitter
brunopalermo has 6 followers

Connect with brunopalermo

Trophy Case

  • 11-Year Club
  • Coach One of your tutorials has over 1,000 readers
  • RTFM Read the fabulous manual
  • Email Verified

Progress

14/44
How to earn trophies