🛈 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
    Try clearing directx shader cache files. Has helped me in the past.
    Share this post

  2. #12
    Originally Posted by WickedBadz Go to original post
    Stop using directx12 and 99% of your crashes and issues will go away.
    Not true at all.
    Share this post

  3. #13
    Merphee's Avatar Volunteer Moderator
    Join Date
    Nov 2016
    Location
    Discord: Merphee#2325
    Posts
    3,821
    Originally Posted by Adze. Go to original post
    Maybe you guys should let me login to your PC using Teamviewer and have a go at fixing your issues for a small fee of course.


    With the amount of Jim Browning videos I've seen....

    ...there's clearly nothing that can go wrong with this!
    Share this post

  4. #14
    Originally Posted by Bursucul Go to original post
    Not true at all.
    Actually it is. Directx12 is a joke in Division.
    Share this post

  5. #15
    Its not a memory leak, it is a simple issue of their code trying to write to memory which either has not been allocated, or their code already released it.

    it happens. It is a common issue that comes from their engine code bein c++. It shouldn't take a month to solve.
    Share this post

  6. #16
    Adze.'s Avatar Senior Member
    Join Date
    Jun 2016
    Posts
    1,005
    Originally Posted by Beza_Bes Go to original post
    Maybe before you answer, you need to replace the Potato in your head? Think about it .. xD


    I've done my fair share of trying to help people fix these problems...
    Share this post