Drivers & Software

[ajlueke]

System Specs

Gigabyte RX Vega 64 (GV-RXVEGA64-8GD-B, under Custom Loop)

Windows 10 Pro 64-bit

Adrenaline 17.12.1

Acer XF270H monitor using DisplayPort.

ASRock Professional Gaming X370 (UEFI version 3.10)

Ryzen 7 1800X

Corsair AX 860 PSU

Corsair Dominator Platinum RAM (4x8Gb at 3200 MHz)

Hello all,

Since upgrading to the Adrenaline software (17.12.1 and 17.12.2) the load times when traveling between systems or strikes in Destiny 2 have been atrocious.  After 30 minutes or so, it can take several minutes to load into any playlist.  Reinstalling Crimson 17.11.1 resolves the issue.  Any chance this could be corrected in a future driver release? 

[ajlueke]

Destiny 2 Long Loading Times and Micro Stutters > Help - PC Support | Forums | Bungie.net

Others have had the identical issue and resolve it with driver reversions.

[ajlueke]

Further updates.  A friend of mine was playing Destiny 2 with us on a 8350-FX RX480 based system and also took minutes to load into the raid.  I asked if he had installed the updated AMD drivers (17.12.2), and he said he had the day prior.

Rolling back to 17.11.1 quickly fixed his issues as well.

[ajlueke]

Doesn't look like this issue has been resolved in 18.1.1, and isn't on the known issues list.  Guess it is 17.11.1 for me for the foreseeable future.

[ajlueke]

Just another update.  I ran the DDU and installed the 18.2.1 drivers and can confirm the issue still exists.  Initially, the game runs great.  But after moving between a few different planets, the load times gradually increase.  Reverting to 17.11.1 once again completely resolves the issue.

[juliocp]

Any luck with 18.2.2?

[ajlueke]

Nope.  Same issue.  I tried doing a complete reinstall of Windows and loading just 18.2.2 without Relive.  Same issue cropped up after I had jumped to a few worlds.  My friends were all loaded into the Leviathan raid long before I got there.  17.11.1 once again corrected the issue.

[juliocp]

In 18.2.3 release notes, Destiny 2 is cited as a know issue, but apparently is not the same as we have. I'll try the new driver this weekend.

[ajlueke]

Yup.  I'm not holding my breath for 18.2.3 to resolve the issue.  I'll just stick with 17.11.1 for now.

[ajlueke]

Hmmm, it seems like the mid February Windows 10 update has resolved the issue.  I just installed the update, and everything seems to be running fine with 18.2.3.