# Why TSR 5.1 worked and in 5.5 it is terrible

**URL:** <https://forums.unrealengine.com/t/why-tsr-5-1-worked-and-in-5-5-it-is-terrible/2224795>\
**Category:** Rendering\
**Tags:** unreal-engine\
**Created:** [December 16, 2024, 11:11am UTC](https://forums.unrealengine.com/t/why-tsr-5-1-worked-and-in-5-5-it-is-terrible/2224795 "2024-12-16T11:11:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![WellCamel](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@WellCamel](https://forums.unrealengine.com/u/WellCamel)\
**Post date:** [December 16, 2024, 11:11am UTC](https://forums.unrealengine.com/t/why-tsr-5-1-worked-and-in-5-5-it-is-terrible/2224795/1 "2024-12-16T11:11:05Z")

</div>

I have unfortunately upgraded our project from 5.1 to 5.5. I did some extensive work on it only to get many reports that the TSR in the new version is just terrible. And it is true.

While in 5.1 TSR produced stable image even at 60 screen percentage. In 5.5 i have to crank screen percentage up to 200 to get stable image (which tanks performance completely)

At similar screenpercentage, the 5.5 version produces incredibly flickering look. Everything in the distane flickers.

I do not use Nanite or Lumen or any other experimental feature.

I have tried every possible cvar that is related to TSR and nothing makes it look like before.

Cvars i have tried and make no difference:  
r.FXAA.Quality=4  
r.TemporalAA.Quality=2  
r.TSR.History.R11G11B10=1  
r.TSR.History.ScreenPercentage=100  
r.TSR.History.UpdateQuality=3  
r.TSR.History.GrandReprojection=1  
r.TSR.ShadingRejection.Flickering=1  
r.TSR.Velocity.Extrapolation=1  
r.TSR.Velocity.HoleFill=1  
r.TSR.RejectionAntiAliasingQuality=2  
r.TSR.ShadingRejection.Flickering.Period 100 // only thing that helps very little is putting this value to 100

Have anyone encountered something similar? I dont see any way out of this now.

---

<div class="post-metadata">

**Author:** ![Miguel1900](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/miguel1900/32/1010694_2.png) [@Miguel1900](https://forums.unrealengine.com/u/Miguel1900)\
**Post date:** [December 23, 2024, 1:30am UTC](https://forums.unrealengine.com/t/why-tsr-5-1-worked-and-in-5-5-it-is-terrible/2224795/2 "2024-12-23T01:30:30Z")

</div>

I also noticed very unstable image quality and super low res edges, like squary.

The question is: what’s not broken in 5.5?

---

<div class="post-metadata">

**Author:** ![Rawalanche](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/rawalanche/32/906578_2.png) [@Rawalanche](https://forums.unrealengine.com/u/Rawalanche)\
**Post date:** [January 17, 2025, 10:27am UTC](https://forums.unrealengine.com/t/why-tsr-5-1-worked-and-in-5-5-it-is-terrible/2224795/3 "2025-01-17T10:27:46Z")

</div>

> [@Screen Percentage settings are still impossible to understand](https://forums.unrealengine.com/t/screen-percentage-settings-are-still-impossible-to-understand/2245536):
>
> Hi, a year later I once again took a whole day just to try to understand how resolution scaling (screen percentage) settings work in UE5, and once again all I got is migraines and anxiety about not being sure what resolution will my game run at, and not knowing how to be sure. Out of the box, when you create a new UE5 project, this is how all of the scattered settings are set up: Editor Preferences-\>General-\>Performance: Project Settings-\>Editor-\>Performance: Project Sett…

This is a topic of mine which may be related. There’s a general issue in UE5 that the screen percentage/resolution scaling settings are so overcomplicated and convoluted most people are never actually aware of what real resolution their game or project runs at. It changes wildly based on way too many factors.

So for example in Editor, you may see extreme flicker because TSR is upscaling from something like 60% of the original resolution. Even worse, just minimizing/maximizing the viewport using F11 key can be changing this screen percentage scaling on the fly.

Out of the box, in editor, it can be either scaled or not depending if you touched the in-editor scalability settings at least once, as they default to project settings, but if you touch them, even just once, the screen scaling will snap from the project settings based one to scalability preset based one.

Here’s an example of the default with maximized editor viewport rendering just 60% of pixels:

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/0/5/f/05f1468cfdeac80f18a9336569a4b45567f1a78e.jpeg)

It’s been giving me severe anxiety for years now, never really being sure about what resolution the editor, PIE and packaged build runs at. It just changes so wildly…

---

<div class="post-metadata">

**Author:** ![Lucian](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/lucian/32/88710_2.png) [@Lucian](https://forums.unrealengine.com/u/Lucian)\
**Post date:** [March 20, 2026, 1:06pm UTC](https://forums.unrealengine.com/t/why-tsr-5-1-worked-and-in-5-5-it-is-terrible/2224795/4 "2026-03-20T13:06:32Z")

</div>

A bit late to the discussion, but I’ve also been noticing TSR instability in Unreal Engine 5.3+ (especially flickering / moiré), so I took a closer look.

I went through Epic’s docs, tested a range of TSR console commands, and focused on which ones actually help improve image stability. I found a few tweaks that make a noticeable difference, and there isn’t much information about them online (like Thin Geometry Detection and Shading Rejection Exposure Offset).

So I put together a short tutorial covering what I found: [https://www.youtube.com/watch?v=I9Dka4NfSvQ](https://www.youtube.com/watch?v=I9Dka4NfSvQ)

---

<div class="post-metadata">

**Author:** ![GarfSnacks](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/garfsnacks/32/591709_2.png) [@GarfSnacks](https://forums.unrealengine.com/u/GarfSnacks)\
**Post date:** [April 5, 2026, 4:52pm UTC](https://forums.unrealengine.com/t/why-tsr-5-1-worked-and-in-5-5-it-is-terrible/2224795/5 "2026-04-05T16:52:13Z")

</div>

Started experiencing this flickering as well when I switch from 5.3 to 5.4. Wish I never ‘upgraded’  
The period command does help quite a bit though.

Appreciate the video Lucian, unfortunately some of the more impactful commands aren’t available in 5.4.

At the very least I’ll be looking into your EUW, that looks extremely helpful!
