[Oculus] Repeating pattern of FPS drops. Performance graph looks like a slow heartbeat.

[Mechalus]

I've had this problem since I got my Oculus, and I can't nail it down.

Build:
Windows 10
Motherboard: ASUS X99-A/USB 3.1
Processor: Intel Core i7-5820K Haswell-E 6-Core 3.3GHz
Memory: HyperX 16GB (4 x 4GB) 288-Pin DDR4 SDRAM DDR4 3000 (PC4-24000)
GPU: nVidia GeForce 1080ti
Storage: Samsung 850 EVO 500GB 2.5-Inch SATA III Internal SSD
HMD: Oculus Rift

Regardless of the settings or what I'm doing in game, whether I'm sitting in the opening menu, in a haz-res, or in a station, I see the same issue:

Framerate will sit at a solid 90fps for about 5 seconds, then dip to about 30fps for about 2 seconds, and then back to 90fps. The cycle repeats endlessly.

Adjusting settings like Anisotropic Filter or SS may get the fps to adjust a bit, but regardless, it always takes a dive every 5 seconds or so and then pops back up, always repeating. Nothing I've been able to do seems to have an affect on the cycle.

I'm at a loss. As far as I can tell there is nothing going on in the background. And it's done this after SSD reformats and re-builds.

Any suggestions would be very welcome!

 

[Sierra_Hotel]

Run a game booster and shut down background programs. Then, go into Task Manager -> Details Tab -> right-click on Elite and both Oculus programs, click on Set Priority, set to High.

 

[Mechalus]

It's worth a try.
I've never delved into game boosters before. Any suggestions?

 

[Sierra_Hotel]

I've tried a few at varioius times. The last one I tried was the Razer Cortex, it kept causing random crashes, but it let me play around and find things I could do without and shutdown/uninstall. I consider them to mainly be a diagnosis tool. Also consider doing some of the Win10 optimizations if you haven't already, that was the biggest gain in performance I saw.

 

[VR_Yata_PL]

I've had this problem since I got my Oculus, and I can't nail it down.

Build:
Windows 10
Motherboard: ASUS X99-A/USB 3.1
Processor: Intel Core i7-5820K Haswell-E 6-Core 3.3GHz
Memory: HyperX 16GB (4 x 4GB) 288-Pin DDR4 SDRAM DDR4 3000 (PC4-24000)
GPU: nVidia GeForce 1080ti
Storage: Samsung 850 EVO 500GB 2.5-Inch SATA III Internal SSD
HMD: Oculus Rift

Regardless of the settings or what I'm doing in game, whether I'm sitting in the opening menu, in a haz-res, or in a station, I see the same issue:

Framerate will sit at a solid 90fps for about 5 seconds, then dip to about 30fps for about 2 seconds, and then back to 90fps. The cycle repeats endlessly.

Adjusting settings like Anisotropic Filter or SS may get the fps to adjust a bit, but regardless, it always takes a dive every 5 seconds or so and then pops back up, always repeating. Nothing I've been able to do seems to have an affect on the cycle.

I'm at a loss. As far as I can tell there is nothing going on in the background. And it's done this after SSD reformats and re-builds.

Any suggestions would be very welcome!

Run Elite in VR and in Task Manager chceck which services generating high peaks.
I had problems with Microsoft Compatibility Telemetry months ago but fixed it already.

 

[Mechalus]

Run a game booster and shut down background programs. Then, go into Task Manager -> Details Tab -> right-click on Elite and both Oculus programs, click on Set Priority, set to High.

No joy. I loaded up and ran Razor's booster. And while it did free up some resources, and I'll probably continue to use it (thanks for the suggestion!), it didn't stop the "heartbeat" problem. It still dips from 90 fps down to 30 fp and back every few seconds. It'd probably be fine if it was a quick dip, but it stays at 30fps for 2-3 seconds before bumping back up to 90.

I opened Task Manager and sorted by GPU usage, and I noticed that OculusClient.exe and Client Server Runtime Process would jump up to the top of the list whenever the downward dip happened. Oculusclient.exe would show about 20% of the GPU's resources in use before it dropped back down. Client Server Runtime Process never used more than just 2-3%.

Unfortunately, I'm not 100% sure if this is normal behavior or tied to the problem.