Semaphore.WaitForSignal is causing so much lag on Android!!! Help!!!

Hi, I also ran into the same! I tried to switch to the default render pipeline and it worked for me!,hi, I have also the similar problem where I used URP. I tried static batching and dynamic batching but Semaphore.WaitForSignal is taking 43ms. so i decided to switch to the default render pipeline and god damn it worked for me! now my game is running 60 fps. so just try to switch to the default render pipeline in case if u use URP!

@soundarking i am not a hundred percent sure on this but I have encountered this once on an oculus quest project. Urp renders to a intermediate render target by default (called color buffer). In the editor this is necessary but in builds you can write directly to the swap chain render targets (which oculus recommends). The texture switch costs a lot of gpu time and almost always pushes you beyond the 90 fps ti$$anonymous$$g. If you feel comfortable editing the urp files it can be fixed though.

It's sad that switching back to built in is still so often the only fix for these kinds of issues :-/