ASW off is Left CTRL/numpad 1.
ED now unplayable in VR - 90% of the time
- Thread starter [VR] Mad Mike
- Start date
ASW off is Left CTRL/numpad 1.
I have had the same problems with elite for ages now and have just changed back nvidea driver to 384.94 as suggested by Benji85 in another post.
This has sorted my stuttering out,it was becoming unplayable with asw on or off.
This does mean i think that you will not be able to use the rift core 2 stuff but at least you can play the game again (this has been ages for me , i dont play any more i just tweak)
384.94 works for me, i'd be inerested to know anyone elses results if you care to try it.
This has sorted my stuttering out,it was becoming unplayable with asw on or off.
This does mean i think that you will not be able to use the rift core 2 stuff but at least you can play the game again (this has been ages for me , i dont play any more i just tweak)
384.94 works for me, i'd be inerested to know anyone elses results if you care to try it.
I'll definitely give it a try
Winner, Winner.
The last Windows update re-enabled that stupid game bar nonsense. Thanks!
I loaded up the above mentioned 384 drivers last night and it appeared to be considerably more stable. Didn't even consider that the recording feature may have turned back on, I'll have to check that.
![[VR] Frank_G](https://forums-cdn.zaonce.net/data/avatars/m/59/59394.jpg?1553527111){kind=avatar}
Everything fine here, running an Oculus Rift on an an i7 4790K Rig with a 1080ti founders edition and 32 Gigs of RAM.
I had slight problems when 3.1 was released (light studders now and then, but far from frequent, annoying or making the game unplayable), but it became better with each following patch.
I updated to the latest NVidia driver today and it got rid of the studders completely (did dock at 2 stations, jumped 1,600 ly and landed on a metallic and a rocky planet).
I had slight problems when 3.1 was released (light studders now and then, but far from frequent, annoying or making the game unplayable), but it became better with each following patch.
I updated to the latest NVidia driver today and it got rid of the studders completely (did dock at 2 stations, jumped 1,600 ly and landed on a metallic and a rocky planet).
![[VR] Mad Mike](https://forums-cdn.zaonce.net/data/avatars/m/27/27910.jpg?1553527108){kind=avatar}
i will check this out thanks.
MS are really out of order resetting preferences etc on updates!.
I find this thread interesting. I don't have a VR device, but I have a Tobii 4C eye tracker in use. Since a few weeks, I have to switch off the Tobii software (and thus not use the eye tracker), else I run into performance issues. Up to now, I thought this to be a Tobii problem (I updated the Tobii software recently, too) and have a ticket open there.
.
But if VR users also have performance issues, which read similarily (for me ED itself also only uses about 50% CPU, the rest is used up by the Tobii software), I wonder if there might be something whacky going on with the interface. As far as I understand, Tobii and Oculus use the same interface to provide info for the head/camera position. Unfortunately I don't know much about that interface, but it'd be interesting if somebody who knows more could say if some whacky stuff could happen there, which results in performance issues? (E.g., as a wild guess: the game could request data updates at an insanely high rate, forcing the software to recalculate and update their tracking position all of the time and thus clog up the CPU. )
.
Anyway, I can also be far off. It requires somebody with more understanding on the topic, to say if my issue is related or a pure coincidence.
.
.
But if VR users also have performance issues, which read similarily (for me ED itself also only uses about 50% CPU, the rest is used up by the Tobii software), I wonder if there might be something whacky going on with the interface. As far as I understand, Tobii and Oculus use the same interface to provide info for the head/camera position. Unfortunately I don't know much about that interface, but it'd be interesting if somebody who knows more could say if some whacky stuff could happen there, which results in performance issues? (E.g., as a wild guess: the game could request data updates at an insanely high rate, forcing the software to recalculate and update their tracking position all of the time and thus clog up the CPU. )
.
Anyway, I can also be far off. It requires somebody with more understanding on the topic, to say if my issue is related or a pure coincidence.
.
early days however i updated my geforce drivers and went into the new build last night and performance was flawless. was really nice to see it running as it should again 
checked my machine, all fans running, airflow and temps all good do that was not my issue.
checked my machine, all fans running, airflow and temps all good do that was not my issue.
Excellent. I’m going to copy you ! [yesnod]early days however i updated my geforce drivers and went into the new build last night and performance was flawless. was really nice to see it running as it should again
checked my machine, all fans running, airflow and temps all good do that was not my issue.
Version 399.07 ?
Flimley
dayrth
Volunteer Moderator
I'm not getting this issue. Played for two hours last night in various locations and no stutter at all (i7, GTX 970, Oculus Rift CV1). What is your supersampling setting? I find that I have to set this to less than 1 to get good performance, but that has always been the case for me and I have a lower spec video card than you. I didn't noticed any performance change with 3.0.
Last edited:
i just got the latest non beta driver from nvidia site so yeah i presume so (am on work pc now so cant double check)
As of yesterday it doesn't seem to be an issue quite like it was. I was even able to bump my graphics settings up just a bit. Definitely a marked improvement. I didn't realize there was a 399.x driver out, Im running the last 398.
I dusted off my DK2 and had a go with my Media PC which runs an i7 3770 and GTX970 and it was smooth enough in VR Medium however I noticed a lot of ship shake when docked, anyone else get this? Unless my tracker is playing up. It was fine (or maybe not noticeable) when flying however.
I wouldn't expect much from that driver.
Probably just to allow use for the upcoming RTX series of cards.