VRFB turns to black

[yavor.rubenov]

The fix should be in today's 3.6 stable nightlies (28979)

[zeronove]

super!
I'll test it asap and let you know

[zeronove]

well, the main issue seems to be gone ...thanks

...but now I've a new one:
is there any know issue with load/compare VRay-settings? ...I mean the one that pops up right clicking history images

It seems sometimes settings are saved correctly and sometime they are not (ex it says they are equal when I'm sure they are not)
I've noticed that reloading some vrimg rendered with external render farm but it seems to work when if images are rendered locally

[yavor.rubenov]

I don't think there's any known issue similar to what you are describing. Could you share some reproduction steps or a vrimg file that gives you wrong results?

[zeronove]

got it, so I'll try to investigate more closely this issue in the next few days and keep you posted

[zeronove]

Hi Yavor,

here is a vrimg file that gives wrong results ...forgive the basic subject

https://wetransfer.com/downloads/ee3...8140200/b5b19c

Just load it in vrfb in a clean file (with default vray settings), save in history and try to compare or load settings ...here it says that they are equal but they are not for sure (ex it was rendered with bucket with 0,02 nr; no GI and so on)

Notice that this one is part of a set rendered with rebusfarm; if rendered locally it seems to work as expected

Let me know

[yavor.rubenov]

I understand now.
This probably is not explained very well in our docs and causes confusion. The required data for compare settings is written in the vrimg file only when saving it to the history.
So first of all - vrimg files from rebus farm are not the history images (I assume) - they are render output and don't contain any settings.
Second when you load a vrimg file and then save it to history the settings are saved the moment you save to history - so they are equal to your current settings.

[zeronove]

I see, thanks ...I didn't realize that before.

I've no idea about coding issues but don't you think it could be more useful to bake the render settings even if they are render output and not only when they are manually saved to history from vrfb? ...maybe with a checkbox option (autosave render settings or not).

Let me explain:
I find very handy to use vrimg as a sort of "backup container" from which I can extract required elements whenever I need them to compose final images.
This could happen in any moment; this means for sure in occasion of the main deadline but even sometime later (ex. months or more). So, if you have a vrimg storing all the render setting you are sure to fix an image the same way it was rendered time before or simply go on tweaking if not yet completed.
I know I can save presets or annotate settings elsewhere but when you have a lot of overlapping works with different requirement (and obviously scenes more complex than this one), it's wiser to have all the infos well tied together to avoid errors.

[yavor.rubenov]

Indeed you are right it can be helpful to save the render setting in the vrimg not only for the history panel. I've already added it to our internal todo list.

[zeronove]

super!!!
thanks a lot