Bug Issue: Multiple collision boxes report wrong collision side


Pages: 1

Luyren

  • Master Stencyler
  • *
November 10, 2015, 12:13:30 pm
b8789

Happens on: Windows export, Flash

Scenario: actor has an animation with a solid collision box of one group, and a sensor collision box of another group.

Top collisions of this actor with a tile are registering bottom collisions. If the sensor collision box is higher than the solid collision box (meaning the sensor hits a tile before the solid collision), this behavior is consistent, registering a top collision followed by bottom collisions.

If both solid and sensor hit the tile at the same time, this doesn't happen.  A solo sensor collision box doesn't register the specific side of a collision, so something is definitely wrong.

Sample game: Arrows to move, Z to jump, click to reset.
If you jump and hit the tiles, the console will print "top", followed by a series of "bottom", as shown in the attached image.


New attachment added by Luyren - November 10, 2015, 12:13:57 pm


New attachment added by Luyren - November 10, 2015, 12:14:10 pm


Issue updated by rob1221 - April 25, 2017, 07:08:00 am
  • Status changed from New to Confirmed


Issue updated by Justin - February 04, 2018, 02:30:31 pm
  • Tags added: 3.5 NP


rob1221

  • Master Stencyler
  • *
March 25, 2018, 07:47:21 am
Fixed in b9826.
  • Status changed from Confirmed to Resolved
  • Issue Assigned from (none) to rob1221
  • Tags removed: 3.5 NP


Luyren

  • Master Stencyler
  • *
March 25, 2018, 07:47:02 pm
Fix confirmed in b9827.


Pages: 1

Details

  • Reported
    November 10, 2015, 12:13:30 pm
  • Updated
    March 25, 2018, 07:47:02 pm

  • View Status
    Public
  • Type
    Bug
  • Status
    Resolved
  • Priority
    Normal
  • Version
    Stencyl 3.4, 3.4.0 beta
  • Fixed in
    (none)
  • Assigned to
    rob1221
  • Category
    Collision Groups

Tags


Attachments

* test again.stencyl (383.92 kB - downloaded 139 times.)

* bug.png (89.18 kB, 1366x490 - viewed 303 times.)