July 17, 201510 yr I don't know why but the inspector is not working correctly, maybe its the version or maybe there is something else. The problem I have is that after I place the values given in the guide and hit apply, the values revert back to where they where and then the [Antialiasing - behavior flags] option goes into [treat "Override any application settings" as "Application-controlled"]. I don't get it, can somebody help me? Francisco Perez
July 17, 201510 yr Commercial Member I don't get it, can somebody help me? Run the inspector as an Admin. Kyle Rodgers
July 17, 201510 yr Run the inspector as an Admin. I'm not entirely sure that helps Kyle. If the OP is using an newer card, say an nVidia GTX-970 or 980, the new drivers appear to prevent changes being made to the inspector. I found that running an older driver version (pre 35X) and inspector version 1.9.7.3 seems to do the trick with the settings staying put. I typically leave UAC completely off on my system and I had the same exact issue like the OP so even running it as admin may have no effect regardless of permission setting. -Jim Engage, research, inform and make your posts count! -Jim Morvay Origin EON-17SLX - Under the hood: Intel Core i7 7700K at 4.2GHz (Base) 4.6GHz (overclock), nVidia GeForce GTX-1080 Pascal w/8gb vram, 32gb (2x16) Crucial 2400mhz RAM, 3840 x 2160 17.3" IPS w/G-SYNC, Samsung 950 EVO 256GB PCIe m.2 SSD (Primary), Samsung 850 EVO 500gb M.2 (Sim Drive), MS Windows 10 Professional 64-Bit
July 17, 201510 yr Author I'm not entirely sure that helps Kyle. If the OP is using an newer card, say an nVidia GTX-970 or 980, the new drivers appear to prevent changes being made to the inspector. I found that running an older driver version (pre 35X) and inspector version 1.9.7.3 seems to do the trick with the settings staying put. I typically leave UAC completely off on my system and I had the same exact issue like the OP so even running it as admin may have no effect regardless of permission setting. -Jim Yes, I think this is my problem, I remember having some other issue before with a new driver version, but now I forgot which version I used because I stopped using fsx for a while. I have a GTX 770. Francisco Perez
July 17, 201510 yr Yes, I think this is my problem, I remember having some other issue before with a new driver version, but now I forgot which version I used because I stopped using fsx for a while. I have a GTX 770. You can open the nvidia control panel and in the help section, you can get the driver version. I learned a while ago to not give in to the notifications that come up in your systray about new drivers, chances are they will break something. If you have a driver installed that works fine for your games, there is no need to upgrade. I wish I could recall the article I found a while back about 970 and 980 cards and their respective driver that was locked out by nVidia, something to do with no tweaking necessary with the new cards and so many gamers were furious. I don't know if they fixed that issue or not but with my drivers and the latest inspector running, I can make the changes in inspector and they hold. -Jim Engage, research, inform and make your posts count! -Jim Morvay Origin EON-17SLX - Under the hood: Intel Core i7 7700K at 4.2GHz (Base) 4.6GHz (overclock), nVidia GeForce GTX-1080 Pascal w/8gb vram, 32gb (2x16) Crucial 2400mhz RAM, 3840 x 2160 17.3" IPS w/G-SYNC, Samsung 950 EVO 256GB PCIe m.2 SSD (Primary), Samsung 850 EVO 500gb M.2 (Sim Drive), MS Windows 10 Professional 64-Bit
July 17, 201510 yr Author You can open the nvidia control panel and in the help section, you can get the driver version. I learned a while ago to not give in to the notifications that come up in your systray about new drivers, chances are they will break something. If you have a driver installed that works fine for your games, there is no need to upgrade. I wish I could recall the article I found a while back about 970 and 980 cards and their respective driver that was locked out by nVidia, something to do with no tweaking necessary with the new cards and so many gamers were furious. I don't know if they fixed that issue or not but with my drivers and the latest inspector running, I can make the changes in inspector and they hold. -Jim My current driver is 350.12, don't remember which one I used before thou, which one do you use right now? Do you think its a good idea to create a new windows account just for fsx? Francisco Perez
July 17, 201510 yr Author Run the inspector as an Admin. I think the problem is the video card driver. Can you tell me which version do you use? Francisco Perez
July 17, 201510 yr I'm using 353.06 with the GTX 650 and it works great with Nvidainspector. Jerry Sterner
July 17, 201510 yr Use version 347.52 which is what I have. Also download inspector version 1.9.7.3 -Jim Engage, research, inform and make your posts count! -Jim Morvay Origin EON-17SLX - Under the hood: Intel Core i7 7700K at 4.2GHz (Base) 4.6GHz (overclock), nVidia GeForce GTX-1080 Pascal w/8gb vram, 32gb (2x16) Crucial 2400mhz RAM, 3840 x 2160 17.3" IPS w/G-SYNC, Samsung 950 EVO 256GB PCIe m.2 SSD (Primary), Samsung 850 EVO 500gb M.2 (Sim Drive), MS Windows 10 Professional 64-Bit
Create an account or sign in to comment