Shimmering remains my main issue with FI for P3D v4, so I think I'll give a go and test what you've done on my rig. My guess would be that SSAA was disabled either because of performance issues (have you tried it on with more demanding addons?) or visual artefacts and glitches. But like you I'd like to know why to better understand whether it be a good fix to enable it in some situations.
it may be that it is a performance issue, but on my rig with a Nvidia GTX980ti i found no glitches. When i am flying with the FSL Airbus (which is a heavy Load for the P3D engine) my GPU Load is round about 45% with 2SSAA and 55% with 4SSAA (flying in Europe with FTX Landclass EU and Vector). With 4SSAA the GPU reaches 99% in some Areas (dont know exactly what is the cause) but then goes back to 50%.
Interesting!!! I will point him in this direction guys.
I don't understand this either, I run with 2xSSAA all the time now (although I have to remember to go back to an MSAA setting before shutting FI down, or FI wont start next time I try to load it) I find this (almost) completely cures the terrible shimmering I get with P3D ver 4.
4XSSAA would be better, and I do use this with A2A but I usually fly with PMDG stuff, and I find the performance hit to be to high with them, so I stick with 2XSSAA.
I dont have any problems using SSAA and think it would help if this option was put into the FI settings option. Maybe the fact that it does work OK when selected inside the sim could be posted as a sticky, just to help some new users who may be confused about using it.
GoFlight Yoke, Saitek TQ, MFG Rudder Pedals, several Goflight modules. Home Cockpit.
I've now checked the actual P3D v4_Academic_4.2.21.24048 Version.
FPS drop to 22 FPS with 2SSAA and 34 FPS with 4MSAA.
So the bottleneck is dynamic Lighting and theres some work left for LM.
Is there a way to disable the SSAA check with a FlyInside.ini file modification or a different file?
I make several modifications to P3D cfg files and cameras.cfg files to optimize things to my tastes. So there should be an entry somewhere that checks for SSAA being enabled in the last run P3D settings that we could just eliminate.