But… body movers incorporate CFrames and vector quantities as well? Body movers are practical and appropriate in a scenario where you need hovering.
Body mover API does not “change all the time”, not sure where you got this information from.
Most of these comments sound like some kind of unsubstantiated bias against body movers due to lack of understanding of how to use them.
And, for the third time, I fail to see what you mean by calling CFrame a solution. It’s a data type, it’s used in methods that support CFrame arguments (i.e. tweening to a specified CFrame goal). CFrame itself is not a solution.
I’m calling it a data type because that’s literally what it is. As for APIs that support CFrame arguments, obviously you’re going to need to feed a CFrame value into it. That’s a required parameter. It’s the same thing like passing a string to Instance.new, that string being the name of a class.
Yes, the methods that support it are available but they aren’t proper solutions. This is going extremely off tangent and is not related to OP’s question about how to make hover cars.
Forces are actually relevant to achieving a hover effect and have been one of the best ways to do so for the longest of time. CFrame appropriately interacts with the physics engine and achieves the desired end effect. They’ve been used in jetpacks (hovering), as a simple example.
No? You don’t need to stack them. Don’t understand what you mean either by “unnecessary hierarchy”. Body movers don’t need to be loaded, only replicated upon first load. It’s not like they’re assets.
Where in this do you see “whole functionalty related to object movement”? Just because something has an instance, doesn’t necessarily mean loading is involved. Replication and loading are two different matters altogether. CFrame data types may have the ability to be applied to methods to achieve methods but that isn’t necessarily appropriate for this scenario. That’s just reinventing the wheel for where body movers exist.
You still aren’t explaining how. Enough chassis and hover items around Roblox and the DevForum use constraints and (constraint) body movers, not “CFrame”. How do they make sense? They honestly really don’t - there’s no point in trying to develop your own movement algorithm or pseudo physics engine when the backend engine is already there and body movers help you perfectly fine with this issue.
Body movers are not restricted. I don’t know what basis you’re working off of when you say that body movers give lesser control over CFrames, this is objectively untrue. This can be proven by enough experimentation and usage.
Why would you use CFrames when there’s SpringConstraints? That’s an example. CFrames are not required in everything involving movement. I don’t know where you’re getting this information from, but it’s not relevant at all.
The physics engine runs on the backend which is comparatively much faster than a full Lua implement of a physics engine, which you can’t even accomplish on Roblox. Even then, this is irrelevant. It doesn’t solve the problem nor does it speak anything about why you think a data type is a better solution than an object meant for these kinds of use cases.
Unsubstantiated comment. Just because you don’t use them for whatever reason, doesn’t mean others don’t hold value in them.
Body movers don’t have any less accessibility.
A good majority of your responses are unsubstantiated biases against body movers or completely irrelevant mentions. Please stop getting off tangent and don’t propagate false facts.
That depends on whether it’s appropriate or not for the scenario. RemoteEvents only have a single trip to make for sending the signal to the other environment without depending on any round trip response back. As it relates to a hotkey for movement, RemoteEvents are far more appropriate. That being said, if you just give network ownership of the whole hover car to the client, then there’s no need for remotes at all.
RemoteFunctions are not appropriate for this use case because you do not need a response back from the client/server and I do not believe they send to the server/client faster, as that’s entirely dependant on the client’s latency however I may be wrong.
