The DirectionalTransformDrive would not work if it was nested to another interactable object and the MoveToTargetValue was true because the TransformPropertyApplier would always work in world space which meant the drive was never calculating the correct position. Now it's possible to work in local space which resolves this issue. The directional and rotational drive also had an issue where they would re-enable the rigidbody kinematic state when ungrabbed due to the default behaviour of the Interactable. This has been configured to never emit the rigidbody kinematic change events for either drive as they should not be changing the kinematic states. The Interactable Consumer Rigidbody can also now be null and the relevant code that uses it will perform a null check. This won't work for nested interactables because there will be no collision catch rigidbody, however if a non-nested interactable is required without a kinematic rigidbody, then this should allow for that.
Latest commit 307ae81
Apr 8, 2019
|Type||Name||Latest commit message||Commit time|
|Failed to load latest commit information.|