Having terrible problems with fast moving niagara projectiles smearing. They are high emissive and they leave awful streaks behind them. Happens with fast moving static meshes attached to the projectile too but nowhere near as bad.
Pretty sure its from a mix of upscaling and tsr.
Any tips on how to solve this? Im using 5.2.
My temporary fix is to set them to render after tonemapper and add in a depth fade to the opacity but this obviously isnt ideal.
But this 2nd video looks nothing like the first one consider it lost almost all light contributing to the scene somewhere ~50 meters? And also lose the light source. Like yes the flickering will make the overall result looks bad but I think itās a ābetterā output lighting wise compare to 2nd video. Once people fix that flicker itās superior result.
Does this work on mobile? If yes. Which is better fsr 1 mobile plugin or TSR for mobile?
If it does not work on mobile, Do you plan to release it in the future for mobile? Or maybe release fsr 2 for mobile? or maybe an update better version of fsr1 for mobile?
hey guys, I got this problem with anti aliasing and Epicās Water plugin: when camera is underwater thereās post processing happening that for some reason introduces tiny, wild flicker around every mesh
the more bright background the more it stands out. Mind that itās not specific to TSR, every available AA method makes it flicker, except for disabling AA altogetherā¦
Huh ok.
I did more testing on this. So you take a static mesh with a high emissive and move it around the viewport, the motion velocity all works fine and there is no smearing.
You take the same mesh and put it in a blueprint as a static mesh component and move the blueprint around and the mesh does not pass its velocity and you get horrible smearing. If you move the component itself the velocity is properly set.
So static mesh components are not inheriting the velocity of the parent blueprint.
I am getting this really weird swimming in pixels where when I examine in a still frame, pixels seem to be swimming diagonally back and forth. It causes huge issues because of our baked motion vectors, so upon sampling the edge, it goes back and forth between the baked motion vector and and then 0 from the background. It produces this high frequency smear and swimming effect. It does not happen on any other AA method. This is on cinematic quality.
I once pointed out problems in game trailers you ended up dismissing as youtube compression.
This trailer is perfect example showing in inadequacy of TSRās design. These issues are present in many games, but this is undeniable Temporal faulting on video:
https://www.youtube.com/watch?v=b6hAzFqWSSQ&t=140s&ab_channel=SILENTHILL(Official)
The res is so high they introduce major performance issues in a game where panning is the main interaction and it destroys modern monitors with persistence blur.
1:18: Leaves, so bad.
3:25: Long ghosting on clubbing object.
4:19 (hair)This is why a frame limit is so serious.
5:15 that girls hair looks like a slimy mess.
Now, the motion smear from fast motion isnāt going to be exposed by the main/slow gameplay. A frame limit and more effective sampling in a shorter sequence would prevent most of these issues.
Iāve already given detials responses of how TSR could be improved here, here. So far the best thing about TSR is the reprojection and ability to sort spatial upscaled N- frames.
Iām not sure how many spatial upscalers youāve tested. But FSR1 performance is more accurate in terms of texture detail when compared to DLSS performance with only 2 frames of resolve.
You also need to move away from FXAA. Really poor quality.
Hi!
I followed the instructions you posted and got the result of ProfileGPU like your example. But one thing I am confused about is how to upscale the captured image with TSR; TemporalSuperResolution() 1024x1024 ā 1024x1024 seems no difference between the render resolution and the display resolution(render target resolution as well).
Maybe something like ScreenPercentage should be set with SceneCapture? I tried to change the ScreenPercentage at Engine Scalability Settings and the upscaling info about the client viewport changed as I expected, but the info about the SceneCapture didnāt change(render resolution and display resolution are always the same). Iām not quite sure if ScreenPercentage is valid about SceneCapture since I read some source code(UE 5.3) about SceneCaptureRendering and found the comment, āScreen percentage is still not supported in scene captureā.
Is there something I missed? How to upscale SceneCapture image with TSR from low render resolution to high display resolution?
Hi, not sure if thread is still active or not, but after spending weeks researching about all this stuff thereās one thing I canāt find an answer for. And thatās why are we still seeing blurring artifacts (regardless of whether we can minimise them using various techniques) at 100% scaling? Is it possible to have a fallback pipeline without TSR (or TAA) for the cases that our users are playing that game from between 1080p and 2k resolution and want the game to look like previous generation games but with lumen enabled? Can you provide links to show which features of unreal require the temporal algorithms to help me understand what the reasons for the temporal artifacts are?
Also to offer an answer to your question, weāre expecting TSR to work with flow maps, but thereās an obvious unfixable artifact present with single layer water. You can see it behind this (attached) thin support pole around screen center - there shouldnāt even be a shadow present but instead a dark and jagged shadow is present. The water material isnāt set to cast any shadows and is more or less the default material present in ue5-main. The scene is using lumen with volumetric fog enabled.
