In 5.5 our graphics looked fine, since we updated to 5.7 (through 5.6.1) we notices some issues
Screenshot is below
The 2 notable issues are weird edges on meshes (as if AA is not enabled) and lighting.
Nothing has changed at all between the project, literallly just an engine update.
Image 1 shows differences highlighted.
Any idea on where to start? What could have changed?
We use nanite (but not enabled on that throne in the middle). The trees are all nanite.
Steps to Reproduce
No idea
Random, could this be TAA related? Maybe mess with some TAA settings and see if anything looks different.
Hi there.
To me it looks like the entire image in the 5.6 vs 5.5 image is noisier / more aliased. Perhaps it is just more noticeable on the throne. I’ve highlighted some more areas where I think this is happening, but to me it seems like the ground and trees are also noticeably more noisy in the 5.6 image, compared to the 5.5 one. Though this could be due to slight image content differences. I think the quality difference is most noticeable on the bridge meshes and tree shadows. These appear obviously smooth in the 5.5 image, but very quite in the 5.6 image.
[Image Removed]
For us to help debug this we will need some more information. To start with, can you answer the following questions:
Can you tell us what Antialiasing method you are using for this project?
If you migrate one of these assets to a new clean 5.7 project, does the same issue occur?
If you could also provide your rendering settings from your DefaultEngine.ini, that would also be helpful.
Regards,
Lance Chaney
We use TAA, heres the render options from DefaultEngine.ini
[/Script/Engine.RendererSettings]
r.GenerateMeshDistanceFields=True
r.DynamicGlobalIlluminationMethod=1
r.ReflectionMethod=1
r.Shadow.Virtual.Enable=1
r.DefaultFeature.AutoExposure.ExtendDefaultLuminanceRange=True
r.CustomDepth=3
r.AntiAliasingMethod=2
r.Nanite.ProjectEnabled=True
r.Nanite.AllowTessellation=1
r.Lumen.TraceMeshSDFs=0
r.Lumen.TranslucencyReflections.FrontLayer.EnableForProject=False
r.AllowStaticLighting=False
r.DBuffer=True
r.DefaultFeature.AutoExposure=False
r.DefaultFeature.AmbientOcclusionStaticFraction=False
r.DefaultFeature.MotionBlur=False
r.SupportStationarySkylight=True
r.Shadow.UnbuiltPreviewInGame=False
r.Shadow.CSMCaching=True
r.SelectiveBasePassOutputs=True
r.DefaultBackBufferPixelFormat=0
r.DefaultFeature.LensFlare=False
r.DefaultFeature.Bloom=True
r.DefaultFeature.AmbientOcclusion=True
r.NormalMapsForStaticLighting=False
Compat.UseDXT5NormalMaps=False
r.Velocity.EnableVertexDeformation=1
r.MeshStreaming=False
r.SupportLowQualityLightmaps=False
r.VirtualTextures=True
r.VT.EnableAutoImport=False
r.Mobile.AntiAliasing=1
r.Lumen.Reflections.HardwareRayTracing.Translucent.Refraction.EnableForProject=False
r.SkinCache.CompileShaders=True
r.RayTracing=True
r.RayTracing.Shadows=False
r.Lumen.HardwareRayTracing=True
r.ReflectionCaptureResolution=512
r.TemporalAASamples=2
r.EarlyZPass=2
r.EarlyZPassOnlyMaterialMasking=True
r.HeterogeneousVolumes.Shadows=True
r.Shadow.TranslucentPerObject.ProjectEnabled=False
r.Water.SingleLayerWater.SupportCloudShadow=False
r.Mobile.AllowDistanceFieldShadows=False
r.Mobile.EnableStaticAndCSMShadowReceivers=False
r.PathTracing=False
r.SupportPointLightWholeSceneShadows=True
r.TemporalAA.Upsampling=True
r.SupportSkyAtmosphereAffectsHeightFog=True
r.SupportSkyAtmosphere=True
r.LumenScene.FastCameraMode=True
r.Lumen.Reflections.MaxRoughnessToTrace=0.5
bDefaultParticleCutouts=False
r.StencilForLODDither=False
r.SkinCache.SkipCompilingGPUSkinVF=False
r.DefaultFeature.AutoExposure.Method=2
r.MSAACount=2
r.VelocityOutputPass=1
r.AllowOcclusionQueries=True
fx.Niagara.SystemSimulation.TickBatchSize=0
fx.Niagara.Batcher.TickFlush.Mode=0
r.RayTracing.RayTracingProxies.ProjectEnabled=True
r.Nanite.Foliage=True
we also have a modified DefaultScalability
Hi,
thanks for these. I think the issue is either related to one or more of the post-processing or anti-aliasing default settings having been modified in 5.6 or not being properly being applied (possibly because they are overridden once the game starts).
Does this issue occur in cooked builds only or also in the editor? To confirm that this is TAA related, can you check if the problem persists when changing the anti-alias method to TSR?
Can you please provide the values for the following CVars at runtime:
r.AntiAliasingMethod
r.ScreenPercentage
r.FXAA.Quality
r.TemporalAA.Quality
r.TSR.History.R11G11B10
r.TSR.History.ScreenPercentage
r.TSR.History.UpdateQuality
r.TSR.ShadingRejection.Flickering
r.TSR.RejectionAntiAliasingQuality
r.TSR.Resurrection
r.Tonemapper.Sharpen
r.TemporalAACurrentFrameWeight
Do you have any other upscalers (such as DLSS or FSR) enabled in your project? In some cases, those may interfere with Unreal’s screen percentage and other TAA/TSR related settings.
Thanks,
Sam
We don’t have DLSS or FSR yet, we did have them in 5.5 but they were not turned on.
[2025.11.21-23.00.44:987][501]
HISTORY
[2025.11.21-23.00.44:987][501]Constructor: 4
[2025.11.21-23.00.44:987][501]ProjectSetting: 2
[2025.11.21-23.00.44:987][501]Code: 4
[2025.11.21-23.00.44:987][501]r.AntiAliasingMethod = "4" LastSetBy: Code
[2025.11.21-23.00.45:620][539]LogViewport: Display: Viewport MouseCaptureMode Changed, NoCapture -> CaptureDuringMouseDown
[2025.11.21-23.00.50:604][768]r.ScreenPercentage = "0" LastSetBy: Constructor
[2025.11.21-23.00.57:871][148]
HISTORY
[2025.11.21-23.00.57:871][148]Constructor: 4
[2025.11.21-23.00.57:871][148]Scalability: 4
[2025.11.21-23.00.57:871][148]r.FXAA.Quality = "4" LastSetBy: Scalability
[2025.11.21-23.01.00:837][271]LogViewport: Display: Viewport MouseCaptureMode Changed, CaptureDuringMouseDown -> NoCapture
[2025.11.21-23.01.01:937][337]LogViewport: Display: Viewport MouseCaptureMode Changed, NoCapture -> CaptureDuringMouseDown
[2025.11.21-23.01.02:803][389]
HISTORY
[2025.11.21-23.01.02:803][389]Constructor: 2
[2025.11.21-23.01.02:803][389]Scalability: 2
[2025.11.21-23.01.02:803][389]r.TemporalAA.Quality = "2" LastSetBy: Scalability
[2025.11.21-23.01.06:420][554]
HISTORY
[2025.11.21-23.01.06:420][554]Constructor: 1
[2025.11.21-23.01.06:420][554]Scalability: 1
[2025.11.21-23.01.06:420][554]r.TSR.History.R11G11B10 = "1" LastSetBy: Scalability
[2025.11.21-23.01.10:004][716]
HISTORY
[2025.11.21-23.01.10:004][716]Constructor: 100.000000
[2025.11.21-23.01.10:004][716]Scalability: 200.000000
[2025.11.21-23.01.10:004][716]r.TSR.History.ScreenPercentage = "200" LastSetBy: Scalability
[2025.11.21-23.01.14:606][910]
HISTORY
[2025.11.21-23.01.14:606][910]Constructor: 3
[2025.11.21-23.01.14:606][910]Scalability: 3
[2025.11.21-23.01.14:606][910]r.TSR.History.UpdateQuality = "3" LastSetBy: Scalability
[2025.11.21-23.01.17:557][ 37]
HISTORY
[2025.11.21-23.01.17:557][ 37]Constructor: 1
[2025.11.21-23.01.17:557][ 37]Scalability: 1
[2025.11.21-23.01.17:557][ 37]r.TSR.ShadingRejection.Flickering = "1" LastSetBy: Scalability
[2025.11.21-23.01.20:406][158]
HISTORY
[2025.11.21-23.01.20:406][158]Constructor: 3
[2025.11.21-23.01.20:406][158]Scalability: 2
[2025.11.21-23.01.20:406][158]r.TSR.RejectionAntiAliasingQuality = "2" LastSetBy: Scalability
[2025.11.21-23.01.22:640][246]LogViewport: Display: Viewport MouseCaptureMode Changed, CaptureDuringMouseDown -> NoCapture
[2025.11.21-23.01.23:640][306]LogViewport: Display: Viewport MouseCaptureMode Changed, NoCapture -> CaptureDuringMouseDown
[2025.11.21-23.01.24:307][346]
HISTORY
[2025.11.21-23.01.24:307][346]Constructor: 0
[2025.11.21-23.01.24:307][346]Scalability: 1
[2025.11.21-23.01.24:307][346]r.TSR.Resurrection = "1" LastSetBy: Scalability
[2025.11.21-23.01.27:090][468]
HISTORY
[2025.11.21-23.01.27:090][468]Constructor: -1.000000
[2025.11.21-23.01.27:091][468]Scalability: 1.100000
[2025.11.21-23.01.27:091][468]r.Tonemapper.Sharpen = "1.1" LastSetBy: Scalability
[2025.11.21-23.01.30:525][624]
HISTORY
[2025.11.21-23.01.30:525][624]Constructor: 0.040000
[2025.11.21-23.01.30:525][624]Scalability: 0.100000
[2025.11.21-23.01.30:525][624]r.TemporalAACurrentFrameWeight = "0.1" LastSetBy: Scalability
Thanks, I had a look at the changelog for 5.6, looking for any changes in anti-alias algorithms that could explain the visual difference between 5.5 and 5.6, but could not immediately identify anything. I wonder of the isometric nature of the scene is throwing off the anti-aliasing algorithm.
Can you provide some more details on how the isometric look is achieved (for example is it using the Paper2D plugin)? Alternatively, would it be possible to provide a small geometry asset which looks correct in 5.5, but has jagged edges in 5.6? That would make debugging on our end a lot easier.
After discussing this issue with my colleagues, it’s also possible that something changed in filtering scene textures (e.g. scene depth) used by the post-process material. Can you compare the 5.5 and 5.6 scenes with post-processing disabled?
Thanks,
Sam
We have tried many many options, nothing has changed it.