OculusRuntime.WaitToBeginFrame takes approximately 10ms when running on a new project with Oculus Integration

In the Oculus runtime, it is completely normal for WaitToBeginFrame to take 10 ms, based on the application's actual performance. In an empty project, you can expect vsync to be about 10 ms. That coincides with the numbers you're seeing with WaitToBeginFrame. When you see spikes in WaitToBeginFrame, that means your app is doing something that causes a miss in the VSYNC deadline. In essence, the last frame gets reprojected and the Oculus runtime decides that you need to wait before starting the next frame. Otherwise you're going to start introducing latency in your app. That's all decided on by the Oculus runtime. As to what causes missing that vsync deadline, that could be anything, from your app taking extra time on the CPU or GPU. One thing you can do is check the frame (or two) before the spike to see if there's anything suspect there.

In the Oculus runtime, it is completely normal for WaitToBeginFrame to take 10 ms, based on the application's actual performance. In an empty project, you can expect vsync to be about 10 ms. That coincides with the numbers you're seeing with WaitToBeginFrame. When you see spikes in WaitToBeginFrame, that means your app is doing something that causes a miss in the VSYNC deadline. In essence, the last frame gets reprojected and the Oculus runtime decides that you need to wait before starting the next frame. Otherwise you're going to start introducing latency in your app. That's all decided on by the Oculus runtime. As to what causes missing that vsync deadline, that could be anything, from your app taking extra time on the CPU or GPU. One thing you can do is check the frame (or two) before the spike to see if there's anything suspect there.