Problem Description
A collision is being falsely reported on start of layout when I immediately restart a layout due to a collision
Attach a Capx
Got a SQL error when attaching a capx. Here's a link to my capx: https://www.dropbox.com/s/8wgrs1vw3rko1 ... .capx?dl=0
Description of Capx
This capx gives you control of a "Player" object with Platform behavior. The "Player" can interact with 3 objects that have the "Solid" behavior:
- Normal - Nothing special. Normal solid.
- Hazard - A hazard that will cause the player to "die". As of right now, death simply results in an immediate restart of layout. I assume this is a perfectly reasonable way to handle a quick restart.
- SolidTrigger - This solid will "light up" the first time it's touched. This happens to be an easy way to communicate a collision in this demo.
There are two layouts. One that easily communicates the bug when you follow the reproduction steps and one that showcases normal interaction
Steps to Reproduce Bug
Scenario A
- Start with the "BUG - Prelit Platform" layout
- Drop down the right side of the starting platform.
- The player should land on a Hazard directly above the leftmost SolidTrigger (this SolidTrigger may light up)
- The layout will immediately restart
Scenario B
- Start with the "BUG - Prelit Platform" layout
- Run full speed to the right
- The player should land on a Hazard directly above the second SolidTrigger from the left (this SolidTrigger may light up)
- The layout will immediately restart
Observed Result
Scenario A - The second SolidTrigger from the left starts as lit when the layout restarts
Scenario B - The leftmost SolidTrigger starts as lit when the layout restarts
Expected Result
I expect all the SolidTriggers to start as un-lit when a layout restarts.
Affected Browsers
- Chrome: YES (Scenario B)
- FireFox: YES (Scenario B)
- Internet Explorer: YES (Scenario A & B)
Operating System and Service Pack
Windows 8.1
Construct 2 Version ID
r200 64-bit