DX12 and Windows Anniversary Update

[gthlm]

Been fighting this for a few days now.

Has anyone experienced problems with DX12 since installing the anniversary update?

I was playing Battlefield 1 with DX12 flawlessly before the AU, after the AU I have been plagued by extreme stuttering caused by cpu spikes. I've tried pretty much everything that conventional wisdom dictates - different drivers, disabling unnecessary services, disabling xbox GameDVR etc. I've even done a clean install (of the AU as I didn't have install media for the older build) and tried different driver revisions and everything under that.

Can only conclude that the AU has totally borked DX12 somehow.

Before I go and download an iso of the pre-AU build of W10 and do another clean install using that, can anyone shed any light on this?

Edit: Dunno why my sig isn't showing, but this is a 4770K @4.2 and a Fury X

 

[Seanspeed]

Whatever the case, you shouldn't use DX12 in BF1 regardless. There are no benefits in doing so, even on AMD cards, and it is known for causing sharp and sudden framerate drops.

 

[gthlm]

and it is known for causing sharp and sudden framerate drops.

Yes exactly. The point is that it wasn't doing that before windows installed that *&^%^* anniversary update.

Even with DX11 I have cpu spikes that cause extreme stutters for a few seconds every 10 minutes or so.

That also didn't exist before the AU.

 

[LokiS]

After I did that update I noticed every so often I would get a large stutter spike for a second then it would go back to normal, would happen randomly. Noticed for some damn reason microsoft decided to make backups of the drivers that were installed prior updating to the new build.

Doing a full fresh reinstall of newer win10 build with the au update built in completely fixed that stutter for me.

Can't say it's the same as yours so i'll try describe best what mine did. Generally when playing Guild Wars 2 (only game played at that time) after the au update when playing I would get this large stuttering hitch that could last for 1-3 seconds and then it would go back to normal, it felt like a big cpu spike. I think it was all the drivers back ups it did.

 

[LegendaryDread]

Try: Latencymon by Resplendence Software

Whatever the case, you shouldn't use DX12 in BF1 regardless. There are no benefits in doing so, even on AMD cards, and it is known for causing sharp and sudden framerate drops.

Confused to learn this - you'd think DICE would have a great DX12 implementation given their previous work with Mantle, and how similar the two supposedly are.

 

[Panos]

Been fighting this for a few days now.

Has anyone experienced problems with DX12 since installing the anniversary update?

I was playing Battlefield 1 with DX12 flawlessly before the AU, after the AU I have been plagued by extreme stuttering caused by cpu spikes. I've tried pretty much everything that conventional wisdom dictates - different drivers, disabling unnecessary services, disabling xbox GameDVR etc. I've even done a clean install (of the AU as I didn't have install media for the older build) and tried different driver revisions and everything under that.

Can only conclude that the AU has totally borked DX12 somehow.

Before I go and download an iso of the pre-AU build of W10 and do another clean install using that, can anyone shed any light on this?

Edit: Dunno why my sig isn't showing, but this is a 4770K @4.2 and a Fury X

Uninstall the drivers. Use DDU and reinstall 16.12.1.

Same issues existed with my GTX1080 on other games when upgraded to Anniversary Edition back in September. Had to reinstall the drivers.

 

[VincentHanna]

Dice recently patched the game, so are you sure this wasn't due to their update rather than Windows?

 

[gthlm]

Uninstall the drivers. Use DDU and reinstall 16.12.1.

Same driver version before and after, and also tried the previous and the latest after the clean install. Pretty safe to conclude that the drivers are not at fault.

Dice recently patched the game, so are you sure this wasn't due to their update rather than Windows?

Yes completely sure, as the patch came out after this - hasn't changed anything though...

 

[Seanspeed]

Yes exactly. The point is that it wasn't doing that before windows installed that *&^%^* anniversary update.

Even with DX11 I have cpu spikes that cause extreme stutters for a few seconds every 10 minutes or so.

That also didn't exist before the AU.

Well that sounds like a strange situation then. Dont know what to tell you.

I do have a hard time believing you now though, given your whole original post was about DX12 specifically. I question whether or not you just aren't able to admit that 'whoops, I should have just switched to DX11 and things are fine now' after my response.

Confused to learn this - you'd think DICE would have a great DX12 implementation given their previous work with Mantle, and how similar the two supposedly are.

It is disappointing, but I think it does a lot to show that DX12 is not quite what people think it is - some automatic performance booster or something. The benefits of that kind of low level optimization are predicated on a lot of things, and not all of them are going to exist for many people, especially those with reasonably good and 'balanced'(between CPU and GPU) systems.

And when you have a team that produce an amazingly, almost magically optimized game on DX11, it's actually not such a surprise to me that there's simply not room for improvement. BF1 is a technical masterpiece, both in visuals and in optimization.

 

[gthlm]

I do have a hard time believing you now though, given your whole original post was about DX12 specifically. I question whether or not you just aren't able to admit that 'whoops, I should have just switched to DX11 and things are fine now' after my response.

I'll clarify; using the previous (last before the AU) build of windows 10, DX12 and DX11 both worked flawlessly.

Using the AU build of windows (both as an update and as a clean install) DX12 is unusable and DX11 is ok but not as it was.

It is disappointing, but I think it does a lot to show that DX12 is not quite what people think it is - some automatic performance booster or something. The benefits of that kind of low level optimization are predicated on a lot of things, and not all of them are going to exist for many people, especially those with reasonably good and 'balanced'(between CPU and GPU) systems.

And when you have a team that produce an amazingly, almost magically optimized game on DX11, it's actually not such a surprise to me that there's simply not room for improvement. BF1 is a technical masterpiece, both in visuals and in optimization.

Agree about the incredible level of optimisation in BF1.

The main point is that I am curious as to how many of the reports of poor DX12 performance are actually due to something that Microsoft broke in windows with the AU. I am guessing that the vast majority of W10 users are running the AU and if there is something wrong with DX12 in that release then people will assume that the fault lies solely with DX12.