Bullet Behavior Bug

0 favourites
  • 5 posts
From the Asset Store
This pack contains 10 types of bullet effects, with different shapes and colors.
  • Problem Description

    Setting the bullet speed behaves more like a multiplier than a speed setting..

    Attach a Capx

    https://drive.google.com/file/d/0B_4xfu ... sp=sharing

    Description of Capx

    When setting the bullet speed to something negative, it behaves erratically.

    Steps to Reproduce Bug

    • Open .capX.
    • Run.
    • Click on either button and watch its behavior.

    Observed Result

    When clicking the left arrow, multiple times, the bullet object switches directions, even though I am setting it to the same speed each time...

    Expected Result

    Setting a bullet speed should save as a constant variable, not a multiplier or whatever may be happening with this behavior

    Affected Browsers

    • Chrome: (YES)
    • FireFox: (YES)
    • Internet Explorer: (YES)

    Operating System and Service Pack

    Windows 10 Latest Service pack.

    Construct 2 Version ID


  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • So it's supposed to go negative speed?

    Whats happening is that the behavior is designed to go by angles. Speed does not determine its direction.

    As a default when you set the speed to a negative value it tells it to go the opposite direction.

    When it goes the opposite direction it must have a positive speed, so that's what it uses.

    Then when you tell it to go - speed it again thinks it's supposed to go the opposite direction.

  • I see, I thought the variable would work like any other, negative speed would mean going in reverse of its current angle, as it already does, then setting it again to the exact same negative speed would keep it going in the same direction..like a constant....

  • The Bullet behavior treats a "set speed" action as "calculate current angle then set magnitude of current movement at that angle". This has the effect of treating a negative speed as "point in the opposite direction then set a positive speed".

    I agree it's a bit strange but I'm concerned about changing this since it could break existing projects that use that feature. It's also a pretty minor quirk IMO. So although the issue is probably valid, closing as won't fix.

  • Ashley Thanks for the honest feedback..

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)