I see this a lot - my impression is it is somehow related to the clouds - very obvious ghosting when flying in overcast conditions (using real weather). Yesterday I was observing an AI jet departing Heathrow into low overcast and the ghosting was shocking. I’d never seen it as bad as that before.
This is temporal ghosting often seen with DLSS high performance modes (which I don’t think your 1660 even has), raising graphics quality probably helps but would come with an fps hit and is obviously not ideal when flying fast jets. IMO upgrading to a RTX card is the most likely solution but in the meantime I suggest you mess around with the latency setting in NVCP.
This isn’t a bug, but it is a side effect of TAA. Switch to clear skies and it will be hardly noticeable. It’s not a bug either in the classic sense, in that it is working as intended, but has these effects.
Here’s a video I uploaded back in February 2021 showing the effect. It’s been there since release.
It’s at its worst when there are clouds behind the object moving. When I first saw it, a trail behind another plane on my flank, I thought it was some kind of vapour trail.
Also, notice how smooth London used to be back then. <sigh>
Interesting, I have been experimenting with DLSS and various RTX graphics options including DX12 to see what works best. The London building video posted above - I see that effect too and for sure it’s the clouds that cause the effect then…I guess I’ll wait to see how things work out - it’s good to know that it’s not just me. Thanks guys for posting.
Is this when you can se “traces” or tracks from the graphics? Its very easy to spot when going down a runway (against the grey surface). It’s like…if this i the plane >> its getting low opacity marks after it. > > > > >>. I though this had to do with my screen (LG 27GL83a).
I use DLSS quality at various screen resolutions and don’t seem to suffer so I believe the PC’s specs are probably responsible be it PCIe gen, core speed or ram speed/latency. Drive speed I think we can discount as MSFS runs from ram and this is not scenery.
It is a side effect of the way Temporal Anti Aliasing works, and is not an MSFS issue specifcally.
When combining pixels sampled in past frames with pixels sampled in the current frame, care needs to be taken to avoid blending pixels that contain different objects, which would produce ghosting or motion-blurring artifacts.
More interesting feedback thanks. I can confirm in my case that DX11 / DLSS Super Resolution / Quality / VSYNC on dramatically minimized the ghosting - except it does cause significant blurring on the A32NX PFD (speed & altitude tapes blurry). I think I can live with that. My monitor (and sim) run in native 2K at (I believe) 60Hz. Testing with FSLTL (static only set to 4) at fairly frame punishing locations such as EGLL / KJFK / LFPG - real weather on - getting around 30-35 FPS on an i7-10700 / 16Gb / RTX3070 which is pretty good. I am not using the latest Nvidia driver (but the one prior) as the feedback was pretty negative. So I’m on the fence for updating that - perhaps after SU12 drops and I’ve experimented with the settings.
True, although that is an artefact of the display device itself, whereas this is an artefact of TAA. That ghosting of the display would affect any fast moving object. Some may remember watching snooker on TV, and seeing a vapour trail behind the balls!
I daresay but as I’m not using Temporal Antialiasing but DLSS (quality) with all graphics maxed and not flying an F-18 it doesn’t seem to affect me, not that I’m even going to try to replicate it. It’s a known fact that TAA can cause this kind of artifacting so why is it being reported as an MSFS bug?