cancel
Showing results for 
Search instead for 
Did you mean: 

Oculus 0.8 Alpha RC2 [Private]

cybereality
Grand Champion
Hey,

There is an 0.8 RC2. Please provide feedback if you can.

Runtime:
https://s3.amazonaws.com/static.oculus. ... .0_win.exe

SDK:
https://s3.amazonaws.com/static.oculus. ... .8.0.0.zip

You will NEED these drivers:

Nvidia 358.70:
https://developer.nvidia.com/gameworks- ... er-support

AMD 15.10:
http://support.amd.com/en-us/kb-article ... -beta.aspx
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
17 REPLIES 17

Scawen
Heroic Explorer
I've tried this new 0.8 RC2 with the 358.70 drivers.

OK: The crash on exiting a VR program has been fixed.

NOT OK: I still get the stutter and the System process consuming one core's worth of CPU time (ALWAYS ON THE SECOND VR RUN, NEVER ON THE FIRST).

I rebooted the computer after installing the drivers. The problem persists.

To reproduce:

Start your computer. Do not run the config utility.
Run a VR program. The Rift light goes blue.
Exit the VR program. The Rift light goes yellow.
Run a VR program. The Rift light goes blue.
Now look in task manager, processes tab, "Show processes from all users".
You will see a mysterious "System" process by User Name "SYSTEM", consuming an entire core.


I wish you guys would hire a tester. This is getting tedious.
Live for Speed - www.lfs.net

andrewtek
Expert Protege
VR Preview works great in UE4. Thanks! 😄

cybereality
Grand Champion
@scawen: I'm going to have to track this down myself. I should have some time today.
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV

andrewtek
Expert Protege
@cyber and @scawen: I tried the steps to reproduce on Windows 10 and upon exit, I saw my overall CPU at 1% with no cores fully utilized. It looks like this issue is not universal to all setups.

Scawen
Heroic Explorer
"andrewtek" wrote:
@cyber and @scawen: I tried the steps to reproduce on Windows 10 and upon exit, I saw my overall CPU at 1% with no cores fully utilized. It looks like this issue is not universal to all setups.
Thanks for the test, but it's not on exit. The high CPU usage is only while the VR program is still running.

The important points are:

1) In task manager, make sure you have "Show processes from all users" set. Otherwise you will not see it.

2) Probably just have the task manager running on your desktop so you can look at it any time by lifting the Rift, while a VR program is still running.

3) The first time you run a VR program, there is no "System" process with extremely high CPU usage. Everything is OK.

4) When you exit a VR program, then start VR again, then there is a "System" process using a whole core.

5) Do not have the Config Utility open while doing this test. If it is open, the Rift light never goes from blue to yellow. The high CPU usage is when the Rift light goes from blue to yellow and back to blue again (when the second VR run is started, and all runs thereafter until reboot).
Live for Speed - www.lfs.net

andrewtek
Expert Protege
Thanks for the clarification @scawen. With that, I was able to reproduce the issue. On Windows 10, that system process happens to be "C:\Windows\System32\ntoskrnl.exe"; pretty low level stuff. Speculating it is related to drivers.

Article about process: https://en.wikipedia.org/wiki/Ntoskrnl.exe

cybereality
Grand Champion
Ah OK. In that case I am seeing the System at around 10%. Is that abnormal?
AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV

Scawen
Heroic Explorer
Yes, as described in the other thread. You should find that does not happen on the first run.

On computers with lower number of cores, the 25 or 50 percent CPU use by that System process is crippling, even if our computer is perfectly capable of running good VR on the first run after a reboot.

If you have loads of cores and your OS doesn't assign the crippled core to any other thread, then I guess you are OK. But we don't all have cores to throw away.

I guess a V8 running on 7 cylinders is still quite powerful... but we don't all have a V8 and don't want to buy one just to overcome what may well be a simple bug.
Live for Speed - www.lfs.net