As others have already mentioned here, I am super happy that backspace can now be ignored when using tool instances - it was worth making some noise about that when tools were last updated!
Creating a custom tool system is pretty hard. Tool instances already provide a great wealth of API and internal code to make them work, as well as how tied they are to the engine, but this one thing made me move towards putting the effort to build those custom systems instead. It felt absurd to build an entire system just to void out a single behaviour.
It’s also nice that the change can be made naturally so it’s not disruptive to experiences that still wish to retain that behaviour and works better for other experiences that otherwise create custom backpacks but want the benefits of the Tool instance. Much appreciated for that one.
Final thing is a thank you for removing the deprecation off of DevEnableMouseLock and EnableMouseLockOption. Someone did a really good in-depth analysis in a previous announcement thread as to why the proposed alternatives were inadequate.
I’m not sure what was changed, either. I visited my baseplate yesterday with Nexus VR Character Model and I was able to tilt my head and look up and down. I don’t think that module has been updated in a while (sadly) but yet it still works.
I noticed there’s a new property on the Camera instance that must supposedly enable rolling and pitch on VR cameras, but again, I assume that property was the default, false, when I was testing.
I thought we would be able to set an Unit Vector which would serve as a multiplier to the current MaxVelocity property, where the default would be Vector3.new(1, 1, 1).
This feature works exactly like the old BodyPosition and to this day I still don’t know how to control these huge numbers to maintain a PROPER LINEAR VELOCITY.
If I am missing something here, please let me know; else let me know how I can maintain a linear velocity since I don’t want my objects to move as fast as possible to the goal and then slow down to reach it.
