09-04-2015 01:19 PM
10-28-2015 02:37 PM
10-28-2015 03:02 PM
"scawen" wrote:
I haven't tried the Config Utility trick since installing the new drivers, so don't know if it still works. I just got the Rift all set up, found the CPU consuming bug was still not fixed and put the Rift away again, as I have done several times in the last 8 weeks.
No point trying to develop for the Rift at the moment while the new drivers are full of bugs. Best to stick with 0.6 as it has the best compatibility and fewest bugs.
I don't know what NVIDIA surround and bezel correct are, I have the simplest setup. I think this CPU consuming process is initialised on most if not all computers with an NVIDIA card. I don't think it is some specific setup.
10-29-2015 03:47 AM
"TrevorA" wrote:The Oculus developers seem to have this idea that fixing bugs will slow their development, and therefore they shouldn't waste any time fixing them (or even having a quick look to see what the problem is). Meanwhile, fewer and fewer customers and software developers can actually use their Rift.
but no real response in 8 weeks is frankly...... quite normal 🙂
10-29-2015 11:33 AM
10-29-2015 01:08 PM
11-02-2015 03:55 PM
11-03-2015 12:38 AM
11-03-2015 01:03 AM
"cybereality" wrote:
You guys will be happy to hear that we have found the problem! Very sorry for the long run around on this one.
11-03-2015 11:53 AM
11-03-2015 09:05 PM
"CrazyNorman" wrote:
I already have a thread vaguely describing the issue, but at the point of writing it, I wasn't sure if I had encountered a bug or not. I've further isolated the issue, and it's definitely a bug with the 0.7 Oculus Runtime.
Reproduction Steps:
1. Boot up your computer, from a fresh power-off state (not sleep or hibernate)
2. Open the Oculus Configuration Utility
3. Press "Show Demo Scene" to run the Desk Demo.
4. Note CPU usage. The desk demo itself will be using some, but other than that CPU utilization should be low:
5. Press escape to close the Desk Demo while leaving the Oculus Configuration Utility open.
6. Note CPU usage. It should be extremely low (nothing's really running)
7. Repeat steps 3-6 as many times as you want. Results are consistent.
8. Press "Close" to close the configuration utility. Your camera light should turn off, indicating that the DK2 is no longer in use.
9. Re-open the Oculus Configuration Utility
10. Press "Show Demo Scene" to run the Desk Demo.
11. Note CPU usage. While the configuration utility is using a similar amount of CPU, there is a new contender for processing power. "System" is now maxing out one core of processing power. For my 4-core 3570k that's 25%.
12. Press escape to close the Desk Demo while leaving the Oculus Configuration Utility open.
13. Note CPU usage. "System" continues to consume as much processing power as it can on one thread, while the Oculus Configuration Utility itself stops consuming any CPU.
14. Repeating steps 10-13 as many times as you'd like. Results are consistent.
15. Press "Close", Oculus Configuration Utility closes.
16. Note that the "System" process is no longer using any CPU. This heavily implies that it's something to do with the DK2 runtime.
17. Run any Oculus app you want, System will jump back up to >= 25%
18. Sleeping the computer, restarting the Oculus Service, turning your Rift on/off, etc, will make no difference. The only thing that will work is a full reboot.
This isn't specific to the desk demo. After a fresh reboot, the first VR application run against 0.7 will function normally (showing that it isn't a necessary behavior of the new run-time, but rather a regression). After closing it and running a second Oculus application (or the same one a second time) will result in the System process maxing out a CPU core full-blast. None of this behavior occurred for me on 0.6
My specs are as follows:
- Oculus Runtime 0.7.0.0
- NVIDIA 355.84 Driver (355.83 is the same)
- Windows 8.1 64-bit
- Intel i5 3570k @ 3.8ghz. Same issue whether underclocked or overclocked
- NVIDIA 780 Ti
- 16GB RAM
Please let me know what I can do to help the development team reproduce and resolve this issue. Quite a few of my application's users have encountered this bug also.