Getting stuttering/juddering when looking left/right? Was perfect a few weeks ago!?

[NeilF]

So trying to use the Rift today I'm getting quite obvious judders/stutters in the rendering as I turn my left left/right.

I've tried Steam VR, and a number of Oculus titles, and around the front 90 degrees as I look left/right I can see every now and then the scene stutter as if the sensors are getting confused?!

I've recalibrated the sensors numerous times. Tried moving them slightly. Tried moving one of the sensors to a USB 2 slot. Tried moving the HMD to USB 3 slot on the MB. But nothing seems to help!? They're minor but enough to put you off, and certainly nothing I was having before!

Any idea how to diagnose the cause of the stutters?

Note: Both sensors and the HMD were all in the Inateck 4 Port PCIe card which I'm sure was working fine until a couple of weeks ago!?



EDIT: Strangely I updated my graphics card drivers, and immediately that seemed to help. I re-did my sensor calibration and now judders seem 99% gone. I can still see the odd one, but that may now be me looking for them. It's certainly loads better! Odd!

 

[Worminator]

I see you fixed it but it was probably the Win10 fall update. Happened to a bunch of us a couple of weeks ago. It pushed a NVIDIA driver that wrecked VR for a lot of people.

 

[shadow133]

Would you define it as a momentary fps drop kind of stuttering? If so, try reinstslling nvidia drivers, then reduce hmd quality/ss and also change the asw settings to test them all (ctrl+1,2,3,4). I have a 1070 too, slightly faster cpu and I have had many issues recently too. Now it seems to have stopped, unless I am in a combat intensive environment. Overclocking makes everything run nicely, but unfortunately any overclock will cause crashes in my system. Volta can’t come soon enough.

 

[NeilF]

Would you define it as a momentary fps drop kind of stuttering? If so, try reinstslling nvidia drivers, then reduce hmd quality/ss and also change the asw settings to test them all (ctrl+1,2,3,4). I have a 1070 too, slightly faster cpu and I have had many issues recently too. Now it seems to have stopped, unless I am in a combat intensive environment. Overclocking makes everything run nicely, but unfortunately any overclock will cause crashes in my system. Volta can’t come soon enough.

The issue was across the board. eg: Even during setup with the VR headset up, if I looked left/right I could see the movement stutter/judder almost on every head turn.

And let's remember I'd been using it for months fine...

As Wominator pointed out, me installing the latest NVidia drivers has hopefully solved it. I was still getting a little tiny judder every now and then, but it really was tiny, and not often, so may now just me looking for issues...

I'll retest again tonight.

 

[Wasp0]

The issue was across the board. eg: Even during setup with the VR headset up, if I looked left/right I could see the movement stutter/judder almost on every head turn.

And let's remember I'd been using it for months fine...

As Wominator pointed out, me installing the latest NVidia drivers has hopefully solved it. I was still getting a little tiny judder every now and then, but it really was tiny, and not often, so may now just me looking for issues...

I'll retest again tonight.

Exact same thing happen to me. Even in OR Home i got that stuttering as i moved my head, made ED unplayable!

It was win 10 fall update and Nvidia driver upadate 388.13 that was the culprit. A quick uninstall of both and i am back to Nirvana. I have done all the delaying tactics to stop M$ from forcing this Autumn update on me again. I do here Nvidia fixed there side of things with the 388.30 update to the update, but i have left mine on the one before 388.13 update.

Now reading the bumf on the new Oculus Rift 2.0 home update, i am told i will need latest Nvidia drivers, so i might have to do the 388.30 update again soon, as i really want the new OCR update.

 

[CylonSurfer]

As others have said, Windows Update is now forcing driver updates (which is really bad imo) and forces the broken NVidia 388.13 to Win 10 PCs. I rolled back but Windows Update still re-installs 388.13, once even while I was playing Elite!!! Which it really didn't like as you would imagine. The only fix I could find was to upgrade to 388.33, which is much better but still not perfect.... MS have really dropped the ball with forcing driver updates onto home users... its a royal up.

 

