(20-04-2022, 09:38 AM)josemendez Wrote: I was under the impression that this happened even in an empty scene? Are the +20000 SearchEnumerator calls only happening in Play mode?
It did happen in an empty scene. Up until now the search calls started happening immediately after importing Obi, without opening any scene. But now with the API upgrade during importing I managed to postpone that to launching play mode in a scene with Obi components. But once it happens it stays that way forever, even if you close and reopen the project.
Quote:Maybe this is a dumb thing for me to say, but if you're using Burst check that the Burst compiler is actually enabled and that the jobs debugger is disabled. Otherwise performance will be quite terrible, much worse than when using Oni.
Burst compilation is enabled, and safety checks are off. I'm not 100% sure about the debugger since that doesn't seem to exist in the dropdown menu anymore for 1.6.5. There only is something called Native Debug Mode Compilation, which is off.
I also tried removing it to see what would happen, and to my surprise nothing changed. I'm pretty sure I got errors in the console when setting the obi solver to burst while burst was not installed in 2019.4, but there is nothing now and the solver works fine apart from the horrid performance caused by the search calls. Its not worse than outside of play mode though, so I'm pretty sure it has nothing to do with the solver.