[feedback] VFB History "not rendered" error

[alexyork]

Hi again,

Diving into 1.5.1 here from 1.4 and we're getting "not rendered" plastered all over the VFB when loading in two simple saved renders in the history. Happening on multiple machines, and multiple scenes.

[vunoj]

Hi again,

Diving into 1.5.1 here from 1.4 and we're getting "not rendered" plastered all over the VFB when loading in two simple saved renders in the history. Happening on multiple machines, and multiple scenes.

because your history folder was changed or source images was deleted.

[alexyork]

Hi again,

Diving into 1.5.1 here from 1.4 and we're getting "not rendered" plastered all over the VFB when loading in two simple saved renders in the history. Happening on multiple machines, and multiple scenes.

because your history folder was changed or source images was deleted.

Hmm... we didn't change either of these things. Just defaults, and the source images are actually visible still as thumbnails in the history so they can't be deleted.

[vunoj]

Hmm... we didn't change either of these things. Just defaults, and the source images are actually visible still as thumbnails in the history so they can't be deleted.

check your history folder ... maybe change the time and date of creation of this images happened this error!?

[alexyork]

I found the files in the history folder. Folder and files are not changed - they're exactly as written from corona when I saved the frame to the history.

[sevecek]

Hi,
is this happening randomly, or have you found a way to reproduce it? Are you getting 'not rendered' also for Beauty, or only for elements?

[alexyork]

Hi,
is this happening randomly, or have you found a way to reproduce it? Are you getting 'not rendered' also for Beauty, or only for elements?

I'll try to check on this for you.

[alexyork]

Hi,
is this happening randomly, or have you found a way to reproduce it? Are you getting 'not rendered' also for Beauty, or only for elements?

I just started a fresh simple scene and I can't reproduce, but we've experienced this on two projects already underway that were started in 1.4 and now testing this in 1.5.1 where the problem appears. But it's also not consistently reproducible..  We will continue to keep an eye on it and see if we can find a reliable way to trigger it.

[maru]

It's a bit random guess from me, but just making sure - you didn't enable the "render elements only" option in the scene where the problem appeared? (scene > "render only masks")

[sevecek]

I just started a fresh simple scene and I can't reproduce, but we've experienced this on two projects already underway that were started in 1.4 and now testing this in 1.5.1 where the problem appears. But it's also not consistently reproducible..  We will continue to keep an eye on it and see if we can find a reliable way to trigger it.

Thank you. I managed to get "not rendered" when using history snapshots between different scenes. Not sure if it's the same issue, though.

[alexyork]

It's a bit random guess from me, but just making sure - you didn't enable the "render elements only" option in the scene where the problem appeared? (scene > "render only masks")

Definitely not, no. We just hit render, hit Save to history, changed something, hit render, save to history, then made one of them A and the other B and both were "not rendered". Same scene file.

[cecofuli]

Same, exact problem here.
Jus reinstall Corona and everything is ok,
I think that I deleted some config file.

[Ondra]

Anyone still having problems with this? in 1.5.2 or daily builds?

[romullus]

I had one case couple weeks ago where every single history snapshot refused to display in VFB. Can't remember if it was "not rendered message" or just garbled image. Max restart solved this problem.

It was with Dec 13 build.

[Ondra]

anybody else still having problems?