Comments Locked

32 Comments

Back to Article

  • damianrobertjones - Thursday, September 22, 2016 - link

    Yay! Let's hope that it installs Vulkan without asking me, again. /s
  • WithoutWeakness - Thursday, September 22, 2016 - link

    Why would you not want Vulkan? I understand not wanting something installed if you specifically uncheck the box during setup (I don't need 3D Vision drivers for my 2D monitor) but I'm more curious why you are looking to avoid Vulkan?
  • damianrobertjones - Tuesday, September 27, 2016 - link

    It's not that I have anything against Vulkan... I just want the OPTION to not install it. I don't really care other than that but at no point was I asked to install it.

    These companies should stop doing this stuff!
  • m16 - Friday, September 30, 2016 - link

    Your programs, all of them come with dozens of libraries, executables, services and files, and you're not privy about them. Even on Linux this is the case when you install software.

    Unless you run a secure box for something specific (In which you wouldn't be gaming to begin with), this is just pointless complaining.

    You can just turn around and uninstall vulkan after it is installed. Be outraged when you can't, or don't be at all when it is a part of the driver permanently and it is not published anywhere.
  • FriendFive - Thursday, September 22, 2016 - link

    I got this last night and it broke Fallout:New Vegas so I reverted to 368.81.
  • Mr Perfect - Thursday, September 22, 2016 - link

    Yeah, they broke New Vegas, Fallout 3 and Skyrim a couple versions back. The real kicker is the bug is now listed as a not-caused-by-our-drivers issue, so I guess they have no intention of fixing it.
    From the patch notes:
    [Windows 10][Bethesda Softworks games (Fallout 3, Fallout New Vegas, Skyrim)] Games crash when launched. [1802925]
  • Mr Perfect - Thursday, September 22, 2016 - link

    One of the nVidia staff commented on the bug on their forums. Guess it's MS's problem.

    ManuelGuzman: The new Windows 10 Anniversary Update had a specification change that required our display driver to output a different string from the previous drivers in the past. This has affected some games which were unfortunately developed with the assumption that the value would never change. We are working with Microsoft to find a solution. Drivers 368.81 and below are WDDM 2.0. R370 and higher drivers are WDDM 2.1.
  • wolrah - Thursday, September 22, 2016 - link

    That sounds like it's Bethesda's problem to me. If the spec doesn't say that string remains static, but Bethesda's games assume it does and break when it changes, that's 100% Bethesda's fault. This is just like when Vista came out and app vendors who were doing things they weren't supposed to claimed that Vista "broke" their apps when in reality it was just XP didn't strongly enforce the rules.
  • Mr Perfect - Friday, September 23, 2016 - link

    This is true.

    I'm just hoping that MS can do something, because Beth sure doesn't care. You have to apply community fixes even to get Fallout 3 running on 7.
  • HollyDOL - Friday, September 23, 2016 - link

    Bethesda is quite famous for their coding quality and they have some history. But at least they seem to improve over time... a bit. Arena couldn't be finished without patch at all and crashed alot. Daggerfall was a crash hell, but hey, at least it was possible to finish it (if you had holy patience with crashes).

    It shouldn't be that difficult for Bethesda to fix their junk (especially if it is just some string parsing thing as it seems).
    I am not sure I'd want system infested with things like

    if (executable == "skyrim.exe" || ...) magicString = "A" else magicString = "B"

    I know it sucks because pple want to play older games on newer systems, but from developer perspective, if you can't follow specs you should be destined to fail big time - especially because it forces other developers to waste time duct taping your crap. It's just too bad general public will often blame something that is not to be blamed at all - in this case majority will blame Windows 10 no matter whether it is the actual 'bad boy' just because it's cool to blame it for everything including bad harvest in summer 1773.

    So now it would be interesting to find out who exactly violated the specs - Microsoft, nVidia or Bethesda.
  • Michael Bay - Saturday, September 24, 2016 - link

    Gamebryo programmers back in 1999, most likely.
  • Konndoor - Friday, October 28, 2016 - link

    It is Microsoft's fault for not fixing the exception handling. They knew that people were playing these games that are better than most of their new ones. Nvidia is just following the guidelines. A patch might me made for each game but that will take time for coding and testing.
    This whole thing is setup to sideline these heavily modded masterpieces like Fallout with TTW and Dagwood Super packed Oblivion.
    Meanwhile, Skyrim Remastered can save the day. It is a done-before game that is pretty but shallow. The gameplay is cheap if only thrilling. Not even as complex as Oblivion with no dual-wielding. The whole affair is just sad corporate maneuvering towards upping the bottom line.
  • Konndoor - Friday, October 28, 2016 - link

    It's fixed. A modded fixed it. Use NVAC and it is at nexusmods.
  • Konndoor - Friday, October 28, 2016 - link

    NVAC fixes the crashing without downgrading or rolling back the driver. The patch is at nexus mods. So, don't bother getting an entire team to work on something a random modded and programmer added in his spare time.
  • Badgerboy1970 - Friday, September 23, 2016 - link

    I don't know if the crashing is supposed to be a universal problem because I was able to play Skyrim for about an hour last night with no crashes or any other issues at all. Currently using the Windows 10 64 bit with Anniversary update and GTX 1060 with the 372.90 drivers.
  • SeanJ76 - Friday, September 30, 2016 - link

    It's the driver no doubt in my mind, I noticed much lower frame-times with 372.90 driver.
  • Zak - Thursday, September 22, 2016 - link

    I can launch Skyrim and it runs but when I quit, Windows crashes to a black screen and I have to reset the PC. Maybe it's finally time to go back to Windows 7. I only use a PC for gaming and Windows 10 has been absolutely awful so far. In the few months I had more issues with games than in years of gaming on Windows 7.
  • Morawka - Thursday, September 22, 2016 - link

    blame lazy game dev's for the bug. not ms.. read the post above yours my Mr Perfect
  • kn00tcn - Friday, September 23, 2016 - link

    checking driver versions in a way that has been used for a decade then breaking many years after the game's release on a new OS (in fact a new update on a new OS) has nothing to do with lazy devs, what a lazy attack
  • Michael Bay - Saturday, September 24, 2016 - link

    One look at KILOMETERS LONG list of fixes on any community patch is enough to see that coding standards are definitely not for Bethesda.
  • Mr Perfect - Friday, September 23, 2016 - link

    With Skyrim you'll at least get a fixed copy on October 4th when Beth gives out the free HD remaster. It's Fallout 3 and New Vegas I'm concerned about, they're to old to get support.
  • eddman - Friday, September 23, 2016 - link

    IMO, fallout 3 and new vegas deserve proper remasters, or should I say remakes since they use Gamebryo engine and bethesda have moved to Creation engine. Still, it might not be that difficult given that Creation is basically a heavily updated Gamebryo.
  • ruthan - Saturday, September 24, 2016 - link

    Ha, ha.. Creation engine, is just new name for old Gamebryo stuff, they just bought Gamebryo license include the source code and continue working on old code base, only changed the name to look more fancy.
  • eddman - Saturday, September 24, 2016 - link

    What do you mean, exactly? That Creation is Gamebryo without any changes? As far as it's known, even though it's based on gamebryo, the code was rewritten in major ways here and there. It's not just a new name.
  • JKflipflop98 - Tuesday, September 27, 2016 - link

    LOL wut? It's the same Gamebryo engine with the same annoying bugs that have been there since Morrowind. The only thing "rewritten in major ways" was the graphics renderer. Everything underneath is still the same ol janky bowl of brown.
  • Michael Bay - Saturday, September 24, 2016 - link

    What a load of bullshit. 10 is at the very least as stable as 7 ever was.
  • HollyDOL - Sunday, September 25, 2016 - link

    My experience is the same. The only issue I had was with insider version almost 3/4 year before official release and it was fixed quite fast.
  • JeffFlanagan - Monday, September 26, 2016 - link

    He could be a zealot who just hates new things, but he may have a crappy PC, leading to a lot of problems that he mistakenly blames on Win 10, in which case your noxious post would be totally out of line.
  • kn00tcn - Friday, September 23, 2016 - link

    didnt this driver come out before amd's?
  • Galvin - Saturday, September 24, 2016 - link

    These caused a black screen during load screens in world of warcraft. Rolled back to an earlier driver fixed the issue.
  • SeanJ76 - Friday, September 30, 2016 - link

    This driver has its issues, clock speeds are all goofed up with this driver, I had to re clock my core clock higher with .90, also noticed worse frame-rates with .90. Rollbacked to .70 pretty much next day, everything is fine with .70 driver.
  • maincpa77 - Friday, May 12, 2017 - link

    find great walking dead road to survival hack tool on http://walkingdeadroadtosurvivalhack.com

Log in

Don't have an account? Sign up now