I’m currently scripting a simple airzone where it will push a player towards where the zone is currently facing. I’m pretty satisfied with the current output. I used BodyVelocity to push players around the zone but theres a problem, the BodyVelocity are inconsisnent depending where the zone faces. Specifically, the BodyVelocitys with negative values seems to have more force than the BodyVelocitys with positive values. I want to make sure all bodyvelocity’s are consistent no matter what direction they are facing.
Most of people that still use the old Body Velocity are beginners that follow old Youtute tutorials without knowing that this is a deprecated instance, and the rest of these people are just lazy to try out the new instance as it is different and a bit more complex to manipulate correctly so they prefer to keep using the old one.
Using deprecated instances is absolutely not recommended at all, each new Studio update have the possibility to break some features of these deprecated instances, and if it happen, Roblox isn’t going to fix anything as these shouldn’t be used anymore.
The best thing people can do is to start using the new instance or find another method to do what they are attempting to do.
Genuinely curious on some examples of latency you are referring to. I’m currently using a few LinearVelocities for my movement and I have no issues with it whatsoever.
Idk it’s really smooth for me in movement systems, but I’ve heard of cases where people were trying to make knockback using them and it was laggy, maybe its a server thing but there are certain cases where you cant use the linear forces
It doesn’t matter if they aren’t removed. It’s still unreliable. They won’t be updated, so new separate Roblox updates could affect their functionality. As you can see it clearly states in this documentation that they should not be used for further use.
If people stopped using them so frequently, maybe they would have already been removed by now. The purpose of deprecation is to give people time to migrate over to new features.
Unfortunately I will have to repeat myself. BodyVelocity was removed for a reason, even in the original post it’s been reported as inconsistent, which isn’t anyone’s fault but OP’s. They should not be using this in new code.
People are recommending BodyVelocity because they are more familiar with it. I’ve heard it been said that it is impossible to use LinearVelocities WITH gravity, but that’s not true. Just using ForceLimitMode set to PerAxis solves the problem. Soon enough LinearVelocity will be up to par with BodyVelocity, Roblox is just taking a while. Who knows, maybe it already is, people just aren’t trying hard enough.
you quite literally just admitted that right now bodyvelocity is better and we should use something inferior while we wait for it to become superior, gravity isn’t even the issue here
I never said it wasn’t. It’s just unreliable. Don’t use it, it’s not going to improve anymore than what it is now. But LinearVelocity will. That’s why OP is having problems. You cannot complain when you’ve already been warned. Twice.
Soon, it will be removed, so you’ll have to use a substitute anyways.
no, it wont lol, roblox won’t do something that will instantly break multiple older games, plus I know big games that use bodyvelocity instead of linears
what about old games that aren’t being maintained but are still fun? those will be affected, plus, I don’t remember any instances where roblox actually removed a deprecated feature
