New this build: a physics engine update, some bug fixes, and a few performance improvements.
In other news note that Construct 3 has been announced and you can stay up to date with the latest news at Construct3.com. While Construct 3 is a long way off, note that a consequence of its development is that the Construct 2 update cycle will slow down.
Physics engine update
We've finally been able to update the asm.js version of the physics engine to the latest version (v2.3.1), and we're very pleased to be able to add back in the 'disable collisions' feature, which was the sole feature missing from the asm.js version. This means asm.js physics should now be compatible with the box2dweb version and all games should be able to switch over to it. If you have a game using Physics, please make sure the 'Physics engine' project property is set to asm.js and let us know if there are any problems.
If there are no issues with the asm.js version, then in the next beta we plan to remove both other physics engines (box2dweb and CocoonJS) and only use asm.js physics. CocoonJS is no longer officially supported, and box2dweb is much slower and prone to creating loads of garbage. One of our benchmarks shows asm.js physics is a whole 3x faster than box2dweb, and since it now supports all the features box2dweb does, there isn't much reason to keep that version around. So please make sure you're using the asm.js engine, test it carefully, and report any issues you find!