search

LibreVR / Revive

Play Oculus-exclusive games on the HTC Vive or Valve Index, scroll down for downloads and installation instructions.
Other
3.57k stars 331 forks source link

Random jitter in Wilson's Heart #612

Open lghtanddrk opened 7 years ago

lghtanddrk commented 7 years ago

I have an overclocked GTX1080, 64 GB of RAM, Window 10 Pro and an i7-6900k. I have tried from low to high resolution settings and I randomly get jitter (like a drop in frame rate) when turning my head. It will go long stretches with no issue and then suddenly start. When the issue happens it tends to last for minutes at a time. This can even happen when there is no action happening on the screen.

ionic234 commented 7 years ago

What version are you using? I have a similar system as you but a 6700k and half the ram and i've not been able to get the game to run either.

I was getting jitters on older versions but when i try using version 1.1.2.1 it crashes on the main menu in the HMD (frozen image) and runs at a very low (single digit) frame rate on my monitor. The HMD is still tracking as the perspective on my monitor shifts as i move it around even-though the image in the HMD is static. I've noticed the game is outputting at full screen which might be an issue as i have an ultrawide QHD monitor with G-sync enabled. I've no idea how this effects VR performance but it still crashes if i only have my old HD monitor enabled.

ionic234 commented 7 years ago

I did a little experiment and captured the frame timings and the CPU utilization from the task manager. Seems Wilsons Heart is only using one of my logical cores and quickly topping it out.

frametimingandtaskmanager

Also the crash is happening when i hold down the menu button to setup my view.

lghtanddrk commented 7 years ago

I'm using version 1.1.2.1. The game runs it's just that occasionally I get this random stutter or jitter effect as if the frame rate id dropping when I look in any direction. then suddenly it will go away for a long stretch and then come back again.

kvdv99 commented 7 years ago

I solved this by disabling asynchronous reprojection.