Which V-Ray feature should we bring to Corona?

[sebastian___]

Maybe this is already possible, in that case ignore this post.
A way to save the GI, or at least the most computationally expensive calculations.
This would be useful for animation rendering, if the scene doesn't have moving objects.
And not only for animation, but even for stills, if one already waited for an hour for a render to finish and he decided the still came out great, but he wants to re-render again with a slightly higher resolution, would be great to just save the calculation to a file, and re-render again from that file. And now the renderer needs to calculate mostly antialiasing and reflections, but not the lighting.

I think Vray has something similar to that.

I know Corona is suppose to only use modern techniques, and baking lighting is old technology, but I think many many years need to pass until a full quality still frame takes between 1 and 10 minutes where the baking point becomes moot.

[Ludvik Koutny]

Maybe this is already possible, in that case ignore this post.
A way to save the GI, or at least the most computationally expensive calculations.
This would be useful for animation rendering, if the scene doesn't have moving objects.
And not only for animation, but even for stills, if one already waited for an hour for a render to finish and he decided the still came out great, but he wants to re-render again with a slightly higher resolution, would be great to just save the calculation to a file, and re-render again from that file. And now the renderer needs to calculate mostly antialiasing and reflections, but not the lighting.

I think Vray has something similar to that.

I know Corona is suppose to only use modern techniques, and baking lighting is old technology, but I think many many years need to pass until a full quality still frame takes between 1 and 10 minutes where the baking point becomes moot.

Corona does this already for UHDcache. To do it for primary GI bounce would require something like Irradiance Map, and that's probably not going to happen.

Regarding DomeLight requests - adding DomeLight would not resolve Corona's inability to store multiple environments for LightMix. That's a completely separate and more complex problem. What introduction of DomeLight would do is just making IBL setup in Corona more confusing and less straightforward.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

As for my vote, definitely being able to see refraction in masking and texmap render elements. It's a long overdue already for such an important feature. V-Ray does that well :)

[Rhodesy]

Thanks for the fur and 2D displacement priority. They would be my top requests. More efficient fur would be even better if it can be tweaked for grass creation which many of us would use it for. 2D displacement is great too for clean and quick results.

After that CAR PAINT SHADER!

[pixel-flow]

VRscans, VRfur and 2D displacement are definitely planned, but not domelight - we could have made that easily from the beginning, but it was our decision not to do it, to keep the renderer simple and easy to use

Dome light
Anyone who wants simple can do the things as before, but having that option in more complex scenarios would make a life much easier for someone like me

[davemahi]

Cryptomatte

[Serj Scennikov]

Regarding DomeLight requests - adding DomeLight would not resolve Corona's inability to store multiple environments for LightMix. That's a completely separate and more complex problem. What introduction of DomeLight would do is just making IBL setup in Corona more confusing and less straightforward.

Then there should be another solution for the cases when need to keep 2 and more different environments in one scene with easy access, control and switching. Not everyone works with the slate material editor to keep separate tab with different environment maps, so this is not the solution.

[Ondra]

it should be scriptable - some simple UI where you drag&drop few maps and there is one switch controling which one is used. Somebody can try writing it ;)

[steyin]

Domelight and being able to have multiple HDRIs accessed easier would be fantastic for ArchViz, though the Lumiere plugin looks promising.

Agreed on a ToonShader also. I'd also say a bump-to-normal map, as well as some of the frame buffer post processing stuff.

[danio1011]

Right clicking in VFB to set DOF focus :-)

[NicoB]

Hej,

maybe it's not a "Vray-Feature", but today I was thinking about
the used LUT affecting the material editor slots.
It would speed up material creation a bit.

A vray specific wish would be the HSL or more color correction
options in VFB. Even less postwork would be needed.

So far for my ideas.

As for the upcoming changes for corona,
my only wish is that corona stays simple and relatively easy to use.

I'm very exited about whats coming up!

Best regards
Nico

[iancamarillo]

Dome Light
Aerial perspective (although the name is confusing - maybe call it fast fog?)

[Ludvik Koutny]

Regarding DomeLight requests - adding DomeLight would not resolve Corona's inability to store multiple environments for LightMix. That's a completely separate and more complex problem. What introduction of DomeLight would do is just making IBL setup in Corona more confusing and less straightforward.

Then there should be another solution for the cases when need to keep 2 and more different environments in one scene with easy access, control and switching. Not everyone works with the slate material editor to keep separate tab with different environment maps, so this is not the solution.

You don't need slate, you can have it in the compact material editor. For example create CoronaMultiMap, call it "Environments", and into each slot, add environment bitmap you want. Then when you need to switch them, just drag a new environment map and instance it into environment slot.

As far as complexity goes, it's about the same number of input actions:

DomeLight:
1, Select current DomeLight
2, Click checkbox to turn it off
3, Select another DomeLight
4, Click checkbox to turn it on

Environement slot:
1, Hit hotkey to open material editor
2, Hit hotkey to open environment window
3, Drag environment map from editor
4, Drop environment map onto environment slot

I am still wondering why do people keep requesting DomeLight. It does not add any new functionality, ease of use or speed. A practical example where DomeLight does something more or does it faster would be much appreciated.

[rambambulli]

I don't know Vray's latest versions.
So maybe this is not an answer to the question.
But, I would love .....

When I started with Corona it was the answer for easy high-quality rendering for me. Way easier as Vray, faster as Maxwell.
Now Vray a Corona join forces I hope Light baking reflection rendering inside Unity and Unreal will be developed. (like Octane is doing inside Unity, but then the Corona-way.... rock solid)

[Sintel]

I wish Corona had an easy, intuitive volume shader like Arnold 5's one but not complicated like V-Ray probabilistic shading, and IR definitely support it
Beside, deep data/OpenEXR 2.0 would be great

[iancamarillo]

I am still wondering why do people keep requesting DomeLight.

When I get a job I usually set up 10+ cameras and tweak the lighting (including hdr's) for each camera. I then set up state sets to record the lighting rigs and start all renders at the end of the day with one click. I don't have to drag and drop the hdr for each camera because it's been recorded in the state set. It saves me time. In 1.6 the scene environment rollout will not record switching between different hdr's but the max default environment tab does record switching between hdr's. So in that sense I guess I don't need the dome light. And I appreciate the simplicity of corona's approach to limiting confusing options. Which is I can see why the dome light was never created.