Ericmopar wrote:In that whole thread they are saying it is the driver's fault, that anything above 350.120 is causing issues.
It isn't just the maps, I was having issues with massive flickering when I put a new driver in recently. I had to revert to 344.750 on my machine.
The software industry is always fiddling with something and causing issues and the new Nvidia drivers are causing massive complaints all over the web.
Well, given that a clever person from UKTS wrote new and correct FXAA shaders to replace the faulty Kuju ones, I wouldn't be surprised if the old Kuju SSAA shaders were likewise faulty.
Railworks is probably not on nVidia's list of preferred games that need to be tested with every release of their drivers. I believe DTG has brought the problem under nVidia's attention, so perhaps it will get fixed. Then perhaps not ....
Massive flickering is also caused by wrong buffering of screens, missed syncing of screens, etc.
I am running nVidia 350.12 on my most powerful desktop with its GTX770, having refused to install anything newer on my dedicated gaming/Railworks computer, still running Windows 7.
To tPlowman: tell us some more about your Railworks graphics settings? nVidia driver settings are all on "application controlled"? On Windows 10 Home, Windows Update will push the latest nVidia drivers onto your system, wether you want it or not.
You can backdate the driver with one from nVidia's site, but it will get updated behind your back once again. Only when you switch your internet to Metered Connection, the forced updates will stop. Stupid MS decision, like so many in Windows 10.