Game Ready Driver WHQL 465.89 download & discussion

Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by valorex, Mar 30, 2021.

  1. morrowindmemes

    morrowindmemes New Member

    Messages:
    1
    Likes Received:
    0
    GPU:
    GTX 1650Ti 4Gb
    Hey, anybody in here also has Vulkan issues like me on this driver? At my end i've encountered issues at RDR2 and any other title that uses Vulkan. I'm not certainly sure but the problem is that games can't detect any device that use Vulkan which is wrong as my GPU (1650Ti) has the Vulkan capabilities but as i said i'm not certainly sure about this. The only solution i found for now is disable the Vega graphics from device manager and re-enable it. After that games run OK.

    And as a proof to my idea here is a log file entry when i try to use DXVK which is Vulkan injector for old titles that use D3D9 or similar:

    warn: DXVK: No adapters found. Please check your device filter settings and Vulkan setup
     
    Last edited: Apr 12, 2021
  2. Stormyandcold

    Stormyandcold Ancient Guru

    Messages:
    5,659
    Likes Received:
    345
    GPU:
    MSI GTX1070 GamingX
    I've rolled back and now Warzone is working with the last driver 461.92-desktop-win10-64bit-international-dch-whql
     
  3. Astyanax

    Astyanax Ancient Guru

    Messages:
    11,009
    Likes Received:
    4,074
    GPU:
    GTX 1080ti
    you have a vega apu in the system, this is a known issue with amd's current drivers due to introducing a broken vulkan layer.

    See https://github.com/KhronosGroup/Vulkan-Loader/issues/552 for workaround

    There is no issue with dx12 and these drivers on supported Release versions of Windows.

    Insiders on the other hand, have issues.
     
    morrowindmemes likes this.
  4. Stormyandcold

    Stormyandcold Ancient Guru

    Messages:
    5,659
    Likes Received:
    345
    GPU:
    MSI GTX1070 GamingX
    IMHO, that's important information which helps people. I don't see why there's any negativity needed. We are here to report our findings, regardless of which version of Windows we're using. The fact that an older driver works means the problem is still with the Nvidia driver, even if it's just a lack of support issue. The next driver I'm sure will fix these issues. IME, it's not a common problem that I've seen in over 2yrs of testing insider builds.
     

  5. Astyanax

    Astyanax Ancient Guru

    Messages:
    11,009
    Likes Received:
    4,074
    GPU:
    GTX 1080ti
    Aye, and I'm pointing out the distinction that matters here, Insider vs Released/Final build users.

    Nvidia isn't actively developing(or testing) the GRD on Insider builds and are using the 19041.xxx version of the WDK/Toolchain for development, so only 1904x users can expect the driver to work properly.
    Insider builds are being built with Preview/Non Final Visual Studio editions and the toolchains they provide, and drivers for those insider builds are too as thats how you get access to the new driver model features.

    That said, the driver will work fine for anyone who prefers not to use GFE, and those who disabled the offending settings.
     
  6. Stormyandcold

    Stormyandcold Ancient Guru

    Messages:
    5,659
    Likes Received:
    345
    GPU:
    MSI GTX1070 GamingX
    I don't think that's true either. Nvidia work on insider drivers too, I don't see any reason why that would've stopped. My bet is they're fully onboard with insider builds and keep up with it.
     
  7. Astyanax

    Astyanax Ancient Guru

    Messages:
    11,009
    Likes Received:
    4,074
    GPU:
    GTX 1080ti
    The thing that comes up here is Branching and Forks.

    There is a heavily scrutinised fork that nvidia has for Insiders testing new features that requires the WDK of the Insider build to achieve the driver model level they are targetting, this is presently 470 and released under the WSL developer branch.

    There is the GRD fork that is rapid development for game optimizations and fixes, this Fork then has its own subtree's (Main, Bugfix and Hotfix) that you will see from time to time depending on how it was released.

    You can have Main xxx.70-0 get followed up by bugfix xxx.70-6, (both are completely WHQL but based on xxx.70) and then get Hotfix xxx.70-9 which has 3 more changes on top of xxx.70-6, but its in the hotfix branch because it doesn't have a normal WHQL signature (attestation signed instead)

    At some point, the Insider fork get is rebased, introduced into its own family and fixes from the GRD's so far are merged into it, with testing to see if any newt issues arise.


    Then..... theres GFE.

    GFE is Release and Beta branches, nobody is testing to make sure it works on Insider builds until Microsoft announces that a specific build has been signed off as RTM, this build then sits and bakes for a bit for a few months for driver vendors to make any corrections and fixes, whilst Microsoft usually goes from 10.xxxxx.Y and by the time its pushed on users its usually either got YY or YYY bugfix versioning.

    the WHQL testkit run against drivers to check for issues is also specific to the build of WDK the driver was produced with (and honestly, the testkit is lacking in a few scenario's and needs updating)
     
  8. tsunami231

    tsunami231 Ancient Guru

    Messages:
    11,974
    Likes Received:
    893
    GPU:
    EVGA 1070Ti Black
    Eh? they have four verisons of drivers? Fork branches? what ever you want to call it?
     
  9. Astyanax

    Astyanax Ancient Guru

    Messages:
    11,009
    Likes Received:
    4,074
    GPU:
    GTX 1080ti
    More than 4, i didn't even include Studio, Vulkan Dev, new hardware dev, etc.
     
  10. tsunami231

    tsunami231 Ancient Guru

    Messages:
    11,974
    Likes Received:
    893
    GPU:
    EVGA 1070Ti Black
    seem like kinda stretching the dev to much but ok, Do i even know to know how many branchs/forks of windows 10 MS has there dev's working on? o_O
     

Share This Page