bad VR issue, Rift S

[Lange_666]

The issues most of you are experiencing are indeed tied to the shitty V17 latest Oculus builds. (I teach electrical engineering and am a developer. I am using the SDK to build a SLI patch currently.) There are several methods for making sure that Oculus does not auto update (google em).

 

 

Any option on downgrading the current V17 to something like V15 or so?

[dburne]

Maybe try the beta Oculus build ?

 

There is no beta build currently , version 17 is on release channel now.

No issues with 17 on my end in all my games.

[30mikemike]

Starting to think it may not be the Oculus software as the last update was something like the 18th of April i think. I’ve been on DCS many times since then and it was fine. Not checked to see if it’s stuck in a Windows update cycle yet but I will. Failing that I’ve no idea!

Probably sounds ridiculous but could it be the GPU on the way out? Although I’ve just tried it without the Rift and on the monitor and it was absolutely spot on...

Edited May 18, 2020 by 30mikemike

[Lange_666]

@Aurelius: Thanks in advance.

I know it's possible to block the updates, i did a quick search after the 1st update to V17 (there was already a 2nd one), found something with 2 empty text files but lack of time prevented me from installing it. Later today i'm gonna search a bit further.

@dburne: Softwarewise in DCS i don't have an issue either with V17 but must say i only had a short 5 min session with no AI (wanted to test something in my F/A-18 HOTAS profile). I don't have the stutters that 30mikemike has. Only the connection crap on startup that's poppin' up again very regulary since V16.

[stormrider]

Starting to think it may not be the Oculus software as the last update was something like the 18th of April i think. I’ve been on DCS many times since then and it was fine. Not checked to see if it’s stuck in a Windows update cycle yet but I will. Failing that I’ve no idea!

Probably sounds ridiculous but could it be the GPU on the way out? Although I’ve just tried it without the Rift and on the monitor and it was absolutely spot on...

 

 

I think it is very unlikely that its a GPU failing. For me, its a software related issue for sure. Its always a combination of bad software and windows rubbish. Back in 2016 I started having stutters in Assetto Corsa for just no reason. Reinstalled windows 10 and they were gone. Before that I had tried absolutely everything to no avail. Also, if you're stuck with bad drivers now, dont block their update, do the opposite and try to get out of them asap.

[30mikemike]

I think it is very unlikely that its a GPU failing. For me, its a software related issue for sure. Its always a combination of bad software and windows rubbish. Back in 2016 I started having stutters in Assetto Corsa for just no reason. Reinstalled windows 10 and they were gone. Before that I had tried absolutely everything to no avail. Also, if you're stuck with bad drivers now, dont block their update, do the opposite and try to get out of them asap.

 

Yeah you're right, I think if it was the GPU failing I'd notice something wrong when in DCS on the monitor. I'll just have to wait for more updates, both Windows & Oculus. I'll give it another go tonight, maybe after a day being switched off it might've fixed itself!

[Lange_666]

In the Oculus/Support/oculus-drivers/ install directory there's a file called oculus-driver.exe.

You might give that one a try. It re-installs the Oculus drivers.

 

I also found that when there's a connection problem at startup of the Rift-S, running this file can cure it too. It also stops and restarts the Oculus service.

Edited May 18, 2020 by Lange_666
Dams those extra lines when you add a return....

[30mikemike]

In the Oculus/Support install directory there's a file called oculus-driver.exe.

You might give that one a try. It re-installs the Oculus drivers.

 

I also found that when there's a connection problem at startup of the Rift-S, running this file can cure it too. It also stops and restarts the Oculus service.

 

That’s great, I’ll give that a try later and see if it sorts my issue...:thumbup:

[Lange_666]

Also, the Oculus Debug Tool (to be found in Oculus/Support/oculus-diagnostics/ ) will give you the option to start and stop de Oculus service without going through the Windows Service.

[30mikemike]

