![]() |
|
Bug / Crash Stitcher breaks simulation - Printable Version +- Obi Official Forum (https://obi.virtualmethodstudio.com/forum) +-- Forum: Obi Users Category (https://obi.virtualmethodstudio.com/forum/forum-1.html) +--- Forum: General (https://obi.virtualmethodstudio.com/forum/forum-5.html) +--- Thread: Bug / Crash Stitcher breaks simulation (/thread-4554.html) |
Stitcher breaks simulation - Qriva0 - 19-09-2025 Enabling or disabling ObiStitcher does not work properly, because simulation is running, error is logged to console. However deactivation of gameobject with stitcher actually breaks solver in some way and simulation does not work anymore - unity must be restarted. RE: Stitcher breaks simulation - josemendez - 19-09-2025 (19-09-2025, 11:47 AM)Qriva0 Wrote: Enabling or disabling ObiStitcher does not work properly, because simulation is running, error is logged to console. Hi, I'm unable to reproduce this issue, tried enabling/disabling the ObiStitcher component in the RuntimeCloth sample scene. What Obi version/Unity version are you using? can you describe steps to trigger this? The error message you posted seems likely unrelated, as it's an error while trying to set the velocity of a rigidbody. RE: Stitcher breaks simulation - Qriva0 - 19-09-2025 (19-09-2025, 12:26 PM)josemendez Wrote: Hi, Obi 7.1 and I tried that demo scene, and it does not work too, but this time I managed to crash unity. Try to disable and enable gameobject with stitcher several times, and try to make it fast. BTW offtopic - I was unable to run cloth tearing on my pc, there was always some error or there was no cloth, can't remember exactly. I think could not create valid, working blueprint. In my case stitcher is not very important right now, just wanted to try it, so don't worry about priority. Enabling and disabling gmaeobject causes this error for sure: Quote:InvalidOperationException: The previously scheduled job BurstStitchConstraintsBatch:StitchConstraintsBatchJob writes to the UNKNOWN_OBJECT_TYPE StitchConstraintsBatchJob.lambdas. You must call JobHandle.Complete() on the job BurstStitchConstraintsBatch:StitchConstraintsBatchJob, before you can deallocate the UNKNOWN_OBJECT_TYPE safely. Then later it spams something like that: Quote:System.IndexOutOfRangeException: Index -8084 is out of range of '387' Length. RE: Stitcher breaks simulation - Qriva0 - 23-01-2026 Hi! Did you manage to reproduce the issue? I tried to use stitcher recently and it make unity crash way more often then before, and even if not, it premamently spams things like this in console and break the simulation: "System.IndexOutOfRangeException: Index 256 is out of range of '0' Length." RE: Stitcher breaks simulation - Qriva0 - 29-04-2026 Hi again! Is there any progress with this issue? RE: Stitcher breaks simulation - Qriva0 - 13-06-2026 In case anyone else encounter the same problem here is dirty quick fix in ObiStitcher: Code: private void RemoveFromSolver(ObiSolver solver)Quick summary of problem causing errors: Obi stitcher is implemented in a wrong way, it creates batches directly used by simulation, including data arrays like lambdas. For this reason anything that triggers removal of stitches from simulation while it's running will causes exception, because arrays can't be disposed. Things that trigger this error is: disabling stitcher, disabling any actor used by stitcher, application quit and exit playmode. |