Added support for kv in position actuators in Unity, missing since 3.1.0 . At first I just reused the Kv property of the velocity actuators however that had some undesired quirks, such as the default value being 1 instead of 0 for position actuators, or that changing the parameter value when editing the actuator as a velocity actuator influenced the position actuator. For this reason, I seemingly redundantly declared the Kvp parameter, let me know if you have any issues or suggestions for this issue.
I'm also interested on any potential suggestions for the intvelocity actuators which are also missing at the moment, but have their own kp and kv. I'm considering not tracking all these parameters in MjActuator and its Editor at all in the first place, and have sibling classes for each different actuator type, drawing their own Editor and supplying their MJCF parsing/conversion separately.
Added support for
kv
in position actuators in Unity, missing since 3.1.0 . At first I just reused theKv
property of the velocity actuators however that had some undesired quirks, such as the default value being 1 instead of 0 for position actuators, or that changing the parameter value when editing the actuator as a velocity actuator influenced the position actuator. For this reason, I seemingly redundantly declared theKvp
parameter, let me know if you have any issues or suggestions for this issue.I'm also interested on any potential suggestions for the
intvelocity
actuators which are also missing at the moment, but have their ownkp
andkv
. I'm considering not tracking all these parameters in MjActuator and its Editor at all in the first place, and have sibling classes for each different actuator type, drawing their own Editor and supplying their MJCF parsing/conversion separately.