Cache friendly incomplete render
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Cache friendly incomplete render
Just testing an animation with Cache friendly because of the speed bump (from 3.5 Ms to 5.4 Ms ) and look like some of the rendered frames aren't completed. There is no Lightracing and the halt condition is set to 32.
Re: Cache friendly incomplete render
You need to set an halt condition only for the eye pass (not for eye+light).
Re: Cache friendly incomplete render
Not sure to understand what you mean. I'm not going to enable LT anyway and the Halt condition setting only offer you to set a number of sample without telling that you can chose between eye pass or eye light.
Re: Cache friendly incomplete render
The Blender addon is doing that already: https://github.com/LuxCoreRender/BlendL ... alt.py#L39
Anyway, it shouldn't matter in this case, since light tracing is not used.
The "cache-friendly" setting in the Blender addon should result in 32 samples per iteration: https://github.com/LuxCoreRender/BlendL ... ig.py#L302Dade wrote: ↑Sun Nov 08, 2020 4:26 pm Than it is this: viewtopic.php?f=4&t=2700&p=26026&hilit= ... ion#p25999
So 32 samples should be the correct halt condition.
@Sharlybg: can you reproduce it in a simple testscene?
What number of samples is reported after the rendering stops?
Re: Cache friendly incomplete render
Currently i just set the halt condition samples higher (128) to avoid such black cut. But i get random final samples/pixels (129/133/136/128/135....)@Sharlybg: can you reproduce it in a simple testscene?
What number of samples is reported after the rendering stops?
Will have to wait for tomorrow to make a simple scene and try to reproduce the issue as the current computer is rendering the animation.
BTW would like to have a TUTORIAL on how to setup AWS server for Luxcore 2.5 will be great as the Luxit thing is still in the Blur side ....
Re: Cache friendly incomplete render
It is normal that the render can stop at slightly more samples than set in the halt conditions. But in theory it should never stop at less, unless there's some bug or other problem.
Re: Cache friendly incomplete render
I got same problem, but with time halt condition. And frames were unreadable at all, not even a part of render.
Re: Cache friendly incomplete render
it doesn't really make sense to use the "time" halt condition when rendering multiple samples per pass over the image, unless the set time is a lot longer than it takes to complete one pass.
Re: Cache friendly incomplete render
So you mean for animation is better to use sample halt condition? If so, you could add some helper notice about it