forked from bartvdbraak/blender
1f43b083a9
This is related to task T29419. Credit also goes to Goran Milovanovic (goran) for proposing an initial fix for this issue. The issue is the current behavior of applyImpulse doesn't match the behavior described in the documentation as instead of a impulse point in world coordinates, it seems to require a coordinate in a local space. Additionally, applyImpulse function isn't consistent with similar functions (applyForce, applyTorque, etc) as it doesn't allow to choose in which space (local or global) the impulse is applied. Now, we have the following function: applyImpulse(point, impulse, local=False) being "point" the point to apply the impulse to (in world or local coordinates). When local is False will have both point and impulse in World space and when local is True will have point and impulse in local space. Reviewers: moguri, dfelinto, brita_ Reviewed By: moguri Differential Revision: https://developer.blender.org/D567 |
||
|---|---|---|
| .. | ||
| blender-org | ||
| epy | ||
| examples | ||
| rst | ||
| rst_from_bmesh_opdefines.py | ||
| sphinx_changelog_gen.py | ||
| sphinx_doc_gen_monkeypatch.py | ||
| sphinx_doc_gen.py | ||
| sphinx_doc_gen.sh | ||