[NeilF]

As others have said, Windows Update is now forcing driver updates (which is really bad imo) and forces the broken NVidia 388.13 to Win 10 PCs. I rolled back but Windows Update still re-installs 388.13, once even while I was playing Elite!!! Which it really didn't like as you would imagine. The only fix I could find was to upgrade to 388.33, which is much better but still not perfect.... MS have really dropped the ball with forcing driver updates onto home users... its a royal up.

This is reassuring in that at least the problem I was getting is explainable. So the Windows Update put on drivers which were causing the issue, and then me (by sheer chance and trying to fix things) apply the latest NVidia drivers helped resolve/improve the matter.

And it's interesting you mention these latest drivers (388.33?) are not perfect? ie: Are there still know issue being caused by these?


TBH, I'm bemused how video drivers are affecting the OR? From my perspective it almost felt like the sensors were getting confused in a few positions as I moved my head left/right and were therefore mis-calculating the angle of my head, hence me getting a couple of frames at the wrong angle etc... But if it was the NVidia drivers goodness knows what was going on! Maybe there's VR rendering related routines in the NVidia drivers which were mis-behaving!?

 

[Wasp0]

As others have said, Windows Update is now forcing driver updates (which is really bad imo) and forces the broken NVidia 388.13 to Win 10 PCs. I rolled back but Windows Update still re-installs 388.13, once even while I was playing Elite!!! Which it really didn't like as you would imagine. The only fix I could find was to upgrade to 388.33, which is much better but still not perfect.... MS have really dropped the ball with forcing driver updates onto home users... its a royal up.

