Hey All,
In the next week we will transition the new PGS physics solver from “experimental” to become the official default solver on production. This means that new levels created in Studio will have the PGSPhysicsSolverEnabled property set to True by default. This only effects new creations.
All pre-existing levels that use the old solver will continue to do so.
This post is a call for all developers using the new solver to immediately report problems introduced by the PGS solver, and (preferably) send us any models that demonstrate the undesired behavior.
Note: After our last round of adjustments to body movers, some users observed changes in motion behavior. This is to be expected. With body mover parameter adjustments you should be able to restore the desired behavior. If for any reason you are not able to get back to the expected behavior please send us your models.
For additional information and best practices when using the PGS solver, please see our wiki page “Building with PGS”.
Now that this is open to posts from non-staff members, I’d like to point out that you can still switch PGS back off manually. I saw a thread or two on the main site where people thought new places used the PGS solver permanently and couldn’t use the old solver, but this isn’t the case. This only makes the default value for Workspace.PGSPhysicsSolverEnabled true – not lock it so you can’t change it.