New To The Forum? Click Here To Read The How To Guide. -- Developers Click Here.

Occasional Brief Stutter/freeze when looking left/right

DranuDranu Posts: 10
NerveGear
edited April 15 in Support
So in just about every game, I have extremely smooth performance with the exception of one thing: any movement of the head left or right, which can occasionally (typically once every 30 seconds or so) cause a very short stutter or freeze.  It is almost as if the screen freezes at that location for a split second while my head is still moving.  Verticle movement does not seem to do this, or if it does it is extremely rare (unless combined with horizontal turning).  Its hard to tell if its a split second of frozen head tracking or if the fps drops to 0 for a split second (audio does not skip, just the visual), but it is almost certainly tracking as sometimes it looks more like a slight jump than a frame slow.  It happens on low end to higher end games with seemingly equal frequency.

It would be a minor annoyance on a screen, but in VR it really break immersion.  It is getting very frustrating.

So I have tried a ton of solutions now (here are a few):
  1. Disabling any MSI afterburner type program
  2. Re-positioning my 3 sensors (both in actual location and USB slots
  3. Disabling programs like f.lux
  4. Searching for and disabling any unnecessary start-up program.

These problems did not exist when I first got the rift.

My system roughly:
Win 10
MS-7917
i7-4790K CPU
1080ti GPU
16gb ram

Comments

  • MAC_MAN86MAC_MAN86 Posts: 868
    Trinity
    Lots have this and I think we all do but to a lesser notable extent on high end PCs.
    I think it's either the USB Controllers in a Win10 Update or the Oculus Firmware Update.
  • DranuDranu Posts: 10
    NerveGear
    hmmm ya, because I do not think I had it earlier in the year, though I suppose I might have not noticed it being new to VR and so forth.
  • KetherMalkuthKetherMalkuth Posts: 1
    NerveGear
    I have also noticed this. It might be just my impression, but it feels to me like this micro-jumps occur at specific angles which roughly coincide with my sensors, as if they were caused by some kind of switching between sensors as the main tracker (no actual idea on how constellation merges data from the three sensors, this are all subjective impressions that might or might not help anyone :wink: )
  • Log_a_FrogLog_a_Frog Posts: 1,044
    Trinity
    Are you using a pci-inateck?
  • Sharkster-NVRSharkster-NVR Posts: 74
    Hiro Protagonist
    There is an obvious issue with a huge percentage of NVIDIA boards and drivers beyond 384. Check out my observations here: https://forums.oculusvr.com/community/discussion/62663/how-nvidia-ruins-the-oculus-rift-experience

    However, Nvidia couldn't be bothered to fix this for over half a year now.
    ERAZER X7849 Notebook - CPU: Intel Core i7 6820HK - GPU: GTX 1070, 8 GB GDDR5 RAM - RAM: 32 GB (4x 8 GB DDR4 HYNIX PC4 17000 DUAL CHANNEL) - MAINBOARD: INTEL HM170
  • DranuDranu Posts: 10
    NerveGear
    Are you using a pci-inateck?
    No, just a MSI-797 gaming 5 motherboard.  I have heard the inateck does not solve issues from a few.
  • cyberealitycybereality Posts: 25,667 Oculus Staff
    What about Asus AI Suite or Asus Sonic Suite? They should be uninstalled. Do you have latest Nvidia driver?
    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
  • Sharkster-NVRSharkster-NVR Posts: 74
    Hiro Protagonist
    Do you have latest Nvidia driver?
    Dranu said:
    These problems did not exist when I first got the rift.

    Having "the latest Nvidia drivers" is the main cause of the problem...
    ERAZER X7849 Notebook - CPU: Intel Core i7 6820HK - GPU: GTX 1070, 8 GB GDDR5 RAM - RAM: 32 GB (4x 8 GB DDR4 HYNIX PC4 17000 DUAL CHANNEL) - MAINBOARD: INTEL HM170
  • DranuDranu Posts: 10
    NerveGear
    What about Asus AI Suite or Asus Sonic Suite? They should be uninstalled. Do you have latest Nvidia driver?
    I dont have those programs and I have the latest driver, though I am going to try rolling it back soon.
  • DranuDranu Posts: 10
    NerveGear
    Okay I fixed it a good deal thanks to Oculus support.  I still get some of the same chop/freeze/stutter, but much less often and far less pronounced.  Plus it seems to run more smoothly.  Might hardly notice it if I werent looking for it.  Wish it were perfect but its not far. So one of these 3 things (for others looking) helped a ton:   Either:
    1.  A fresh rollback on NVIDIA display drivers to 388.59;
    2. Pulling the HDMI cord out of the Oculus headset and putting it back in; or
    3. In device manager, selecting the USB devices ("universal serial bust controllers"), and making sure all do not have the "allow the computer to turn off this device to save power" checked on any of them
  • Sharkster-NVRSharkster-NVR Posts: 74
    Hiro Protagonist
    Dranu said:
    I still get some of the same chop/freeze/stutter, but much less often and far less pronounced.
    You'll soon realize that it didn't really change anything. You can actually run diagnosis tools (as shown in the thread I've linked above) to have an objective comparison.
    ERAZER X7849 Notebook - CPU: Intel Core i7 6820HK - GPU: GTX 1070, 8 GB GDDR5 RAM - RAM: 32 GB (4x 8 GB DDR4 HYNIX PC4 17000 DUAL CHANNEL) - MAINBOARD: INTEL HM170
  • MAC_MAN86MAC_MAN86 Posts: 868
    Trinity
    edited April 18
    This is actually possibly true too @Sharkster-NVR as for me I used to use SS=1 & HMD=1.5
    If I use this now (no ODT) I get similar issues again.
    Now I use SS=1 & HMD=1 but with ODT and PD=1.85 to perform well enough without glitches/judders but its not as smooth as it once was in E:D at the edges when rolling for large objects. Happy enough but inside Stations is where it can build up to go very bad if I go any higher so I keep to Shadows High not Ultra.

    I don't recommend solely rolling back nor using DDU in Normal Mode as it will leave files behind unless you do access SAFE MODE. Once installing new drivers, reboot again to access the Nvidia Control Panel. If it's still there before a boot then the files were not fully deleted prior!
    The machine will take a long time to re-Index the new drivers so be patient and allow it to settle. It has much re-mapping for DLL files to sort out and things will load slower at first!
  • cyberealitycybereality Posts: 25,667 Oculus Staff
    Turning up pixel density settings, even on a decent computer, can be a cause of judder.
    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
  • MAC_MAN86MAC_MAN86 Posts: 868
    Trinity
    Hehe solved: I turned off EVGA PrecisionOCX and can now run PD=2
    I may try reverting back to PrecisionX16 to get use of my superclock2 KBoost though.
Sign In or Register to comment.