🛈 Announcement
Greetings! The Division forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #1

    Suggestion : Fix DX12 for Nvidia users

    There are still many people like me who are experiencing random lockups using Nvidia hardware in combination with the DX12 renderer. This has been a ongoing and long-term issue , of which Ubi stated they were working with Nvidia on a fix. But from what i've gathered, this was months (if not longer) ago. And we haven't heard anything since.

    Can we please get a confirmation that you guys are still working on this? or should we just stop trying things and use the inferior DX11 instead?

    The game runs so much better on DX12 on Nvidia that it's really a shame this does not work properly.

    Btw , for most people , the so called fixes (dpi settings, scaling, windowed/fullscreen, fps limits) do not work. DX12 + Nvidia in this game is broken. and if you are actually
    using it and it's stable for you , that's fantastic. enjoy it. but for the majority , it's a complete disaster.
     1 people found this helpful
    Share this post

  2. #2
    Yeah dx12 performance fps-wise was amazing when I first started playing. Then I realized that the reason I was crashing every 40'ish minutes were due to using dx12 and hopped over to dx11.

    Since then I can count my crashes on one hand and I'm almost at 800 hours.
    I miss those 20-30 extra fps though.
     1 people found this helpful
    Share this post

  3. #3
    Yeah, it would be great if this could be adressed. Both me and a friend have recurring freezes when playing in DX12 mode.
     1 people found this helpful
    Share this post

  4. #4
    No reply from anyone yet who can pass this on?

    I admit i'm new here but support seems a bit lacking...
    Share this post

  5. #5
    WrecK3rr's Avatar Senior Member
    Join Date
    Sep 2019
    Location
    Chillin w/ Morozova
    Posts
    1,597
    Originally Posted by fredspekvet Go to original post
    No reply from anyone yet who can pass this on?

    I admit i'm new here but support seems a bit lacking...
    Hundreds of threads running on this issue already since launch.
    So I'm afraid you'd have to get in line buddy.
     1 people found this helpful
    Share this post

  6. #6
    SuspiciousPixel's Avatar Senior Member
    Join Date
    Apr 2012
    Location
    Chasing Keener
    Posts
    1,740
    You should try DX12 again with the new Nvidia drivers that will officially support WDDM 2.7 for Windows 10 20H1 2004. aka May 2020 update

    What WDDM 2.7 will do
    So the latest improvements coming to Windows 10 appears to be a new path through the WDDM layer to allow the gpu to have better control over it's own task scheduling. Among a few other things.

    - DXR 1.1: customizable API for RT cores which allow for physics, audio
    - WDDM 2.7: GPU can allocate memory form shader program (without ask CPU)
    - Hardware-accelerated GPU scheduling
    - Shader Model 6.5
    - Mesh Shaders
    - Variable Rate Shading integrated into DXR and Temporal Frame Reconstruction
    - DirectX 12 Sampler Feedback: Texture Streaming, Texture-Space Shading
    - DirectX 12 Video Protected Resource Support

    This also appears to have improved black screening and issues with multiple monitors of different refresh rates.
    Official support with come with a Game Ready Driver update next month.

    https://forums.guru3d.com/threads/nv...7#post-5793595

    This may not be the solution for DX12 crashes but hopefully the improvements, GPU scheduling, new Windows update it could work as intended.
    P.S The devs seem to have given up on DX12 and High CPU issues several months ago so good luck getting any proactive response that isn't "We are looking into it"
     1 people found this helpful
    Share this post

  7. #7
    Originally Posted by SuspiciousPixel Go to original post
    You should try DX12 again with the new Nvidia drivers that will officially support WDDM 2.7 for Windows 10 20H1 2004. aka May 2020 update

    What WDDM 2.7 will do


    Official support with come with a Game Ready Driver update next month.

    https://forums.guru3d.com/threads/nv...7#post-5793595

    This may not be the solution for DX12 crashes but hopefully the improvements, GPU scheduling, new Windows update it could work as intended.
    P.S The devs seem to have given up on DX12 and High CPU issues several months ago so good luck getting any proactive response that isn't "We are looking into it"
    This is useful. Thank you for your reply. I have installed the may 2020 update and the 450.99 driver , and I have set windows 10 to Hardware -accelerated GPU scheduling . I will now test the game under DX12 mode to see if things have improved at all, and will let you guys know soon.
    Share this post

  8. #8
    WrecK3rr's Avatar Senior Member
    Join Date
    Sep 2019
    Location
    Chillin w/ Morozova
    Posts
    1,597
    Originally Posted by SuspiciousPixel Go to original post
    You should try DX12 again with the new Nvidia drivers that will officially support WDDM 2.7 for Windows 10 20H1 2004. aka May 2020 update

    What WDDM 2.7 will do


    Official support with come with a Game Ready Driver update next month.

    https://forums.guru3d.com/threads/nv...7#post-5793595

    This may not be the solution for DX12 crashes but hopefully the improvements, GPU scheduling, new Windows update it could work as intended.
    P.S The devs seem to have given up on DX12 and High CPU issues several months ago so good luck getting any proactive response that isn't "We are looking into it"
    That's Cool. I'll wait for the official release as I'm not facing any crashes at this time.
    Share this post

  9. #9
    I have maanged to play for around 4 hours now using DX12. So far I have yet to see it crash.

    Before the windows may update and the beta 450.99 drivers, the game would crash between 1 minute and 30 minutes play time, so at the very least , it has been massively improved. Will keep you guys updated when I have played more tomorrow.
     1 people found this helpful
    Share this post

  10. #10
    I hope these new drivers work, got same problem as described here. Please let us know if they work for the long run.
    Share this post