Forum Discussion
It cleared itself up spontaneously. A lot of others were complaining in game though. It was not occurring in the menu, single player, or training range (full GPU utilization no other issues) so perhaps there was a server side problem so bad it was bottlenecking my GPU
And its back, somewhat spontaneously within 10 minutes of starting my first game of the day. I noticed a lot more threads with similar to exact symptoms though so im going to go ahead and assume this is known. Just adding one more to the pot
- IICookieGII8 years agoSeasoned Veteran
- 8 years agoBFV ran smooth for weeks in DX12. Dice releases a patch on 12/11/18. FPS is the usual 144 but there is a micro stutter and screen tearing. Nvidia releases driver 417.35. DX11 gameplay is smooth and there is no tearing but I have to use FFR to achieve high framerates. DX12 still has tearing and choppy gameplay. Dice releases a patch this morning(12/13) and now both DX11 and DX12 have screen tearing and feel choppy. HOWEVER if you play in borderless or windowed mode it's smooth as butter. I'm not sure who to point the finger at since Microsoft, NVIDIA and Dice have released patches this week and my GPU is a replacement.
I7 8700k
EVGA z370 FTW
EVGA 2080TI XC2 Ultra
Acer XB270HU 1440P/144HZ - Anonymous8 years ago
Thanks for the suggestion. Honestly it did feel a bit better, have no idea if its just in my head. But unfortunately the main problem still persists and its reflected in GPU utilization and FPS as well. Perhaps FFR was just a regular resource hog and thats the benefit I'm seeing if at all
Edit: I guess it doesn't quote replies.
Anyhow GPU utilization is in the dirt. Its being bottlenecked hard, glaringly obvious and only in multiplayer. 100% GPU in the menu, single player, training ground, but varying all over in multiplayer with a rough average of 60% GPU usage with all the poor fps and much worse the bad stuttering, hitching, and fall offs with what im assuming are even worse frametimes. The fact I witnessed it suddenly going away then coming back (along with being constrained to multiplayer) leads me to believe this is actually a server side source issue even though thats typically pretty low on the list for stuff like this