-
Notifications
You must be signed in to change notification settings - Fork 8
Description
Discussed in #224
Originally posted by inn-pgonzalez January 9, 2026
Whenever I open the LiveCut scene and press Play, the Sofacomponent gets removed from the Cutting manager It seems to happen even before the CuttingManager reaches Awake. By the time the simulation begins, the component is already removed.
I have tested this in Unity 6.0.59f2 and 2022.3.62f1, with the same result.
The console shows multiple warnings, but nothing that clearly indicates why the cutting subsystem shuts down. For example:
No license detected. SofaContextAPI will use the free version of the integration.
...
Sofa Warning: Sofa.Component.Collision.Detection.Algorithm has already registered its components.
...
Sofa Warning: MeshRefinement has already registered its components.
There are dozens of “already registered” warnings, but no explicit errors explaining why the cutter disables itself.
Interestingly, if I modify the CuttingManager to search for the SofaCutting object by name after initialization, it works correctly. However, if I assign the component in the editor directly, it should work without needing a runtime search.
Has anyone seen this behavior?
Is there a required setup step (license, project settings, URP setting, or plugin configuration) needed to make it work properly?