hmm no news about the surge 2 ? ;(

Changes and Fixed Issues in Version 436.48 Fixed Issues in this Release  [UBOAT]: The game crashes due to memory allocation issues when launching Sandbox mode from the main menu. [2694301]  [Tom Clancyʹs The Division II]: The game may crash when played in DirectX 12 mode. [200406322]  [Vulkan-based games]: Error message appears in the game when invoking GeForce Experience Freestyle or Ansel using the hot keys. [200549987]  [Tradesmen OS3DE]: Some objects are missing in the game. [2691363]  [Cinema4D]: Brushes produce a ghosting effect. [2633267]

PDF release notes listed known issues:

Windows 10 Issues [PowerDVD]: Blu-ray disks might not play using PowerDVD. [200555216] [FIFA 19/FIFA 20]: The game may crash to the desktop. [2690624/2713659] [Shadow of the Tomb Raider]: Random crashes to the desktop occur when the game is played in DirectX 12 mode. [200549489] [Star Wars: Battlefront II]: Random crashes to the desktop occur. [200550245 ] [Apex Legends]: Random flickering occur on the screen. [2709770]

And then from the GeForce forums there's this: https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/320827/official-geforce-43648-game-ready-driver-feedback-/

Top Issues and Updates: [FIFA 19/FIFA 20]: The game may crash to the desktop. [2690624/2713659] [Shadow of the Tomb Raider]Random crash to desktop in DX12 mode[200549489] [Gears 5]Random crash to desktop when loading match or quitting to game menu[2630220] [Star Wars: Battlefront II]Random crash to desktop [200550245 ] [Grand Theft Auto V]: Game may crash randomly after driver update[2703155] [Apex Legends]Random flicker on screen[2709770]

And when compared against the PDF there are these two additional listed issues are found here but not in the PDF, might be worth knowing about for anyone playing Gears of War 5 or GTA 5 and using these drivers or earlier depending on where the issue first appeared. 🙂 (It's in the known issues so it's getting fixed.) [Gears 5]Random crash to desktop when loading match or quitting to game menu[2630220] [Grand Theft Auto V]: Game may crash randomly after driver update[2703155] Nice to see quick updates for Breakpoint and then fixes to the longer standing D3D12 issue in Division 2 as well. 🙂

No surge 2 performance fix 🙁

is surge 2 having issues? I can't play yet... just finished BL3 and RMAing my card today (has some flaky vram), have to wait like a week 🙁 i loved surge 1, so i am excited for surge 2 🙂

[Tom Clancyʹs The Division II]: The game may crash when played in DirectX 12 mode. [200406322] They finally fix this, just as ShadowKeep is released and I stop playing The Div2.

Is it known if the DX12 issues are for Turing only or if they've been reported for all architectures? I wonder why so many DX12 games have been affected as of late, there's been no leak about a major DX12 rewrite either.

Yxskaft:

Is it known if the DX12 issues are for Turing only or if they've been reported for all architectures? I wonder why so many DX12 games have been affected as of late, there's been no leak about a major DX12 rewrite either.

Shadow of the Tomb Raider will not even run in DX 12 for me.

cricket bones:

Shadow of the Tomb Raider will not even run in DX 12 for me.

Then you have a whole other unique problem.

Yxskaft:

Is it known if the DX12 issues are for Turing only or if they've been reported for all architectures? I wonder why so many DX12 games have been affected as of late, there's been no leak about a major DX12 rewrite either.

The problem is actually DX12 and developers. Its why more are going towards Vulkan over DX12.

jwb1:

Then you have a whole other unique problem.

It isn't unique at all. Happens to many people, and not just this driver version.

WhiteLightning:

hmm no news about the surge 2 ? ;(

Do you have some issues with it? Using 436.30 myself without problems and it is the GRD for Surge 2. Also great that Div. 2 DX12 crash fixed.

AsiJu:

Do you have some issues with it? Using 436.30 myself without problems and it is the GRD for Surge 2. Also great that Div. 2 DX12 crash fixed.

yes vsync is broken. it will stutter if enabled. latest beta they added a switch to turn texture streaming off, which also helps with stutter, but the tearing is high.

good they fixed the division 2 crashes in dx 12, but it suffers also of some micro freezing happening randomly that is quite annoying, only happening in dx 12

jwb1:

The problem is actually DX12 and developers. Its why more are going towards Vulkan over DX12.

It's not a problem with DX12 itself and the developers when older games that haven't had issues before suddenly started getting them as well. AFAIK Shadow of the Tomb Raider ran without issues on Maxwell on many earlier drivers since release. Later drivers started getting DX12 issues across most of Nvidia's architectures. FWIW, I've not noticed any issues running Shadow on Kepler DX12. And Vulkan by itself isn't less forgiving than DX12. If the various studios' graphics teams do have issues with DX12, they're likely to face similar issues with Vulkan too.

one thing a lot of people often don't realize is that developing a game to be compatible with both DX11 and DX12 is usually what causes DX12 to have no gains over DX11, because you have to optimize and support two different code paths, therefore ultimately the developers get lazy and use the same DX11 code because it is easier to maintain. If a game is developed from scratch to use DX12, and you don't have to support DX11, then it is likely to be perform much better than if it was developed for DX11. And why would DX12 have problems or worse performance over DX12? My only guess is because using DX11 code in DX12 doesn't really produce the exact same results as running in DX11, as the low-level APIs are different and behave differently, so it is kinda of a workaround. If I understand those differences correctly, the DX11 code used in DX12 ends up being more prone to race conditions, which ultimately causes random issues and crashes. Why then aren't DX12 games developed from scratch? Games being released today have either started development several years ago, or the engine is the same as the previous game and would require a lot of work to rewrite the engine completely, so it ends up still having the same DX11 code paths. Also, if they stop introducing new DX11 code to slowly migrate to DX12, they will lose Windows 7 compatibility, which is still has a large user base. Solution: go straight to Vulkan, so there are no 2 code paths to maintain and works fine in windows 7, plus the added benefit of more easily supporting Linux. Given that Quake 2 RTX uses Vulkan, there is absolutely no reason to use DX12 for Ray tracing through DXR.

jwb1:

Then you have a whole other unique problem.

Nah it's not a unique problem, lots of people have problems with DX12 and ROTTR. I'll try these drivers and re-install the game to see if it's fixed yet.

WhiteLightning:

yes vsync is broken. it will stutter if enabled. latest beta they added a switch to turn texture streaming off, which also helps with stutter, but the tearing is high.

Interesting, I'm using Gsync and I actually must enable ingame Vsync for Gsync to work and it is smooth, then. Trying Vsync off with a framerate cap results to stuttering as refresh rate gets locked to 144 Hz but there doesn't seem to be tearing so it looks like normal Vsync with fps lower than refresh rate. Doubt these are driver issues though, most likely game bugs.

Nope, ROTTR still crashes hard for me. I can get to the main menu, but crashes when I try to load a game or run the benchmark.

Shadow of TR still crashes in DX12 on those, so can't even use RTX on 2080 Ti.. Why so many games have problems with DX12 lately? If not crashes then stutter ot freezing issues, not looking great for the future..