Constraint objects will not function correctly because Workspace.PGSPhysicsSolverEnabled is false

[MapleMarvel]

This warning just started popping up:

Constraint objects will not function correctly because Workspace.PGSPhysicsSolverEnabled is false

To replicate, add a Part to your workspace, and then add a constraint into that part, such as a AlignPosition. Then hit Play.

I just want to be sure that I can use the constraints (AlignPosition, AlignOrientation, …) and body movers (BodyGryo, etc), and am not sure if this warning message applies.

[Edited: corrected nomenclature per buildthomas suggestion!]

[buildthomas]

FYI, body mover objects are the family of BodyGyro, BodyVelocity, etc. Constraints are the family of objects that inherit from Constraint, i.e. AlignPosition, AlignOrientation, etc. AlignPosition and AlignOrientation are not typically referred to as “body mover objects”.

Regardless, it seems the warning is a dud based on the responses in this thread:

Studio complaining about PGS physics solver not being enabled when PGSPhysicsSolverEnabled isn't a property of Workspace any more

I noticed that after the most recent update, Studio complains that I’ve disabled the PGS physics solver and that constraints won’t work properly, when I never touched the setting - and worse - it doesn’t even seem to exist any more. [image] [image] I get this issue in the client window when starting a local test server, 100% of the time.

It should be patched by next week.