Hi,
We've been experiencing a bug with Obi for the past few weeks. It is really hard to reproduce, but sometimes it happens out of the blue. It mostly happens in scenes where we have two solvers. Sometimes at startup, sometimes when we're instantiating a GameObject with an ObiCloth.
The stack trace indicates the issues is with GetPointCloudAnisotropy, but this method is only used in the SoftBody script, which we're not using. I even tried to comment the line in Oni.cs but it is still trying to call it. Here is the stack trace:
0x00007FFE554D0805 (libOni) ClearTasks
0x00007FFE554D6FF5 (libOni) ClearTasks
0x00007FFE55504399 (libOni) GetPointCloudAnisotropy
0x00007FFE5550A28A (libOni) GetPointCloudAnisotropy
0x00007FFE5550A579 (libOni) GetPointCloudAnisotropy
0x00007FFE5552D470 (libOni) GetPointCloudAnisotropy
0x00007FFE876D7E94 (KERNEL32) BaseThreadInitThunk
0x00007FFE887CA251 (ntdll) RtlUserThreadStart
Do you have any indications of what this could be caused by? Our timestep is 0.04 and the max allowed timestep is also 0.04, which works fine for our simulations.
We're running Unity 2019.1.7 and we're using HDRP, but that shouldn't affect Obi(?).
Best,
Sune
We've been experiencing a bug with Obi for the past few weeks. It is really hard to reproduce, but sometimes it happens out of the blue. It mostly happens in scenes where we have two solvers. Sometimes at startup, sometimes when we're instantiating a GameObject with an ObiCloth.
The stack trace indicates the issues is with GetPointCloudAnisotropy, but this method is only used in the SoftBody script, which we're not using. I even tried to comment the line in Oni.cs but it is still trying to call it. Here is the stack trace:
0x00007FFE554D0805 (libOni) ClearTasks
0x00007FFE554D6FF5 (libOni) ClearTasks
0x00007FFE55504399 (libOni) GetPointCloudAnisotropy
0x00007FFE5550A28A (libOni) GetPointCloudAnisotropy
0x00007FFE5550A579 (libOni) GetPointCloudAnisotropy
0x00007FFE5552D470 (libOni) GetPointCloudAnisotropy
0x00007FFE876D7E94 (KERNEL32) BaseThreadInitThunk
0x00007FFE887CA251 (ntdll) RtlUserThreadStart
Do you have any indications of what this could be caused by? Our timestep is 0.04 and the max allowed timestep is also 0.04, which works fine for our simulations.
We're running Unity 2019.1.7 and we're using HDRP, but that shouldn't affect Obi(?).
Best,
Sune