petfy Posted December 12, 2017 Share Posted December 12, 2017 Installed the windows 10 1709 update. It deleted several orbx scenery files Ran the orbx library update from FTX central 3. Continually get the following error message at the end of that imstall. Running FSX. Edit : also FTX central 3 shows nothing is installed. Force migration is greyed out and unusable. My advise is to not upgrade the W10 upgrade until other people are successful. Link to comment Share on other sites More sharing options...
Doc44kin Posted December 12, 2017 Share Posted December 12, 2017 Hi folks, Well I had my normal computer and my Tripple screen Flight sim,IRacing etc games computer updated yesterday,must admit it was a bit of a worry,but they are both fine this am,hope this helps,Doc Link to comment Share on other sites More sharing options...
petfy Posted December 12, 2017 Author Share Posted December 12, 2017 Thanks, looks like it is only mine then. Link to comment Share on other sites More sharing options...
petfy Posted December 12, 2017 Author Share Posted December 12, 2017 Turn out it is 1709 overcoming my blocking efforts and installing itself Link to comment Share on other sites More sharing options...
petfy Posted December 13, 2017 Author Share Posted December 13, 2017 That upgrade destroyed all my symbolic links, that' s why a large amount of files could not be found. Had to delete and then recreate all symbolic links. Now to figure out why antialiasing is not working. Link to comment Share on other sites More sharing options...
petfy Posted December 13, 2017 Author Share Posted December 13, 2017 For some reason the latest Nvidia driver does not obey the Nvidia profile inspector profile for FSX. Had to set the Nvidia FSX profile back to the default and activate antialiasing within FSX. Link to comment Share on other sites More sharing options...
petfy Posted December 18, 2017 Author Share Posted December 18, 2017 Found this in another forum. Towards the top of the profile settings in your FSX Inspector profile you will see a setting called "Antialiasing compatibility." Set that to "0x004412C1 (Diablo III)" and it should work again. Have yet to try it. Link to comment Share on other sites More sharing options...
Wolf2grey Posted January 5, 2018 Share Posted January 5, 2018 Hey Petfy, Have you tried the fix above yet for Diablo III. My AA is not working in Full Screen. Link to comment Share on other sites More sharing options...
petfy Posted January 6, 2018 Author Share Posted January 6, 2018 Kind of got used to the non blurry menu and AI labels so have not used it so far. When the CPU fan starts to really have revs in this hot weather I might shift antialiasing to the GPU. There was another game you could set it to that was posted on this forum. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.