Also, the Oculus Debug Tool (to be found in Oculus/Support/oculus-diagnostics/ ) will give you the option to start and stop de Oculus service without going through the Windows Service.

 

 

Unsure what you mean by stopping the Oculus Service? I get confused with the things like Tray Tool, De-Bug tool and Oculus Service. Is the Service something that can be stopped or is running all the time?

 

 

Sorry for the daft questions.....:pilotfly:

[Lange_666]

If done nothing extra after installation, the Oculus Service runs always in the background and is started after booting your PC, together with all the other services (Windows Services etc...). I keep mine running as clean as possible so i change the startup of those services that i don't need into manual, that way they start when starting the software instead of at boot.

You can do that too with the Oculus Service. But if you didn't, it's automatically started when you boot your PC, no problem.

In order to get a faulty USB connection running again they always say un-plug and re-plug the Oculus USB but for that i need to dive under my desk so i looked for another way. Stopping the Service and starting it again does the same thing without the need to un-plug / re-plug the USB each time.

TrayTool you can compare with the nVidia settings tool but then for Oculus VR. You can define a profile setting per game.

Debug Tool is what the name says, gives you a few options to get some more info from your Rift-S and gives you a few options to display info in the "HUD" while running a game in VR. It also offers to stop and start the Oculus Service.

[30mikemike]

If done nothing extra after installation, the Oculus Service runs always in the background and is started after booting your PC, together with all the other services (Windows Services etc...). I keep mine running as clean as possible so i change the startup of those services that i don't need into manual, that way they start when starting the software instead of at boot.

You can do that too with the Oculus Service. But if you didn't, it's automatically started when you boot your PC, no problem.

In order to get a faulty USB connection running again they always say un-plug and re-plug the Oculus USB but for that i need to dive under my desk so i looked for another way. Stopping the Service and starting it again does the same thing without the need to un-plug / re-plug the USB each time.

TrayTool you can compare with the nVidia settings tool but then for Oculus VR. You can define a profile setting per game.

Debug Tool is what the name says, gives you a few options to get some more info from your Rift-S and gives you a few options to display info in the "HUD" while running a game in VR. It also offers to stop and start the Oculus Service.

 

 

 

 

Ah that's great, thanks for that. More clear now as to what they do. To be fair I've used TrayTool but since these problems a couple of days ago I deleted it, ran DCS and it appears exactly the same anyway? Pixel Density set in game gave the same results.

Any services you'd recommend to stop or at least put into manual?

[Lange_666]

You can find a list to start with over at Black Viper's webite.

Compared to Windows XP or Windows 7 there aren't a lot of services to put to manual (but do have a look). I mostly look at those that are run automatically for installed software that i don't let run at boot because i don't need it.

[30mikemike]

You can find a list to start with over at Black Viper's webite.

Compared to Windows XP or Windows 7 there aren't a lot of services to put to manual (but do have a look). I mostly look at those that are run automatically for installed software that i don't let run at boot because i don't need it.

 

Spot on, thanks. Not that I’ve had any problems before but it’s worth looking at. Fingers crossed this latest issue I’ve got will get sorted....

[30mikemike]

Still the same tonight and no Windows updates going on. Might be time for a Reverb I think.....

[Lange_666]

Does it also stutter in other games beside DCS?

If that's not the case, your Rift-S is not the problem and you probably end up with the same stutters on your Reverb.

[30mikemike]

Does it also stutter in other games beside DCS?

If that's not the case, your Rift-S is not the problem and you probably end up with the same stutters on your Reverb.

 

I’ve not tried any other game in VR as the only thing installed on my machine is DCS. I tried it tonight again on the monitor with the settings on high, SSAA x2 and MSAA x2 etc etc and it was absolutely glass smooth. And that’s on my Asus 1440p monitor so it’s definitely pointing to a VR specific issue. It’s literally doing my head in!

[30mikemike]

Does it also stutter in other games beside DCS?

