10 hours ago
(02-05-2025, 11:04 PM)josemendez Wrote: This is really strange. A SIGTRAP signal is sent when a thread hits a breakpoint while a debugger attached. Furthermore, the stack trace line (1794985864) doesn’t look like a sane value. If I had to guess, this looks like heap corruption, which isn’t typically caused by managed (C#) code.
Have you updated Burst or any of the related packages (jobs, collections, mathematics) along with Obi? If so, which versions of these are you using? Also, is the build you’re testing a regular or a development build?
Collisions work in the Compute backend just like they do in the Burst backend. Feature-wise both backends are equivalent.
Kind regards,
There's no debugger attached, it's just a regular non-development build that's using IL2CPP. All of those packages are on the latest version that it lets me install with this version of Unity:
Burst - 1.8.21
Mathematics - 1.2.6
Collections - 2.1.1
Jobs - 0.70.0-preview.7
I don't know if this matters, but in both locations where I've seen this so far, the rope was disabled by default in the scene file and then was enabled after the scene was loaded, at which point the crash happens (but it doesn't crash every time).
I'm not sure why the colliders weren't working with compute when I tested before, but I just tried it again and that seems to be working correctly now.