b10575, on Windows.
The collision shapes of actors already in a game before updating to b10575 (could have happened before, I didn't notice until now) will have red Xs on their fields. The X and Width appear to be correct, but the Y value is set to the entire height of the animation and the Height of the collision box is negated (so removing the minus sign fixes to what it was previously). I can only move the collision shape if I fix the Y/Height values or if I delete and create a new collision shape. In the collision display and in-game the boxes behave properly as they were previously configured.
Steps to reproduce:
1- Open Stencyl on the public build, or any build before b10575
2- Create an actor and add an animation.
3- Close, and open build b10575
4- Open the actor and check the collisions tab.
Once this is triggered, returning to previous builds doesn't fix it. Circle collision shapes are unaffected.
Attached a sample game where I tested this, an image showing the error and my logs, cleared before testing this.
The collision shapes of actors already in a game before updating to b10575 (could have happened before, I didn't notice until now) will have red Xs on their fields. The X and Width appear to be correct, but the Y value is set to the entire height of the animation and the Height of the collision box is negated (so removing the minus sign fixes to what it was previously). I can only move the collision shape if I fix the Y/Height values or if I delete and create a new collision shape. In the collision display and in-game the boxes behave properly as they were previously configured.
Steps to reproduce:
1- Open Stencyl on the public build, or any build before b10575
2- Create an actor and add an animation.
3- Close, and open build b10575
4- Open the actor and check the collisions tab.
Once this is triggered, returning to previous builds doesn't fix it. Circle collision shapes are unaffected.
Attached a sample game where I tested this, an image showing the error and my logs, cleared before testing this.