Motor6d animations freeze on assemblies that the client doesn't have network ownership over

Bug Reports Engine Bugs
#1

Based on this post: Motor6Ds failing to update when attached to instances without network ownership

Basically, all motor6d animations (be it setting desired angle, or using an animator) fail to render/update on assemblies you don’t have network ownership over. on this game: Steam & Steel - Roblox
I don’t know what I’m doing with the motor6ds on at this place, but it doesn’t matter if they’re client side or server side motor6d, they just refuse to update until you get network ownership.


this issue tends to get worse as player count increases on the server.

Expected behavior

I expect that the Motors, Motor6ds, and humanoid animations work as intended, updating their cframe regardless of network ownership.

6 Likes
#2

Thanks for the report. We’ll follow up when we have an update for you.

1 Like
#3

UPDATE: This extends to serverside created Motor6Ds that are changed by the server.

it starts working again once network ownership is gained by the person viewing the cars.

#4

ok, at this point, it has got to be something wrong with how i’m implimenting the animations.

I’m playing all the animations from my client, and it just… freezes.

The particles and sounds are playing correctly, so keyframes are being reached. but… no movement.

#5

update: So, to add to the wackyness.

the animations start working just fine if you have one mech in physical contact with another

#6

Hi GregTame,

Are you still seeing this issue?
I’m a little confused by the videos on what’s going wrong - would you be able to provide a repro file and repro steps?

Best,
M0bsterLobster

1 Like
#7

I can confirm that this is still somewhat an issue. Once NetworkOwnership transfers to my client, the motors stop functioning.

Important to note that I’m animating the enemy by setting the DesiredAngles of each motor, and not through an animation track.

#8

Here’s some further insight, keep in mind I have no scripts in the “Infected Noob” model, the only script in workspace is one which will set the network owner to the player who clicks on it.

From what I can tell, it seems like the Motor will only update on the network who currently
is owning it, and the DesiredAngle will not replicate to others until updated.

[EDIT]
While yes, this is most likely a server security feature, the fact that even when the server calls updates to the motors they do not replicate when a client owns them is extremely annoying