Potential issue with Progressive render in RTX mode...

[HowardDay]

So the issue I'm seeing - and I should be clear here, I dont know if it's *intended* to work like this - if the behavior is even an issue, but it does look off to me - I have my render set for progressive, with a time limit per frame. As it renders it goes through pass 0-16, and looks like it's almost done, right up at the time limit I set... then it appears to start *completely* over, with the visible VFB looking noise AF and the pass *and* time counter re-set to 0. So renders tend to take twice-ish as long as I've set, and dont look any less noisy at the end. I'm on the latest Next 3.1, in Max 2020. Am I missing something? is this actually working like it's supposed to?
Give you an example of the results I'm seeing - a render time limit of 0.95 leads to a 51s render. Setting it to 1.0 gives a render time of 2m46s. Whaaat's going on here?
Thanks!

Howie

[hermit.crab]

Could you send the scene with the mentioned issue to support@chaosgroup.com so we can take a look? A video of the issue reproduction would be most helpful. Mention this thread in the e-mail as well along with your V-Ray and host platform versions.