HingeConstraint Active won't enable for client only mechanic

[Galvarino]

Hi everyone,
I am working on a mechanic that rotates using a hinge constraint. I have replicated this mechanic to the client using replicated first, then cloning it on the client exclusively. Because of this, the mechanic exists only on the client, which causes some weird behavior, hence why I’m making this post. I have gotten this to work before in a previous version of the mechanic.

Basically, what are the causes for a hinge constraint to be active? I have two attachments in the same spot and orientation, properly linked to the constraint. The constraint is a child of the anchored part that does not move, and the moving part is properly unanchored. What else am I missing? Is there something weird with the client system I’m using that would break this?

Please let me know if I’m leaving out anything important. I wrote up this post rather quickly.

[SubtotalAnt8185]

There shouldn’t be anything wrong in this case, unless I’m missing something. Can you provide more details?

@Galvarino

replicated this mechanic to the client using replicated first

I recommend ReplicatedStorage instead. Should be functionally identical, unless your script is also in ReplicatedFirst.

[Galvarino]

I’ll give that a try and see if it changes things. Thanks for replying!

[Galvarino]

The hinge is still not active. I’m hoping this is just a simple mistake or something… I checked recently if the parts were sleeping, but they aren’t.

[Galvarino]

I discovered a solution, finallyyyy. Basically, when I replicated the folder of mechanics, I moved it on the client. This was problematic because the server still had ties to the objects. Instead, I am now cloning the folder, creating a new instance that doesn’t exist to the server at all. Thanks for the help Sub!