Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by WhiteLightning, Oct 23, 2016.
Played BF1 for about an hour yesterday, no freezes or any other issues.
OMG! I had this problem! I tried everything I could find, including a clean install, and still had it. So, it was an video driver issue, wow.
Could it be the fact that GPU rasterization is enabled for Maxwell and Pascal GPU's? Or hardware VP9 decoding (maxwell does not have this feature though)?
You can disable GPU Rasterization through the command line option (may also exist in chrome://flags I can't remember):
You can also try disabling hardware accelerated video decode (this option also exists in chrome://flags):
I would not recommend outright disabling hardware acceleration in the regular options menu. You may be able to fix the problems by disabling the specific feature (or do nothing and just wait till it gets fixed by Nvidia/Google if it's not a major problem). You can see if GPU rasterization and hardware accelerated video decode is enabled by looking at chrome://gpu.
Not sure whether it is the driver or the game but the two (brief) plays of Battlefield 1's campaign with 2560x1440 Ultra DX12 settings have both ended with crashes to the desktop on my system. The first happened with the v375.57 driver and the other with the v375.63 driver.
I haven't tried DX11 yet but is DX12 still in beta or something because overall I've not been especially impressed with it in any game I've played so far, even those where it is stable. I either see the same or worse performance and absolutely no visual upgrades of any kind (in Rise of the Tomb Raider you actually lose VXAO) which makes it, in my view, the most pointless graphical API yet.
For those wondering, here is the results of chrome://gpu for GTX1080 in Chrome 55b:
There is precisely no reason to use DX12 in BF1 on any GPU right now.
seriously just use DX11 & change other brand like Asus instead of EVGA.
FYI, EVGA started to send free thermal pad. if i were u, i don't dare to mentioned it at here.
there's a lot reviewer at youtube using GTX 1080 playing DX 12 smooth & silky w/o any hiccups.
one of it;
i had the same, but a dev channel update fixed it.
Yes, Dx12 might look ok playing but the min fps, 1% frametimes are real bad, and this goes for both AMD and Nvidia.
Dx11 is faster, smoother and more stable as dx12 still beta listed in BF1.
I noticed lower performance in Dx12 vers Dx11, not sure on 1080 as that stronger GPU but I bet even there you"ll notice Dx11 being better.
No issues with hw flash/html5 player, but I'm on Firefox x64 latest v49.0.2
Although RIFT is not so smooth with R375, R370 was a lot better.
ingame streaming mechanism seems a bit bugged, I've read once they use 3 different and then game picks best available while also switching between them., but this was a long time ago.. Lately they only changed to 64bit and multi core.
It happens if I turn around quick or sometimes when its streaming new area, 60fps-60-59-60-57-60-60..
I had standalone RIFT, now its in steam, if that makes any difference. Although in the past I remember standalone had less streaming issues, but I also had it on HDD, now on SSD.
I updated chrome to 55 beta, no more video corruption that i've noticed. Opera never had it. No other issues to report so far. I played a couple hours of counter strike and got my usual 250+ fps, and I tried to play star citizen but i think their servers are having problems.
On the regular release version of Chrome it has rasterization set to software only no hardware acceleration by default with my GTX 1080. I tried switching it to hardware accelerated but it made no difference. The canary branch which I have no issues with, has rasterization set to hardware accelerated by default on my PC. Both have VP9 hardware decode enabled.
Edit: Disabling Hardware-accelerated video decode in chrome://flags on the regular release version of Chrome dose fix the issue. For now I'm just gonna use the "canary" branch version since it installs along side the regular version and I have no issues with it.
Regular release version of Chrome (54.0)
Canary branch version (56.0)
Anyways, besides the Chrome thing which I think is a issue with chrome not the driver, I've had no issues. Played BF1 for a few hours and it ran great.
Pardon me for asking, but is there something about TF2 and FastSync we should know? When I pan around, my framerates tank to the mid-'40s, down from a fps-limited 210 …
Jez, hopefully i saw your post, i was by 2 fingers for a fresh w10 install
I'm nut :banana::banana::banana:
Im playing it vsync'd and RTSS 60fps cap, but still not it, now with r375 it was super smooth (tried 3 different servers).
Yep... Skipping the hell out of these drivers.. No thanks to all of this..
i don't think it's a driver problem since i wasn't having any issues using chrome 53 with this and previous driver (my chrome was outdated until i checked my chrome version), so maybe it's a chrome issue this time, i will try chrome 55b like dr.rus maybe like he says is not a driver related issue.
edit: tested with canary.
left is chrome 54 (black theme); right is canary chrome 56 (white theme) (current driver 375.63)
this makes my porn slightly distorted..
Flawless driver this time around. This driver has all the Win 10 Apps fixed etc.
Games running like a charm, including BF1.
i will keep the driver version 373.06 becouse i only instal the driver yestarday and all Works fine.
Personal top best score in 3d mark time spy: no problems during installation desktop any flickering issues don't use chrome: in f1 pc 2016 4k still random stuttering moments other games in testing