You can (Within a certain time) roll back win 10 Autumn update to get you back how you where, then stop M$ from forcing this update on you. Well at least postpone for 365 days, hopefully by then they will have sorted their biowaste out and fixed it. Windows will then update again after, which will bring down the dreaded Nvidia 388.13 AGAIN, but you simply then roll back this driver to the one before 388.13 (Not sure of the number but it is 385 or something like that. Then stop windows from downloading 3rd party updates, and take the tick out of Nvidia's auto download and install.

Thanks M$ and Nvidia for destroying millions of gamers PC's with your puerile attempt at an upgrade. Luckily it is recoverable, but this process is not easily found and stopping the dreaded 'Forced upgrades' is even less easy to instigate/find.

M$ YOU SUCK BIG STYLE!!

 

[Wasp0]

Neil, Nvidia 388.33 driver did fix the stuttering issue for a lot of people, but for others it is still there (Me included), thats why i am on still 385.79

Try it and if you do still get milder stuttering then find the driver before the dreaded 388.13 (Think it is 385.79) and roll back to that, do a clean install and not custom install which will keep some of the later driver bits in it!



EDIT: Just looked it up and the reliable driver i am on is from September 2017 385.79 can be found here..... http://www.nvidia.com/drivers/beta

 

[NeilF]

Neil, Nvidia 388.33 driver did fix the stuttering issue for a lot of people, but for others it is still there (Me included), thats why i am on still 285.** (Or number defo begins with a 2 something).

Try it and if you do still get milder stuttering then find the driver before the dreaded 388.13 (Think it is 285.**) and roll back to that, do a clean install and not custom install which will keep some of the later driver bits in it!

Well the update to the latest update made a huge difference to the stutter. Before just moving my head left and right at almost any speed, I could get it almost every time to a significant degree. After the update I'd say its nigh on 99+% perfect. Possible as good as ever. As I said I may now just be looking for any stuttering when turning my head where before I wasn't. So I may be detecting the odd tiny stutter now that I had before...

It really was a painful few hours trying to work out what was up. Moving sensors. Trying different USB slots etc etc... Calibrating over and over...

Just wish I'd known about the driver issue from the outset. Why didn't Oculus send out an email!!!

 

[CylonSurfer]

And it's interesting you mention these latest drivers (388.33?) are not perfect? ie: Are there still know issue being caused by these?

Yeah, the drivers are better but not perfect, pre-388.13 I had no issues of this nature and while 388.33 is miles better than 388.13 I still notice the occasional glitch from time to time. I'd stick with the 385.XX drivers if I had the option as they were miles better than either 388.13 or 388.33 but sadly they are re-installed on Win 10 1709 no matter what Windows updates settings are disabled.

 

[NeilF]

....while 388.33 is miles better than 388.13 I still notice the occasional glitch from time to time.

Well, that seems to backup my limited experience so far...

Again, I'd love to know why Oculus didn't sent an email out informing folks of this issue.

 

[Wasp0]

Yeah, the drivers are better but not perfect, pre-388.13 I had no issues of this nature and while 388.33 is miles better than 388.13 I still notice the occasional glitch from time to time. I'd stick with the 385.XX drivers if I had the option as they were miles better than either 388.13 or 388.33 but sadly they are re-installed on Win 10 1709 no matter what Windows updates settings are disabled.

I used this methord ( http://www.itprotoday.com/windows-server/stop-automatic-driver-updates-windows-10) to stop M$ from downloading the unwanted Nvidia 388.13 (and other 3rd party driver updates) and so far it has left me on 385.79!!

 

[Wasp0]

Well, that seems to backup my limited experience so far...

Again, I'd love to know why Oculus didn't sent an email out informing folks of this issue.

Not an excuse Neil and no way defending OR, but it was on their forum, but then you have to know what caused this stuttering, know about the forum, know how to get there, when an email would have...............

 

[vic]

funny ,windows fall update did not update my graphics drivers. I wonder why it did so to some and not others?!

 

[NeilF]

funny ,windows fall update did not update my graphics drivers. I wonder why it did so to some and not others?!

I believe I was on an old(er) version as I didn't take the option to upgrade the video drivers last time I was notified.

Were you old old/new drivers?

 

[Alec Turner]

Just stumbled upon this thread (wish I'd found it sooner, been struggling with unwanted GFX driver updates suddenly appearing at the weekend) ... anyway, people here are talking about 388.33 but the newest I've managed to find (for GTX 1080) is 388.31. I figured, seeing as I'm being forced to update (or so it seemed at the time) I may as well get the latest (I guess I'll have to do so for Rift 2.0 anyway) so I'm puzzled now as to whether I've achieved that.

http://www.nvidia.co.uk/download/driverResults.aspx/126969/en-uk

 

[Wasp0]

Just stumbled upon this thread (wish I'd found it sooner, been struggling with unwanted GFX driver updates suddenly appearing at the weekend) ... anyway, people here are talking about 388.33 but the newest I've managed to find (for GTX 1080) is 388.31. I figured, seeing as I'm being forced to update (or so it seemed at the time) I may as well get the latest (I guess I'll have to do so for Rift 2.0 anyway) so I'm puzzled now as to whether I've achieved that.

http://www.nvidia.co.uk/download/driverResults.aspx/126969/en-uk

Nope 388.31 is the latest driver. it has fixed quite a lot of stuttering but not mine so i am on 385.79, which for me is sweet. Hope OR 2.0 is not going to make me get 388.31, otherwise i face a bit of a dilemma

 

[dape]

Win10 xx me as well. Tried several methods to prevent it from updating third party drivers but it did not work. Installed 388.31 which runs fine for now.

 

[CylonSurfer]

I used this methord ( http://www.itprotoday.com/windows-server/stop-automatic-driver-updates-windows-10) to stop M$ from downloading the unwanted Nvidia 388.13 (and other 3rd party driver updates) and so far it has left me on 385.79!!

Yeah I did try that, but after selecting 'No, let me choose what to do' the other 2 options and checkbox do not appear for me. I'm using Windows 10 Home Edition v1709, no idea if that is why. I'd go back to 385.79 in a flash if Windows didn't keep updating it.