Bug / Crash Burst not working at all

[josemendez]

So thank you for explaing that Fixed updates are accumulating, but that doesnt answer the question
Try explaining why Burst is not executing the same way between the two

Have you checked that Burst is enabled for builds, as I suggested? https://docs.unity3d.com/Packages/com.un...er-support

On the same pc, with Burst compilation enabled for standalone, the standalone build is about 5-10% faster than the editor for me. The build should never be slower than the editor, unless your code isn't being compiled by Burst.

Note: you should enable SSE4 to take full advantage of vectorization. SSE2 is a much older extension, and AVX2 isn't as widely supported, so chances are your build is falling back to SSE2.

Regarding the freezes and reproducing them. So we have noticed that your system spawns these OniColliderWorld game objects on its own in Editor time. Yesterday I thought it was in Play only. So it spawns, and then we (without knowing it) save them to the scene.

Imagine, after that I decide to run Burst instead, and enforce it through all Ropes like this:

/*[SerializeField]*/ private BackendType m_Backend = BackendType.Burst;
ObiSolver.cs, line 101

This is where the freeze happens once you try loading a scene with a rope.

I'm unfortunately unable to reproduce this :/. I've created a solver that uses Oni, saved the scene, then switched the solver to Burst programmatically, but it runs fine.

The Oni/BurstColliderWorld object lifetime is managed by the solvers using lazy initialization: in the case you outline, since the world already exists in the scene it won't be created again on first use: the existing instance would be used.