Godot Engine – Multi-platform 2D and 3D game engine https://godotengine.org https://git.neuromancer.sk/godot.git/atom/servers/physics_2d?h=2.1.4-stable 2017-08-27T12:11:45Z 2017-08-27T12:11:45Z Rémi Verschelde 2017-08-27T12:11:45Z urn:sha1:9d598833d2e284b57458ade9d27b9433588339ef 2017-07-05T17:38:11Z Pedro J. Estébanez 2017-07-05T17:28:23Z urn:sha1:a30dd8494c9347d7f85216120e548c0b3f2514c7 This affected both 2D & 3D physics and was a regression introduced by my physics mega-fix (#8999). 2017-06-25T09:14:31Z Rémi Verschelde 2017-06-25T09:14:31Z urn:sha1:5e7fb570e8e45222dd676359e246732c24c92d49 Fix one-way collision detection (2.1) 2017-06-19T10:02:50Z Pedro J. Estébanez 2017-05-30T16:56:43Z urn:sha1:3e5e8b6c9e9bb3ead3f127ff2d656a18c974a2a3 - Use `NOTIFICATION_ENTER`/`EXIT_WORLD` for `Area` (intead of `*_TREE`). - Now both bodies' and areas' constraints are cleaned up. - And now also that happens as soon as the space is set to null (i.e., when exiting the tree) instead of only at freeing time. - When clearing constraints, the loop goes on to the next if the current is already released, instead of breaking. - When one has been already released, no error is shown from now on, as it's something expected, since a pair (our kind of constraint of interest) can be freed by any of its involved collision objects and the other will try again. - Implement index shifting (or marking as -1) for shapes indices in collision pairs shapes are removed. - Standarize behavior of bodies and areas so that anything that invalidates a given pair gives the same result (collision mask, actual collision, etc); for instance, triggering area enter/exit signals. - Add missing member initializations. - Extend the new-space-equals-area/body-current-space test to every case. - Fix 3D ray-casts early accepting Areas (skipping the mask check). - Fix unpairing of large elements (2D's `BroadPhase2DHashGrid`). Some of these prevent random crashes caused by constraints with dangling pointers to involved objects. Fixes #8856. Fixes #7589. Fixes #6676. And maybe others. 2017-05-11T00:45:48Z Pedro J. Estébanez 2017-05-11T00:13:33Z urn:sha1:5e4216fd497e8a4b1d4d0b0d204f2cb27f68f663 Also, change the explanation of the one-way collision direction in the docs to reflect how it is actually used by the engine and clear up the usage of the "max depth" property. 2017-04-07T22:45:24Z Rémi Verschelde 2017-04-07T22:45:00Z urn:sha1:e9b045d9e572ff7a211b604d6400f35003bae327 2017-03-18T23:36:26Z Rémi Verschelde 2017-03-18T23:36:26Z urn:sha1:f8db8a3faa30b71dca33ced38be16d3f93f43e8a Applies the clang-format style to the 2.1 branch as done for master in 5dbf1809c6e3e905b94b8764e99491e608122261. 2017-03-18T20:14:33Z Rémi Verschelde 2017-01-14T17:03:38Z urn:sha1:dbf013757658ad48bb61242ed69ad4145a946863 (cherry picked from commit f44ee891beaad397481dd88da41cb80e6539774f) 2017-03-06T04:10:15Z Pedro J. Estébanez 2017-03-06T04:08:12Z urn:sha1:95a5d9e617847ea4b8f6f0c6b469e1e2ac9d287b Got part of the fix from 5fc084c28e912c54bf64645df3e6cf2cd2c30be6 Added an engine setting to enable the fix (physics_2d/motion_fix_enabled) which is false by default so the default behavior is the same as always Added motion methods with a from parameter, the same as 3.0 does 2017-01-12T18:15:30Z Rémi Verschelde 2017-01-01T21:01:57Z urn:sha1:d8223ffa75f7028bb104001e7195233f335556f2 That year should bring the long-awaited OpenGL ES 3.0 compatible renderer with state-of-the-art rendering techniques tuned to work as low as middle end handheld devices - without compromising with the possibilities given for higher end desktop games of course. Great times ahead for the Godot community and the gamers that will play our games! (cherry picked from commit c7bc44d5ad9aae4902280012f7654e2318cd910e)