I don't know if it is just me, but when I downloaded and installed the latest NVidia drivers (not sure of version, but came out today) they appear to have broken Direct3D (where Elite Dangerous is concerned). I have go back to the previous drivers, and am able to play ED.
NVidia latest drivers break Rift VR
- Thread starter Hell Razor5543
- Start date
![[HJ]-RedRaven](https://forums-cdn.zaonce.net/data/avatars/m/67/67389.jpg?1553527112){kind=avatar}
Well you can't escape the Oculus Home and firmware updates, but you can avoid the nVidia driver update until some others have tested it 'in the wild'!.
I'm using the just-superceded nVidia drivers 368.69 over the past week without issue. I haven't tried the new 369.81, but will avoid now for a bit.
Best policy is to update drivers every once in a while, not every point release that pops up.
I'm using the just-superceded nVidia drivers 368.69 over the past week without issue. I haven't tried the new 369.81, but will avoid now for a bit.
Best policy is to update drivers every once in a while, not every point release that pops up.
Well, it's a hack, but you can avoid the Oculus updates. I've blacklisted all the Oculus .exe's in my firewall precisely for fear that an update will break the DK2 compatibility. I'm on Oculus 1.5 and actually, I'm using the DK2 clone, Deepoon HMD which has DK1 and DK2 modes.
Oculus home starts up fine and I can play ED, Alien Isolation and Skyrim with no problems, but of course, I have an error message in Oculus Home saying it can't connect to Oculus server. Not an issue for me since I don't use any of the features of OH. I realize some have purchased games through OH and probably can't use this hack or else they may not be able to play their games.
I've also cloned my SSD in case something tragic happens I can revert back to my previously working state.
YMMV
Last edited:
Zero issues for me as well. I've updated to latest Nvidia and Oculus firmware/software.
No problems my end either with either download. But regarding the memory leak I'm still in 2 minds if it's ED or oculus causing it .My system was up to 7 gb when I shut ED down biggest drop was oculus in task manager so who knows lol
OK, that might be my system then. I am running 8.1 Pro (64 bit), Rift DK2 and the latest Oculus software.
I haven't got my dk2 as borrowed it to a friend otherwise I could test and rule out the oculus out. But I'm sure I've read somewhere that someone had the new sdk and it worked fine with the dk2. Sorry I could not help more. And I'm still not convinced by win 10 should of stuck with 8.1
updated newest Drivers from nvidia today and the oculus Software last night... 1080/6700k/16gigs
no new issues, runs fine - just the ususal Memory leak thing
no new issues, runs fine - just the ususal Memory leak thing
Repped! Great ideas - that's a useful hack for DK1/2 owners who might not know how to avoid the eventual update that breaks their support (if that happens).
I'd suggest writing it up in a bit more step by step detail and getting it stickied in here - it'd definitely be a help to some!
Already a couple of members on this forum have complained that their DK2's lost compatibility with the Oculus 1.5 update. Apparently, they just fired up OH and it auto-updated and and their DK2's started acting up and they could no longer get ED to work. Can't really say what happened, as in each of those cases, other members quickly followed up by saying they were having no problems with 1.5.
I certainly wouldn't mind writing it up. It's really a simple process, assuming your firewall has that feature. I'm not sure how much different the process would be for each individual firewall though. :\
OK, so I still have a problem. I have recently switched to Windows 10 Pro (64bit), and upgraded to a CV1, but with the latest NVidia drivers I got the same Direct3D error. Using the earlier drivers allowed me into the game.
See FD advisory on top of the page (under DRIVERS)
https://support.frontier.co.uk/open.php?jira_only=1
https://support.frontier.co.uk/open.php?jira_only=1
Ahh so SLI only issue according to that - would explain many (me included) not seeing it
And it would explain why I do see the problem (as I have a pair of Asus Strix GTX 970 cards). I also have seen an issue with Geforce Experience not correctly picking up the two cards, and installing drivers for 1000 series cards (and then not being able to optimise games). Manually installing the right drivers (but one down from the ones causing issues) has got my PC working properly.
Do SLI users not use Google to see if their setup has issues with a game they intend to run? A simple search like "Elite dangerous VR and sli" exposes the fact that sli is not supported in VR and causes issues in ED. I have never installed a second card and even I have known for months that this is the case. SLI has been discussed a lot in this VR forum.
Given multiple gpu's is a rather high end hardware effort by those who use it and that , depending on how well it is supported, it can result in good and bad implementations and experiences, I would have thought a little homework would be standard operating procedure for such hobbyists.
I am not saying sli is a bad choice. It may well be useful depending on what games you play and what level of graphics your shooting for. It may suit one's desire to extend the life of their graphics system. However to quote Scotty "The more they overthink the plumbing, the easier it is to stop up the works"
Given multiple gpu's is a rather high end hardware effort by those who use it and that , depending on how well it is supported, it can result in good and bad implementations and experiences, I would have thought a little homework would be standard operating procedure for such hobbyists.
I am not saying sli is a bad choice. It may well be useful depending on what games you play and what level of graphics your shooting for. It may suit one's desire to extend the life of their graphics system. However to quote Scotty "The more they overthink the plumbing, the easier it is to stop up the works"