Currently I’m working on a short ‘cinematic’ Star Wars animation and I’m using Unreal as a renderer and I stumbled across this issue where my depth of field will look much more noisy (and smaller?) when rendering/exporting a scene from sequencer while it will look much better in the real-time viewport, even when viewing in full-screen/F11 mode. Is it because of the motion blur? It happens in both 4.16 and 4.17. Thanks
What’s your depth of field quality set to? Check r.DepthOfFieldQuality. Maybe increase it to 2 or 3?
It’s set to 4 but I just found the cause - even though my scalability is set to Cinematic, in Render Settings for the Sequencer Export the “Cinematic Scalability” was unchecked and it was reverting back to lower settings.
Hello,
enabling “Cinematic Scalability” in the render setting window did not work for us.
While the rendering settings were set to cinematic in the editor and in the DefaultGame.ini, the DoF was always
reset to “medium” I think, when rendering the sequence.
Trying to set “r.DepthOfFieldQuality 4” on Begin Play did not work for rendering.
Trying to set “r.DepthOfFieldQuality 4” on Tick dod also not work.
Both did their job in Editor Play/Standalone Play, but not while Rendering. So we thought, that it is reset by the sequence.
Deleting all PostPro Keys/Tracks did also not do the job.
We maybe narrowed it down to the cinematic cameras. They are created only by the sequence in Shots and we think they override the Scalability Settings in some way.
My really bad but working solution:
The Sequence goes from frame 0 to frame 1627. When I hit render, the DoF Settings went low.
When rendering from Custom Starting Frame -1627 to Custom End Frame 0 renders everything with high quality. (WHAT)…
And it ignores the Custom End Frame and renders the whole sequence two times. I got the double amount of frames: The first half is high quality, the second pass is low quality. This is crazy!! What is going on?
Nevermind, it works for now…
Sebi
This worked for me (setting the start frame to a negative number), the motion blur rendered properly for me when before it wasn’t rendering at all. Thank you!
I can’t believe this is still broken 5 years later.
I also cannot get the negative frame number to work in 4.26.2…
Any solution to this? Makes cinematic cameras completely useless for rendering sequences.
Something that worked for me was to actually enable to Manual Focus Debug Plane. The viewport doesn’t seem to understand the large value inputs the focus distance supports. I suggest that you actually dial in and see where your focus plane is actually hitting.