This pictures below were rendered in the movie render queue using Path Tracing. I have no idea why, but the ground textures are supper lowres. I’ve put this down to the engine mipping the textures, as you can see in one of my pictures it’s gradually getting more low res the further away the mesh gets.
I think MRQ is pretty messed up when you want to use it with pathtracer(weird blurry filtering over image, tonemapping seems off and high amount of spatial samples will crash gpu).
I use legacy video capture option in sequencer when I want to use pathtracing, maybe try that option. I think if this issue you describing isn’t present in editor then it wouldn’t be in legacy capture either.
This was a really smart idea, so I tried it… In the image below you can see it rendering fine in the preview window. On the right you can see I’m using the legacy sequencer.
However upon checking the output, it’s just just giving me black empty images (?). I tried finding a solution for this, but seems I couldn’t find any answers.
I think I solved the issue, it was a multiple of things causing it. I turned the rubber marks into a static texture and not virtual texture as this was a decal. Maybe there is a bug here with virtual textures/path tracing/decals?
The asphalt blur was related to the camera aperture being set too low as it was naturally blurring.
To be honest the asphalt still looks blurry at the focus point but looking at a normal photo this kind of looks correct. Maybe I can just adjust the contrast of the asphalt to pop a bit more.
I have the same problem when rendering with path in version 5.1. I just want to render an image and I get blurry with no reflections and lots of errors. In the viewport it looks good, but rendering in high quality is the problem. does anyone know the problem?
