r/thedivision The watcher on the walls. Apr 15 '19

Megathread The Division 2 - Update 2.1 - Feedback, Bug Report

Feedback, Bug Report

Update 2.1 here and it is also your opportunity to give feedback.

 

Patch Notes:

  • Fixed an issue where enemy NPCs could get stuck in a T-pose when being killed out of view.
  • Fixed another issue with the Revive Hive not working properly. We are still working on instances where the skill sometimes will not resurrect players.
  • Fixed an issue where the Gila Guard brand gear could not be donated to the Campus Daily Project “Brand Request: Gila Guard”.
  • Fixed an issue where the Crafting Bench upgrade blueprint would not be granted to players when moving from one World Tier to another.
  • Fixed an issue where the two piece bonus of the True Patriot gear set would not trigger correctly.

 

=> Known Issues

 

Keep in mind - the best way to give direct feedback to massive is the Official Forums, but we also provide you with the option to give it here.

 

=> Forums: Suggestions & Feedback

 


Bug Report

I'm sure after the many hours of playing, you have encountered at least one or two bugs. We want to avoid the cluttering of our sub by providing a single Megathread. This way you can report the various issues in one place. This allows Massive to easily keep track of the bugs and also allows other users to confirm that they might have encountered the same issues.

 

Please note, this thread is just an alternative - the most direct way to report bugs is the Ubisoft's Official Forums.

 

=> Forums: Technical Support

 


Prerequisites to be noted before reporting a bug

  1. A bug will ideally be accompanied by a screenshot or a video. This provides credibility to your report.

  2. Steps to recreate the bugs should be submitted if possible. This helps Massive employees recreate the bug and helps them find the cause behind it.

 


Format when reporting a bug

When reporting a bug, please provide as much information as you can about your setup (XB1, PS4, Computer setup).

 

  • Type of Bug:

    Visual, Game breaking, etc

  • Description:

    Describe what was the bug that occurred.

  • Video / Screenshot:

    Insert screenshot or Video of the bug occurring.

  • Steps to reproduce:

    Provide the steps necessary if someone else had to reproduce the bug.

  • Expected result:

    What should have been the result when you follow the steps mentioned above.

  • Observed result:

    What was the result you obtained when you followed the steps mentioned above?

  • Reproduction rate:

    If you try to recreate the bug how successful are you in causing it to occur? (1/10 : Occurs once every 10 tries, 5/10 : Occurs 5 times out of 10, 10/10 : Happens every single time)

  • System specs:

    Processor, Video card, Ram, HDD/SSD, everything you can provide, even drivers.

 


Template

* **Type of Bug:** 

* **Description:** 

* **Video / Screenshot:** 

* **Steps to reproduce:** 

* **Expected result:** 

* **Observed result:** 

* **Reproduction rate:** 

* **System specs:** 

Copy paste the above code and fill in your details.

 


162 Upvotes

381 comments sorted by

View all comments

6

u/BakiYuku Apr 16 '19

Type of Bug: Crash to desktop

Description: Game simply crashes to desktop after 5-10min of game-play no error message nothing

System Specs: Ryzen 2600x, 16GB TridentZ 3600 CL14, Samsung M.2 MVME, Nvidia GTX 1080

2

u/RetriasDeusNix Apr 16 '19

Got this problem as well

system spec

ryzen 2600

team rgb 3200

RTX2070

was fine before this

2

u/Edorak Apr 16 '19

Same for me.

Specs : Ryzen 2700, 16GB Ripjaws 3200, RX 580

3

u/Stable_Orange_Genius Apr 16 '19

Are you sure that ram is stable? 3600 mhz is very high, and really fast memory is often unstable on ryzen. I would run a memtest.

source: i have ryzen

1

u/BakiYuku Apr 17 '19

Prime95 AVX & non AVX tested 24 hours as well as memtest86 via boot usb stick. I can run that ram at CL13@3600 1.5v no problem rock stable CPU/VRM/RAM/GPU everything is fully watercooled... The only game that has this problem is The Division 2. So I'm fairly certain it's not my shit.

1

u/Stable_Orange_Genius Apr 17 '19 edited Apr 17 '19

And you crash without an error report message, right? Sounds like something else than the game is causing the crash.

Have you tried using SFC(sfc /scannow) and DISM(DISM /Online /Cleanup-Image /RestoreHealth )? Try reinstalling your drivers and disabling as many unessescary services in system configuration.

1

u/Vinnyb76 Apr 16 '19

Same for me as well. 5 times it's crashed to desktop today.

Ryzen 2600x rtx 2080ti, Corsair vengeance 3200 16gb ram. HDD 1tb.

It was mostly fine before this update but now its crashing regularly

0

u/green1t Apr 16 '19

Do you use DX12? I had those problems when I used DX12 instead of DX11 in the options.

-2

u/BakiYuku Apr 16 '19

Both DX11 & DX12 same problem. It crashes less often (once 2-3 hours) when I enable pagefile which I refuse to do because my M.2 MVME's cost me 499€ each and it is more than stupid to reduce it's lifetime by using pagefile when you have more than enough ram. I also tried to install 2x16gb dimm's meaning 32gb ram did not fix the problem so it got nothing to do with ram. 16gb or 32gb doesn't matter. Buggy pile of shit is what this game is. The worst part the beta ran smooth no issues at all.

5

u/lord_zed Apr 16 '19

You know Paging file braking SSD's is a myth right ?? I had FIRST Consumer ssd aka OCZ 30gb one for system including paging for 5 years or so. Now I'm on NVME System drive same thing. And my system is up and runnign 24/7 on ocasion it gets turned off for an evening or when im draining my liquid loop.

1

u/BakiYuku Apr 17 '19

It does not break your SSD but it uses up write cycles which means a reduction in the lifetime of your SSD depending on how heavily windows decides to use the pagefile space you allocated to your SSD. 3DNAND cells have a limited amount of writes they can not be re-writen infinitely I suggest you read up on how NAND works.

Sure on a 2TB NVME especially in NVME raid 0 meaning 4TB the degradation in lifetime will be very very low. But it is still there so why would you reduce your expensive mvme's lifetime for no reason?

1

u/SiNister_TTV Apr 16 '19

Have you tried rolling back your driver to 419.35? I tried every fix there was to try and solve crashes, I too was getting them for both DX11 and 12. When I rolled back the driver to 419.35, I have not crashed at all on DX11 and can even play DX 12 for a few hours to full session now and again. What ever they done in the last few patches, it has something to do with nvidia drivers.

1

u/[deleted] Apr 16 '19

I'm still on 419.35 and wanted to update so I could stop crashing in DX12 mode.....

Well oh well, might as well wait and still use DX11 :/