21-12-2023, 10:43 AM
Hey, thanks for the quick reply.
I checked the profiler yes, but I struggle to make a lot of sense out of it, apart that it seemed related to Obi operations. Here are two profiler screenshots with highlights of what seems relevant to me. One is editor profiling, one is play mode.
Again I repeat myself, but keep in mind that the code being executed is the same before and during the ~2000ms spike AND this only happens if the VS debugger is active.
Also something else that might be related: when I tried to replicate the issue on a new, simple project, I got exceptions on the two lines I mentioned earlier. See the attached screenshot.
This is a new, very simple standard pipeline project (although my main project uses URP) that only make SpatialQuery calls (I couldn't reproduce the lag spike there). On my main URP project, there is no caught exception here.
Also I just tried disabling the safety checks from the Jobs menu, as you indicated, but somehow the spikes still occur unless I comment the two lines.
Ultimately, commenting those two lines works well enough for me, but if you want to investigate this issue more I'll do my best to assist. I just hope it's not an issue that I somehow created myself, as I don't mean to waste you time on this.
I checked the profiler yes, but I struggle to make a lot of sense out of it, apart that it seemed related to Obi operations. Here are two profiler screenshots with highlights of what seems relevant to me. One is editor profiling, one is play mode.
Again I repeat myself, but keep in mind that the code being executed is the same before and during the ~2000ms spike AND this only happens if the VS debugger is active.
Also something else that might be related: when I tried to replicate the issue on a new, simple project, I got exceptions on the two lines I mentioned earlier. See the attached screenshot.
This is a new, very simple standard pipeline project (although my main project uses URP) that only make SpatialQuery calls (I couldn't reproduce the lag spike there). On my main URP project, there is no caught exception here.
Also I just tried disabling the safety checks from the Jobs menu, as you indicated, but somehow the spikes still occur unless I comment the two lines.
Ultimately, commenting those two lines works well enough for me, but if you want to investigate this issue more I'll do my best to assist. I just hope it's not an issue that I somehow created myself, as I don't mean to waste you time on this.