If that's not the case, your Rift-S is not the problem and you probably end up with the same stutters on your Reverb.

 

I’m going to borrow my mates Rift-S and see what that’s like first.

[dburne]

I’ve not tried any other game in VR as the only thing installed on my machine is DCS. I tried it tonight again on the monitor with the settings on high, SSAA x2 and MSAA x2 etc etc and it was absolutely glass smooth. And that’s on my Asus 1440p monitor so it’s definitely pointing to a VR specific issue. It’s literally doing my head in!

 

Don't use SSAA in VR, only the MSAA.

[30mikemike]

Don't use SSAA in VR, only the MSAA.

 

I don’t have SSAA on in VR mate, only MSAA x2.

[30mikemike]

Just a thought but I’ve tried thinking what I’ve done over the past week or so and the only thing I can think of is revert back the Nvidia driver, then reverted forward again and then back. Always select the clean install but maybe this has done something? Anyone with a better knowledge of it might know? Possibly left registry files and knackered things up a bit?

Edited May 18, 2020 by 30mikemike

[Lange_666]

Do you mean the clean install in the nVidia option or did you go the DDU way first?

Display Driver Uninstaller: latest version: https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

 

 

Recommended usage

 

• You MUST disconnect your internet or completely block Windows Update when running DDU until you have re-installed your new drivers.
  
• DDU should be used when having a problem uninstalling/installing a driver or when switching GPU brand.
  
• DDU should not be used every time you install a new driver unless you know what you are doing.
  
• DDU will not work on network drive. Please install in a local drive (C:, D: or else).
  
• The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best.
  
• If you are using DDU in normal mode, Clean, reboot, clean again, reboot.
  
• Make a backup or a system restore (but it should normally be pretty safe).
  
• It is best to exclude the DDU folder completely from any security software to avoid issues
  

[30mikemike]

Do you mean the clean install in the nVidia option or did you go the DDU way first?

Display Driver Uninstaller: latest version: https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

 

 

Recommended usage

 

• You MUST disconnect your internet or completely block Windows Update when running DDU until you have re-installed your new drivers.
  
• DDU should be used when having a problem uninstalling/installing a driver or when switching GPU brand.
  
• DDU should not be used every time you install a new driver unless you know what you are doing.
  
• DDU will not work on network drive. Please install in a local drive (C:, D: or else).
  
• The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best.
  
• If you are using DDU in normal mode, Clean, reboot, clean again, reboot.
  
• Make a backup or a system restore (but it should normally be pretty safe).
  
• It is best to exclude the DDU folder completely from any security software to avoid issues
  

 

The clean install route is what I select every time when installing new drivers. What’s concerning me though is the drivers I’ve installed over the past week or so. I reverted back to the 442.19 and another and then back to the latest so I’m thinking maybe doing that has caused this issue. I might be wrong but it’s the only thing I can think of that I’ve done.

I’m thinking the DDU cleanup is worth a shot but I don’t want to mess things up completely...

[Lange_666]

It will not mess things up, just follow the steps.

Before you uninstall, download nVidia 436.30 (which performs nice on my system) so you have that at hand already for when the DDU has doen it's job. When it does, you are in Windows 10 with a standard videodriver. To prevent it downloading one for you be sure that you have unplugged yourself from the net and then install the 436.30 driver. In general, no need to update your nVidia beyond that one for now.

[30mikemike]

It will not mess things up, just follow the steps.

Before you uninstall, download nVidia 436.30 (which performs nice on my system) so you have that at hand already for when the DDU has doen it's job. When it does, you are in Windows 10 with a standard videodriver. To prevent it downloading one for you be sure that you have unplugged yourself from the net and then install the 436.30 driver. In general, no need to update your nVidia beyond that one for now.

 

Thanks mate, appreciate your help. I’ll give it a go after work tomorrow and fingers crossed it’ll sort things. I’ll let you know....thanks again.