🛈 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. #11
    Also have the same issue since June 22 when the new driver ( 471.11 ) was released. Impossible to play could you please keep us updated on the glitch so we can get back to playing as soon as possible
    Share this post

  2. #12
    yep same here. Ubi get good at your job son!
    Share this post

  3. #13
    Imagine_Brata's Avatar Senior Member
    Join Date
    Apr 2017
    Location
    Sweden
    Posts
    713
    Originally Posted by Joker.729 Go to original post
    My friend and I started having this same issue today. Both Nvidia cards and the latest drivers (471.11). Need to know if this is a known issue for this driver or another malfunction from Ubisoft?
    There are several games that have the same problem with the new Nvidia driver. so i think nvidia is working on fixing the graphics bug
    Share this post

  4. #14
    Imagine_Brata's Avatar Senior Member
    Join Date
    Apr 2017
    Location
    Sweden
    Posts
    713
    Originally Posted by Ubi-Mercury Go to original post
    Hey everyone! I'm sorry to hear you all have experienced a visual issue in-game. Could you all please try out these troubleshooting steps to see if they help?
    The driver is causing the problem. See here in the Nvidia forum. Lots of people have problems with new Driver 471.11. in both games and programs
    https://www.nvidia.com/en-us/geforce...eleased-62221/
    Share this post

  5. #15
    Thank god I found this forum post.. I was thinking my graphics card was dying because of all the random **** happening. Models being weird, textures being blocky, colors distorting, etc all look like a dying graphics card. But at least it seems to be isolated to Division 2.
    Share this post

  6. #16
    I reinstalled division and it seems to be running much more smoothly. This could be a fix for people experiencing this issue.

    Edit: Nope.. It's back. Reinstalling did not fix it.
     1 people found this helpful
    Share this post