This may not be your issue, but I found that running the app standalone fixed my similar issues. I was seeing frame drops at odd times when my game was doing the least amount of work. But when I tried to diagnose it by running it through the performance wizard/CPU sampler it ran fine. So for me at least, I only see these issues when running from within Visual Studio 2013 with the debugger attached.
As you see in the images above the DirectX performance is much smoother. The 1 dropped frame came at program start, after that I do not get any more dropped frames.
OpenGL version on the other hand continuously drops frames, roughly every 10 seconds.
Running the examples as standalone executables vs. inside Visual Studio seem to have no impact on performance on my machine.
I'm using OpenGL and an Nvidia 970GTX paired with the VR recomended Nvidia drivers and it runs without drops. Our integration is done externally by loading a .dll into our own rendering engine. The .dll is being compiled in release mode using VS2010.
On 0.6.0.1 I was experiencing drops that occurred in quite fixed intervals. I imagine that this may be related to the oculus direct driver mode and nvidia direct driver mode?? I guess when moving forward to 0.0.7.0 nvida direct mode is being used which does not have this problem??
"skavee" wrote: I'm using OpenGL and an Nvidia 970GTX paired with the VR recomended Nvidia drivers and it runs without drops. Our integration is done externally by loading a .dll into our own rendering engine. The .dll is being compiled in release mode using VS2010.
On 0.6.0.1 I was experiencing drops that occurred in quite fixed intervals. I imagine that this may be related to the oculus direct driver mode and nvidia direct driver mode?? I guess when moving forward to 0.0.7.0 nvida direct mode is being used which does not have this problem??
0.4.4.0 Doesn't have the problem with direct mode. We are stuck to that version because of the bug. 0.6.0.1 Have the problem in direct mode. 0.7.0.0 Have the problem in direct mode.
Either oculus officially drops OGL support or fix the problem, but any application that use OGL doesn't work properly past 0.4.4.0.
"skavee" wrote: I'm using OpenGL and an Nvidia 970GTX paired with the VR recomended Nvidia drivers and it runs without drops. Our integration is done externally by loading a .dll into our own rendering engine. The .dll is being compiled in release mode using VS2010.
On 0.6.0.1 I was experiencing drops that occurred in quite fixed intervals. I imagine that this may be related to the oculus direct driver mode and nvidia direct driver mode?? I guess when moving forward to 0.0.7.0 nvida direct mode is being used which does not have this problem??
0.4.4.0 Doesn't have the problem with direct mode. We are stuck to that version because of the bug. 0.6.0.1 Have the problem in direct mode. 0.7.0.0 Have the problem in direct mode.
Either oculus officially drops OGL support or fix the problem, but any application that use OGL doesn't work properly past 0.4.4.0.
I think you miss understood me. For us 0.7.0.0 does NOT drop frames when using direct mode & OpenGL. 0.6.0.0 and 0.6.0.1 did however drop frames.
So as I said the new direct (nvidia) driver mode seems to not be affected by the 'dropped frames bug' when running OpenGL. However I have not yet tested if this is also true for direct oculus driver mode under 0.7.0.0 (OpenGL).
EDIT: System configuration: NVIDIA 970GTX + Driver v.355.83 Oculus Runtime 0.7.0.0 SDK version 0.7.0.0 VisualStudio 2010
My config that worked: Windows 7 + some old drivers. Oculus SDK 0.6.0.1
I've updated drivers to recommended for 0.7 BUT I stayed with 0.6.0.1 SDK and Runtime. Now I'm seeing constant frame drops, lag every N frames. I'm searching for some older drivers that won't have this issue. I decided not to move to 0.7 as I don't know if OpenVR already supports it as well (need to check).
