Tom Clancy’s The Division will receive official DirectX 12 support next week

As you may already know, Ubisoft experimented with a DX12 renderer in the PTS build of Tom Clancy’s The Division. However, PC gamers were disappointed when they found out that this renderer was not included in the previous PC patch for The Division. Well, good news everyone as official DX12 support will be coming to The Division next week.

This upcoming PC patch will be released next week that will add official DX12 support. In addition, this patch will lower performance impact with high CPU usage, will fix the issue that caused the loss of character controls and will fix  issues with controllers on PC.

As Ubisoft claimed:

“This patch will also activate DirectX12 which should provide better optimization for higher resolutions. Please note that there is a known issue with DirectX12 where you are not able to change the brightness. “

According to early reports, the game’s DX12 renderer was running as good as its DX11 renderer (at least in the PTS build). Therefore, it will be interesting to see whether Ubisoft has made any additional improvements to it.

Stay tuned for more!

51 thoughts on “Tom Clancy’s The Division will receive official DirectX 12 support next week”

      1. Don’t waste your time S0ldier. It’s cool to be edgy, they don’t really care either way. I’ve seen the results of the PTS DX12 test and it was better for Nvidia cards, but “muh narrative” doesn’t like that.

      2. because it was with an amd fx processor in dx11 that cpu is getting pwnd by second gen i5…now dx12 finally makes those cpu shine but if you have a relatively modern i5 or i7 and a nvidia gpu then dx11 will be faster

        1. usually if there’s any bad performance from a dx12 patch, it’s worse on nvidia cards and little improvements on amd cards

  1. There’s been like one video comparing the peformance of The Division between DX11 and DX12. The results were great for NVIDIA GPU owners, but we need more samples. I hope this will change as soon this patch is officially released.

    1. There has been a few sites that benchmarke the PTS DX12 and Nvidia gains no worthwhile advantage in DX12. In fact the 1060 has negative gains from DX12. AMD barely does also.

    1. Not really, I get 60+ with every setting cranked up to max, so it’s no slouch already. Always nice to get better performance, but it doesn’t NEED Vulkan like other games do.

          1. How is DX12 better ? DX12 has been a shitshow so far. Most games that use it run worse than DX11 which is just laughable. Vulkan actually has benefited the games that use it.

          1. Explain what you mean, please, most PC games can run at more than 60 FPS.
            I personally find 60 FPS a bit disappointing, too. It feels “rusty”, somehow. It’s 75Hz which gives satisfyingly fluent gameplay, in my opinion. In fast-paced games, that is.
            Titles in which you don’t have to move the camera rapidly will do even at 30 FPS.

          2. Actually a lot of PC games has a hard lock at 60fps and generally breaking that lock breaks the game. Again, if you haven’t ran into this you clearly don’t play many games. As a modern example: Dark Souls 3 and Skyrim, as a retro example: No One Lives Forever and Tomb Raider quadrology.

          3. If it’s impossible to make a game go over 60 FPS, I won’t mind playing it, it will just be a tad disappointing.
            Keep in mind that the games you mentioned were either old or ridiculed for FPS being tied to their simulation speed. That’s right, I’m not outlandish, many people want games to go over 60 FPS and there’s flak in the PC community if they can’t deliver.
            “Again, if you haven’t ran into this you clearly don’t play many games”
            I just don’t play those specific games which coincidentally happen to have horribly designed engines. I’m not a fan of titles published by neither Bethesda nor Namco (and Japanese games – they often neglect PCs), and maybe that’s why I’m able to mostly shun this problem.

      1. Wtf, Vulkan works on any platform. Consoles with x86 architecture can support it just fine. Game Dev’s use DX12 because Microsoft incentivizes them to. Also, a ton of games in your list are by Microsoft themselves lol.

        1. No existing console support Vulkan. Also Mac OS doesn’t support it. Sony, Apple and MS don’t want Vulkan on own platforms. Only Valve want that API on Steam OS but gamers don’t want to change Windows to Steam OS.

          Graphics API by platform:
          – Windows PC: DirectX 11/12
          – Xbox One and Scorpio: DirectX 11/12
          – PlayStation 4 and Pro: GNM/GNMX
          – Mac OS: Metal
          – Steam OS and Linux: OpenGL or Vulkan (but without support of AMD)

          1. So your argument is that the consoles are incapable of supporting Vulkan because the corporations that own them block Vulkan compatibility? I was talking about the hardware. Theoretically, every (hardware) platform supports Vulkan because of the SPIR-V language. If a corporation decides to block Vulkan on purpose thats on them, not on Vulkan.

      2. Didn’t this argument already get crushed when that one guy explained that one thing about how Shader Languages were coming up behind you & f*cking you in your DX12-shaped *ss?

        Yeah, I thought so.

      3. He claims that just because the Xbox One uses a modified version of DirectX, the coding similarities make things easier for developers.

        P.S. Great point on multi-core support.

Leave a Reply

Your email address will not be published. Required fields are marked *