Recent Update has broken/changed how welds work with large amounts of parts

[JKVette]

I have a large body of moving parts that is cframed using the :SetPrimaryPartCFrame() method. It has worked just fine for months up until an update some time this week. A lot of the parts are welded together but they are all non collideable. I am not sure if its the large amount of parts welded together or if it is the :SetPrimaryPartCFrame itself.

[inHeadspace (vee)]

Try just setting model.PrimaryPart.CFrame = CF. It’s an inefficient workaround but it’s still something. You could also use a class changer to change welds to Motor6Ds

[JKVette]

I might try to change them to motor6d thanks for the suggestion

[ContextLost]

Your statement is a big vague so I’m not sure what you mean. Broken how so?

Can you provide a minimal place file that reproduces this? If you can provide a repro I’d be happy to investigate.

I did make a change to how the CFrame setter behaves recently. The new behavior should be more straightforward than the old one, but it is a change that could be affecting you.

[Live] Change to Part.CFrame Setter Behavior

NOW LIVE This change was enabled on September 10th at 3:05 PM PST. It should take effect within 10 minutes on servers and upon restart for clients and studio. Original Post We are planning to make some behavior changes to the BasePart.CFrame setter in the near future. If your game uses the CFrame property you should read this. The value returned by the CFrame getter is unchanged. Only the behavior of assigning to this property is changing. We’re planning to enable this change globally on Sept…

[ContextLost]

I’d also personally recommend against using Motor6Ds for rigidly welding parts together if you’re not animating them.

They have more overhead for replication and at runtime than Welds do. Motor6Ds have angles that are sent over the network and they update every frame, unlike other Welds that have no passive overhead. Worth it if you’re animating them as intended, but not worth it as a weld replacement.

[JKVette]

Sorry for being vague. I have a giant 8 legged robot that is made up of 700 parts. The legs are all welded together because they are animated. The upper half is anchored. I have a basepart that is the primary part of the entire model that I cframe to simulate movement of the robot using :SetPrimaryPartCFrame(). The upper half of the model is anchored. It used to work but now when i try to move the entire model the game overloads and eventually crashes in the same way that happens when you forget a wait() in a while loop.

[JKVette]

At 9 a.m. central time when I was trying to fix this it was crashing but now it is working as intended again.

[ContextLost]

Interesting. I enabled a change for cframe replication that might have affected this in that time frame.

If it’s ok with you, can you DM me and send me the place file so I can test it without that change and figure out why it was crashing?

[JKVette]

DMed