20-04-2022, 12:09 PM
(This post was last modified: 20-04-2022, 12:11 PM by josemendez.)
(20-04-2022, 10:13 AM)locque Wrote: 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.
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.
This is extremely strange. The pattern you describe could have something in common with how Burst compiles jobs: by default it uses async deferred compilation, so nothing is compiled until you run the code for the first time. Once it's compiled, it stays that way unless you modify the code. Seems like the sluggishness has something to do with Burst having compiled the code?
However this also happened with the Oni backend right? So even though the behavior pattern is consistent with how Burst works, I'm not sure if it's related at all.
I think only Unity can shed some light on this, at this point. I will post on the Unity forums to see if someone has come across a similar issue, but if possible please report this as a bug so that they can take a look at it.