User scawen has posted this in the bugs section, but I would like to see how many of you have this bug, and whether there are any Nvidia Users that don't have this bug.
Pre-requisite: Oculus SDK Ver 7.0 or Later running a Nvidia Graphics Card
To see if you have the bug:
Re-boot your PC.
Once everything has loaded up, Start the Oculus Configuration Utility
Click Show Demo Scene
There is no need to wear your headset, just do the above.
The Blue Light will come on your Camera, and the Oculus Demo Program will Start and your headset should turn yellow to blue.
Now Close your Oculus Demo Screne Program using the Cross in the Top Right
And finally Click Close on the Configuration Utility, So the Blue Light Turns Off from the Camera and your headset goes from Blue to Yellow.
Now Repeat the Above Once Only, but this time, Leave the Demo Scene Program Open
Now Press CTRL ALT and DELTE at the same time and Select Task Manager
Click on the Process Tab
Sort the Process Tab by CPU, Showing the Highest CPU Usuage First
You should see this:
The bit your looking for is the part highlighted in Red above. Could you let us know what your CPU Usuage is please for the system process with the demo screne running. As you can see from mine, its 14% meaning this bug is taking up a whole of one of my cores, reducing performance in VR. Others have lost 25% CPU and whilst Cyberreality is looking into this, I would like to know if its affecting everyone or just specfic users.
More info for this bug was posted in the Reporting issues section by scawen and can be found in this link:
https://forums.oculus.com/viewtopic.php?f=34&t=25914
This bug has been outstanding since the 0.7 SDK. I have identified that it is a NVidia file causing the high CPU, but its important that this is fixed, and hence the post, to get others aware of the bug and report if you have it. I wasn't even aware of it until I read a post about it in the SDK 8.0 release.
This bug if you have it, will be hurting your Frame Rate. Most may not even notice is, because you have very fast machines and GPU, but I'm running Windows 10 on a I7 with a GTX 970, and it hit me with 14% CPU usuage that's uncessesary. On Flight Sim X, when I mananged to kill this process and regain my 14% Cpu back, Asyn Timewarp ran me at 75FPS Solid. Prior to that, the 14% was introducing a lot of judder.
Mabs
Pre-requisite: Oculus SDK Ver 7.0 or Later running a Nvidia Graphics Card
To see if you have the bug:
Re-boot your PC.
Once everything has loaded up, Start the Oculus Configuration Utility
Click Show Demo Scene
There is no need to wear your headset, just do the above.
The Blue Light will come on your Camera, and the Oculus Demo Program will Start and your headset should turn yellow to blue.
Now Close your Oculus Demo Screne Program using the Cross in the Top Right
And finally Click Close on the Configuration Utility, So the Blue Light Turns Off from the Camera and your headset goes from Blue to Yellow.
Now Repeat the Above Once Only, but this time, Leave the Demo Scene Program Open
Now Press CTRL ALT and DELTE at the same time and Select Task Manager
Click on the Process Tab
Sort the Process Tab by CPU, Showing the Highest CPU Usuage First
You should see this:
The bit your looking for is the part highlighted in Red above. Could you let us know what your CPU Usuage is please for the system process with the demo screne running. As you can see from mine, its 14% meaning this bug is taking up a whole of one of my cores, reducing performance in VR. Others have lost 25% CPU and whilst Cyberreality is looking into this, I would like to know if its affecting everyone or just specfic users.
More info for this bug was posted in the Reporting issues section by scawen and can be found in this link:
https://forums.oculus.com/viewtopic.php?f=34&t=25914
This bug has been outstanding since the 0.7 SDK. I have identified that it is a NVidia file causing the high CPU, but its important that this is fixed, and hence the post, to get others aware of the bug and report if you have it. I wasn't even aware of it until I read a post about it in the SDK 8.0 release.
This bug if you have it, will be hurting your Frame Rate. Most may not even notice is, because you have very fast machines and GPU, but I'm running Windows 10 on a I7 with a GTX 970, and it hit me with 14% CPU usuage that's uncessesary. On Flight Sim X, when I mananged to kill this process and regain my 14% Cpu back, Asyn Timewarp ran me at 75FPS Solid. Prior to that, the 14% was introducing a lot of judder.
Mabs
