Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by zandathrax, Aug 1, 2018.
Yeah, or by steam too at times..
I first saw this with win8 I think, not sure..
I'm not the only one that noticed this issue like long long timer ago eh? I pretty sure this going back to when I first started using firefox which was windows xp goldage. if it actual fixes that, then I might just might uupgrade my drivers then everything works fine for atm
Either way if this is for what I think it is for it proof this issue was with nvidia drivers,
I haven't actually seen it happen with firefox 62 so far.
Weird. I ran it and it said that it was on after the benchmark finished. The performance during that run was also inline with previous scores with async turned on, if not slightly better. When I go home I'll upload the screenshot of that run later on, but one thing I noticed is that the performance characteristics are slightly different compared to previous runs. This tells me that the driver's programming when it comes to asynchronous workloads is different than before.
Valley ~ the same as 397.64. QC, Vermintide2, Midair no issue, all run good. However, I still think 397.64 is smoother and tighter.
Here are several screenshots with async turned with different drivers. If you look at the CPU render framerate, it has gone down in these newest set of drivers, despite the average framerate increasing.
Spoiler: Newest drivers with async on
Spoiler: Old drivers from over a year ago with async on
Spoiler: Old drivers from over a year ago with async off
Something has just always felt off with the 38x & 39x branch drivers since using them.
Don't know if something is going on with memory subsystem or the color compression algos or something, but they seem to have more microstutters and not as smooth as previous drivers.
Most definitely not a scientific evaluation, just from using them. Could also be windows 10 updates maybe. Wish Nvidia would drop all of the useless Experience, Ansel & telemetry bull in the drivers and concentrate on making a robust driver for windows 10. Using a GTX 1080 here. . .
So I have a question now guys, because a friend thinks about getting himself a new monitor:
When using a main monitor for gaming with Gsync, and a second one without Gsync, does that work? Do you really have adaptable framerates (working Gsync) on the main screen and the other one's still usable for other stuff? Anybody having such a setup who can give me some intel on that?
it works, but the desktop is always treated as a single image so anything operating at full framerate on the normal / 60hz screen will bring the gsync screen down too.
Thanks for your answer. So if somebody uses a Gsync screen with borderless window mode (the way he plays games), and the desktop extending to show either desktop or a stream on the other screen, it won't work displaying e.g. a browser on the right window, and a borderless window game on the left (then Gsync) one?
it will work, but any activity on the browser will bring down the framerate of the game.
Thank you very much for the answer. Might as well give a second monitor a try again now...
I have not actual payed attention to the bug in years, I have not updated to these drivers either. if issue with nvidia driver or firefox it self I guess we find out if I see it happen
Not judging if you legitimately like the game, but man this made me chuckle. Sorry, bud.
I'm getting DX11 crashes in Final Fantasy 14 with these drivers, never happened before.
I got a tdr in clash royale. Its f2p game, I don't play this but friend ask me I'd I want to do a game or two. So I did and after 15-30min I got that error..
While in game on left corner with red text saying driver reset lowering textures, I played only with this driver, idk what's with others.. already deleted the game.
Make a proper clean install with DDU! Shouldnt be a driver issue...or else you would see more complaints about it in the (FFIV) forums.
Just a FYI there is a newer version 398.98 with additional hotfixes
For anyone that's interested, asynchronous compute is OFFICIALLY turned back on in Gears of War 4 for NVidia users after an update that went out today, and you can now toggle it in the settings again
Yep played today for an hour and everything seems right the game is smooth and good.