Warning: Windows 10 Fall Creators Update - Loss of Antialiasing
-
After updating Windows 10 to version 1709 “Fall Creators Update”, antialiasing for Falcon BMS will be lost.
My graphics card is GeForce GTX 1080 using nVidia driver version 387.92.
Reverted back to version 1703, and antialiasing is working again.It could be that the current nVidia drivers are incompatible with Win10 v1709. I don’t know.
Anyone else noticed this problem?
Please give feedback if antialiasing working/not working after updating Windows 10.JayJay
-
What happens if you just reset the driver profile for BMS? Or delete d3d9.dll from the respective bin folder?
-
What happens if you just reset the driver profile for BMS? Or delete d3d9.dll from the respective bin folder?
Resetting the driver profile didn’t help. Did not try deleting the dll file.
Can’t test that since I’m running Win10 v1703.
Will not upgrade until new driver comes from nVidia or other confirmed fix. -
You have to use ingame AA option and in drivers switch it to Application Controlled, i am using it like that and it works. I tried 8 different driver versions and the behaviour is still the same.
-
You have to use ingame AA option and in drivers switch it to Application Controlled, i am using it like that and it works. I tried 8 different driver versions and the behaviour is still the same.
Are you running Win10 v1709?
In v1703 I use override x8 AA. -
Yes i am running W10 v1709, I had it like you aswell but 1709 broke the App setting override it seems. I tested different drivers and settings ( since i deleted old win version i have no choice ) and atleast the ingame AA works even tho it is not x8, still better than no AA at all.
I will try to play with the override AA for other games to see if it is broken for everything or just only BMS.
-
Ok, understand.
I’m almost sure all that’s needed is an updated Fall Creator driver from nVidia.
Hope you post an update on the situation as soon as the next driver arrives. -
Stay away as possible from version 1709, it produces much more problems than what is supposed to solve.
-
We should change the thread title to simply “Warning: windows 10” in big bold red letters and make it sticky.
All the best, Uwe
-
The ability to roll back and update windows 10 so easily is a god send compared to how things used to be and have been very impressed with its operation so far.
-
I chatted with nVidia support about this issue. They had no reports of this AA problem.
So community… all hands to the pump!
Send an e-mail to nVidia Support and tell about the problem.
If they get allot of mails regarding this issue, they can’t ignore it.Be aware, you can only temporarily pause Windows 10 updates for 35 days. After that, Windows will update itself wether you like it or not.
Brgds,
JayJay -
Setting the network connection to metered is supposed to restrict updates to only essential ones……though not used it myself so don’t know what is considered essential or what it actually does.
Disabling the Win Update service and BITS etc should stop all updates, but again not really had to go this far in win 10 so far so not totally certain…of course doing this you wont get any patches like the recent Krack one MS released 3 days before it was known publically.
-
Setting the network connection to metered is supposed to restrict updates to only essential ones……though not used it myself so don’t know what is considered essential or what it actually does.
Disabling the Win Update service and BITS etc should stop all updates, but again not really had to go this far in win 10 so far so not totally certain…of course doing this you wont get any patches like the recent Krack one MS released 3 days before it was known publically.
Dsiabling all updates is not a good idea really. There is an official tool that can be used to block particular updates. I’ve used it to prevent the download and install of 1703 CU.
Option 2 from here: https://www.tecklyfe.com/block-defer-windows-10-creators-update/
-
Is it not a better idea to make nVidia or Microsoft fix the issue, rather than blocking updates?
Many updates is released to protect us from the bad guys taking over your computer…Come on… Send an AA bug report to nVidia (and maybe Microsoft) and make them aware of the AA problem.
We are not many people flying F4 BMS compared to the other big games out there.
Hence, everybody in this forum with Windows 10 should put pressure on nVidia and or Microsoft, demanding a fix.JayJay
-
I’ve since upgraded to the Creators Update v1703 and did not have the issues I had before, but have since set my connection to metered to prevent updates as much as possible. I don’t like the idea of being a beta tester for MS.
Harry, what is this “official tool” used to block updates?
-
Dsiabling all updates is not a good idea really. There is an official tool that can be used to block particular updates. I’ve used it to prevent the download and install of 1703 CU.
Option 2 from here: https://www.tecklyfe.com/block-defer-windows-10-creators-update/
I only have the Home version so have been using that cab tool for a few years but didn’t catch 1709 before it started downloading.
On the other hand everything worked just fine for me in 1703.
-
Is it not a better idea to make nVidia or Microsoft fix the issue, rather than blocking updates?
Many updates is released to protect us from the bad guys taking over your computer…Come on… Send an AA bug report to nVidia (and maybe Microsoft) and make them aware of the AA problem.
We are not many people flying F4 BMS compared to the other big games out there.
Hence, everybody in this forum with Windows 10 should put pressure on nVidia and or Microsoft, demanding a fix.JayJay
Yes we should do this….however in the mean time it is important to try and give people a few options outside of “the great satan has removed all update control lets all run around screaming!!”
-
Ok so after downloading and wanting me to install 1709 I disabled the Windows Update Service and restarted.
I then reenabled the Windows Update service (set back to Manual) and windows thinks it is up to date.
Not only that but the wushowhide tool now lists 1709 under hidden updates so I might be alrightSo business as normal - Gotta love Windows really!
-
Stay away as possible from version 1709, it produces much more problems than what is supposed to solve.
You’re right and can bet it well, Raptor… I’ve lost the possibility to run BMS in 64 bit since I’ve updated.
Even if BMS is the one and only 64 bit program not running at all, I’m also thinking about reverting to an earlier version.With best regards,
-
This post is deleted!