Hi, josemendez, thanks for your answer. 
However, please notice in the screenshot, that that's not related to the fixed timestep and multiple calls in the same frame, as that spike is for just 1 call in that frame. We're using the same timing for update and fixed update calls, as you can see below. Also, here's one more screenshot showing a spike using these timings (for 60fps) on the clean project:
![[Image: LZ4gXKI.png]](https://i.imgur.com/LZ4gXKI.png)
![[Image: n6hjG3V.png]](https://i.imgur.com/n6hjG3V.png)
As you can see, it's narrowed down to a single call specifically to Oni.WaitForAllTasks(), and doesn't seem to be affected by Unity's own physics calculations.
There are no such spikes whatsoever when temporarily disabling the ObiSolver component, and we aren't affecting any rigidbodies with ropes in this project, they're purely visual, and all colliders are set as kinematicForParticles.
Changing the "Maximum Allowed Timestep" doesn't change this behavior in any way, as it's already just 1 call in those frames. There's a better official documentation on that value in this post: https://forum.unity.com/threads/what-is-...st-2139556
I've also tried setting it to the minimum and higher values, just to be sure, to no avail.
I can send you the project so you can take a closer look if you can. (It's really just a clean new project though).
These high spikes are rendering the application unusable in VR, and I really need your help with that.
Thanks again.
However, please notice in the screenshot, that that's not related to the fixed timestep and multiple calls in the same frame, as that spike is for just 1 call in that frame. We're using the same timing for update and fixed update calls, as you can see below. Also, here's one more screenshot showing a spike using these timings (for 60fps) on the clean project:
As you can see, it's narrowed down to a single call specifically to Oni.WaitForAllTasks(), and doesn't seem to be affected by Unity's own physics calculations.
There are no such spikes whatsoever when temporarily disabling the ObiSolver component, and we aren't affecting any rigidbodies with ropes in this project, they're purely visual, and all colliders are set as kinematicForParticles.
Changing the "Maximum Allowed Timestep" doesn't change this behavior in any way, as it's already just 1 call in those frames. There's a better official documentation on that value in this post: https://forum.unity.com/threads/what-is-...st-2139556
I've also tried setting it to the minimum and higher values, just to be sure, to no avail.
I can send you the project so you can take a closer look if you can. (It's really just a clean new project though).
These high spikes are rendering the application unusable in VR, and I really need your help with that.
Thanks again.