I'm trying to control a physics sprite with a gamepad. I reached a point where I started working on an entirely different part of the game, and suddenly problems, where everything was previously working perfectly, started popping up! If seemingly any "For Each" event was used in combination with my code to change the angle of the physics sprite, the sprite will always try to aim to the right or 0 degrees. It's meant to still remain in the general direction it was facing... not return to 0 degrees.
If I disable the "For Each" code, it works as intended. I thought it was because my original "For Each" contained the player sprite, so I changed it so it was completely disconnected, and the same error occurred. Tried on multiple devices running 216.
Attach a Capx
Description of Capx
Capx shows a very simple game producing the problem I'm having.
Steps to Reproduce Bug
- Play Game with GamePad connected
- Touch a button and move the right stick
- Note that the player sprite will rotate, but always return to 0 degrees when you release the stick
- Close the game, disable the "For Each" event(s), and play the game again
- Note that the player sprite will rotate and will not try to aim back to 0 degrees when the stick is released
The Player sprite will always try to aim towards 0 degrees
The Player sprite should remain towards it's last angle, or spin
- Chrome: (YES)
- FireFox: (YES)
- Internet Explorer: (YES)
Operating System and Service Pack
Windows 7 and Windows 10
Construct 2 Version ID