Okay, thanks! I actually had that on my list of general performance improvements to try (putting all the ropes into one solver), but it's a bit time-consuming to redo some of my existing setup, so I kept putting it off. I'll give it a try soon and let you know if it solves my issues.
If this ends up making a big difference, I'd actually recommend putting that into the documentation for solvers / general setup in the same way that you recommend to only have one updater per scene.
Before reworking my logic / scenes, I decided to give this a test in a version of the same level where I put a bunch of ropes on a single solver (but without the additional script I use for my gameplay logic). It does seem worth doing in any case though, as even with Oni there's a little bit of an improvement in terms of framerate.
However... while the big difference in performance between Oni and Burst goes away, Oni is still SLIGHTLY better, which seems like something must still not be working as intended?
Oni: https://drive.google.com/file/d/1dE_pCfd...drive_link
Burst: https://drive.google.com/file/d/1wR9B0C9...drive_link
If this ends up making a big difference, I'd actually recommend putting that into the documentation for solvers / general setup in the same way that you recommend to only have one updater per scene.
Before reworking my logic / scenes, I decided to give this a test in a version of the same level where I put a bunch of ropes on a single solver (but without the additional script I use for my gameplay logic). It does seem worth doing in any case though, as even with Oni there's a little bit of an improvement in terms of framerate.
However... while the big difference in performance between Oni and Burst goes away, Oni is still SLIGHTLY better, which seems like something must still not be working as intended?
Oni: https://drive.google.com/file/d/1dE_pCfd...drive_link
Burst: https://drive.google.com/file/d/1wR9B0C9...drive_link