A typical wheel on a car setup, as of today.
Currently, working with constraints that have two attachments is very fragile.
If you move, resize, or rotate either part in this setup (Wheel or Car), your whole physics rig no longer works, and you have to go rummage around and copy the worldCframe data from A0 to A1 to make it work again after every edit.
What I propose is the following addition to two-attachment constraints, in that you allow the Attachment1 parameter to also be any basepart
This would look like this:
Proposed change
In this newly proposed setup A1 goes away, and you point the Attachment1 parameter of Hinge directly at Car
The A0 instance would become the relative attachment point between the Wheel and the Car.
What this means is:
- You can move, resize, rotate Wheel and not have to adjust the attachments
- You can move, resize, rotate Car and not have to adjust the attachments
- Wheel can become self contained - all the instances that affect it are within its own hierarchy (A0 and Hinge)
And then - the prestige! Watch this:
If I want to add a second wheel, all I have to do is clone the first one and move it to where it goes!
With this setup, roblox physics would become a lot more intuitive and robust - things that “look right” would be “be right” a lot more often, and open up the ability to resize and explore and play with physics much more without things constantly breaking.
Thanks 