I think I’ve found a bit of a bug in the progressive rendering limit.
When set initially, it will work to make rendering move on when it reaches those samples, but when I cancel a rendering and try and lower it, it doesn’t respect the new number. If I close and open the file, the number can even be arbitrary…the attached screen cap that says ‘89’ is a good example. I’ve never put 89 in as a progressive limit.
This is consistent with the scene file I have here.
(Loving Corona so far…quite a lot actually. Keep up the great work! Thanks!)
I see auto keyframes are on in one of the screenshots. It is possible that you unknowingly animated the parameter, but corona does not display the animation properly in the UI. I’ve fixed this in newer versions. You can confirm it by looking in the track view
The only other clue that may or may not matter is that it did start out as a Vray based scene, then I moved it over to Corona. I doubt that would matter, but just in case…that’s one odd thing about it.
yep, the parameter is really animated. There is a bug that corona lets you animate a parameter without displaying it properly in UI (it is visible in the track view though). It will be fixed in the next release.
AHA! (I can’t see my curve editor now after switching my monitors around…stupid Max)
Great feature actually…I would have toned it down a little when the camera was moving quickly through the scene, but kicked it up a little when people would have noticed the noise.
