![]() ![]() Then I went to Home Depot's web site and it was crashing. Once I rebooted and went back to the same setup, it was working great again.įast forward a couple more hours, the game ended and I stopped playing Diablo. Completely closing Edge and reloading the page didn't help, nor did switching to Firefox. It would take a number of attempts to get the video to play in full screen mode again as it would occasionally flicker and fail. After a few hours, I noticed a drop in performance with Diablo and the game video would occasionally revert to un-full screen mode or crash. I only have a few games installed at the moment (HDD failure), but I loaded up Diablo III (Windowed full screen mode) on one screen and used Edge to stream the crazy 5+ hour Indians vs Yankees game on the other screen (full screen). ![]() After Windows installed these drivers, I re-ran the installer with the clean install option checked and then rebooted. It almost behaves as a memory leak and take some time (hours) after a reboot to notice and will keep getting worse. The browser and full screen issues seem to be related though. ![]() It's hard to describe because it's very erratic behavior. ManuelG - Was this a known issue that was fixed in this driver or was it some oddity with my PC?Ĭlick to expand. Since the v387.xx drivers have no release notes then it is impossible to say if it is due to the new driver or just some other peculiarity on my PC that somehow fixed itself. The Unity engine/30 FPS bug I mentioned Here *seems* to have fixed itself over the last couple of days, coincidentally after I installed the newer v387.87 NVIDIA graphics from Windows Update (I was previously using v387.78). Obviously, with the Creators Fall Update not being out yet then any issues with games are going to be few and far between but with Unity being a very popular engine for independent developers then it could become a widespread issue come the 17th (assuming this issue is not specific to my PC, which I do not believe it is since games using other engines all run perfectly as before). I suspect the issue may be tied to a specific build or builds of Unity Engine (most of those games use DX9 I think). Not all Unity games are affected though Ori and the Blind Forest, Oddworld: New 'n' Tasty, The Last Tinker: City of Colors all run at upwards of 165 fps on my system. Since then I have come across a number of other Unity games that have this same weird 30 fps bug, which incidentally is due to extremely low CPU and GPU usage: Orwell, Immortal Redneck and Kerbal Space Program, all run at 30 fps on my PC when tested with the v387.78 driver despite the fact these previous ran at 60+ fps on the previous version (v1703 build 15063.6xx) of Windows 10 with earlier drivers, including the officially released v385.69 WHQL driver. I am currently forcing exclusive fullscreen mode for this game via the Steam launcher options (-window-mode exclusive) and this allows the game to run perfectly without the need to constantly use Alt-Tab. I then discovered, completely by accident while adding a Framerate Limit of 165 fps via RTSS while the game was running, that Alt-Tabbing to the desktop and back fixed the framerate but on starting the next race the same 30-110-30 fps would reoccur until, I again, used Alt-Tab. The only way I could guarantee a solid 60+ fps framerate with to use the Low preset. I first noticed weird behaviour in Road Redemption, which uses Unity, as I saw framerates going from 30 fps at the start to 85-110 fps then back to 30 fps constantly during a race, which completely ruined the experience. ![]() the Creators Fall Update due for official release on 17th October) and, I believe, WDDM 2.3? I use a 165 Hz G-SYNC 2560x1440 ASUS ROG Swift PG279Q monitor. ManualG - Are you/NVIDIA aware of issues with Unity engine games on Windows 10 v1709 build 16299.15 (a.k.a. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |