Vray 5 | Light cache | Flythrough Mode Removed?

[troy@visualiii.com.au]

Maybe I've missed this within Vray 5 documentation, so apologies if I have.

Using Light cache for secondary bounce for an animation. It would appear that the flythrough mode has been removed. it only has single frame and from file.
Is this correct?
If so, does the single frame mode now work like Irradiance Map (multi frame Incremental mode)

Vray 5 | Max 2019

[B_Loeffler]

We facing the same surpirse in our office.
I'm sad that this option is not available in vray 5 anymore.

So what is now the best solution, if I want to render a flythrough animation? Light cache in single frame mode will result in unneccessary higher rendertimes for a flytrough animation.

Thank you in advance!

[troy@visualiii.com.au]

the response i received from Lele about this matter.
Render times do feel like it's blown out. But i see no alternative but to adhere to Chaos suggestions
This method does work well, tinker with noise threshold and denoiser

https://forums.chaosgroup.com/forum/...06#post1003906
and
https://forums.chaosgroup.com/forum/...35#post1003935

V5 removed the pre-calculated LC entirely, and while the IRMap is still present, it's officially a discouraged method.
Saving precalcu;ated caches to disk is also officially discouraged.
This, due to the needs of stuff like the LightMix and LPEs, besides others.

From factory defaults, use BF/LC, per frame, setting the LC up as needed (still or animation from the dropdown).
If on earlier V-Ray versions, you can mimic that by setting the LC to 3000 subdivs, and a retrace of 8.0, in single frame mode, for animations.

[Oleg_Budeanu]

the response i received from Lele about this matter.
Render times do feel like it's blown out. But i see no alternative but to adhere to Chaos suggestions
This method does work well, tinker with noise threshold and denoiser

The Docs are not explaining in detail - what is Single Frame and what is Animation.
I usually render camera-only movement animations and I used Fly-Through and every 10-15th frame of irradiance map in incremental mode. That worked perfectly for me. Now, what should I use? Single frame? Animation?

[^Lele^]

The Docs are not explaining in detail - what is Single Frame and what is Animation.
I usually render camera-only movement animations and I used Fly-Through and every 10-15th frame of irradiance map in incremental mode. That worked perfectly for me. Now, what should I use? Single frame? Animation?

Animation.

[troy@visualiii.com.au]

Oleg, if you need more assistance or explanation, email me at enquiries@visualiii.com.au and I'll screen grab what i used to make it a little clearer. I'm in Australia, so right now, I'm leaving for the day.

[Oleg_Budeanu]

Animation.

Thanks, Lele.
And it will render each n-th frame I specify? I still render with irradiance map, as it is faster for me.

[Oleg_Budeanu]

Oleg, if you need more assistance or explanation, email me at enquiries@visualiii.com.au and I'll screen grab what i used to make it a little clearer. I'm in Australia, so right now, I'm leaving for the day.

Oh thanks mate, will do!
Though there should be nice and clean tutorial from Chaos Group regarding that matter...

[^Lele^]

It'll render each frame, and with some higher settings than the "still" preset, because it's the only way to avoid bubbling.
The LC phase, in general, is a minute fraction of the rendering phase, but has enormous benefits for the final rendering stage.
With a retrace of 8.0, as the animation preset dictates, it will let V-Ray spend some more time cleaning issues, at the cost of some rendertime.

I am entirely unsure as to what will happen with a nth frame IRMap: it may work fine, or it may throw up tantrums.
The IRMap *is* faster than BF, as it's an undersampler method, while the Brute Force GI is an oversampler.
So, while the first deals with a pixel every few (with all that that entails) the other will work on each pixel, many times over (as that ensures accuracy.).

The *user* time to final is however shortened with LC+BF, as it's a fire and forget method (if not, it's a potential bug we may have to fix.).
It won't look as smooth as an IRMap, for the reasons above, unless one sets a very low noise threshold, or one denoises.

The only way to use old approaches (precalculated, nth frame, and so on) is with previous version of V-Ray than v.5.
Which of course also means letting go of a number of techs (LightMix, LPEs, Adaptive Lights and Dome, and so on. Particularly if using the IRMap!).
It's up to you to decide.

[Oleg_Budeanu]

It'll render each frame, and with some higher settings than the "still" preset, because it's the only way to avoid bubbling.
The LC phase, in general, is a minute fraction of the rendering phase, but has enormous benefits for the final rendering stage.
With a retrace of 8.0, as the animation preset dictates, it will let V-Ray spend some more time cleaning issues, at the cost of some rendertime.

I am entirely unsure as to what will happen with a nth frame IRMap: it may work fine, or it may throw up tantrums.
The IRMap *is* faster than BF, as it's an undersampler method, while the Brute Force GI is an oversampler.
So, while the first deals with a pixel every few (with all that that entails) the other will work on each pixel, many times over (as that ensures accuracy.).

The *user* time to final is however shortened with LC+BF, as it's a fire and forget method (if not, it's a potential bug we may have to fix.).
It won't look as smooth as an IRMap, for the reasons above, unless one sets a very low noise threshold, or one denoises.

The only way to use old approaches (precalculated, nth frame, and so on) is with previous version of V-Ray than v.5.
Which of course also means letting go of a number of techs (LightMix, LPEs, Adaptive Lights and Dome, and so on. Particularly if using the IRMap!).
It's up to you to decide.

Thanks for the explanation.
The only thing i'd add is that n-th frame irrmap is being used not only because previous version of VRay, but it does save time. On simple fly-through animations, when your budget is limited - this is a life saver, as it saves quite a lot of time in long-run.
And I totally do not understand why Chaos Group removed the "fly-through" completely... just add it as an option?
It worked perfectly for cases like mine, and now I have to render LC for every n-th frame with new issues which may or not may rise, as I have to change my stable workflow.

[^Lele^]

All that stuff is incompatible with the newer techs brought to bear, techs that most of our users requested.
There is also a case of terminal misbehaviour in a number of situations which we couldn't cure, and sent a good few user projects back to the drawing board, and more users still to our support.

Look at the bright side too: you can now do whatever your creativity demands, have moving geo and lights, and as much thin detail as you want to enrich your renders, and the settings won't have to be changed.

[jeremiah_jones]

[QUOTE=^Lele^;n1089455]All that stuff is incompatible with the newer techs brought to bear, techs that most of our users requested.
There is also a case of terminal misbehaviour in a number of situations which we couldn't cure, and sent a good few user projects back to the drawing board, and more users still to our support.

Moving forward with new tools is great and all and appreciated but I'm facing a case of having to update an animation done with Vray Next that is no longer rendering as expected using Vray 5. I was using IR/LC solution with pre cacls and was happy with results and time it took to render. At this point I can't downgrade my software and farm. Going this new route of BF/LC seems to either introduce a ton of noise or extremely high render times. I'm at a bit of a loss as to what to do in order to get the animation to render and look as good as it did and render in the same amount of time. What do we tell clients that have seen something without the noise and we can't afford to introduce extra time into the process to alleviate it. Any suggestions would be helpful.

[^Lele^]

I replied to you in the other thread.