Hi,
my first project done with Corona.
Sorry, the room is not so “cool”
. But it was just a test to understand how Corona works.
It was an old scene modeled and textured from my friend with VRay.
I just convert from VRay to Corona, change the bed, the pillows and add the blu carpet.
Super!!!
hi cecofuli
very nice render ![]()
render time?
() 9 hours for the first at 6000px (during the night)
() 4 hours at 2500 px. But after one hours and half was ok. But the DOF is not very clean.. Look the last picture, on the right side.
I have my machine free, so I run as much as I can.
Usually, in VRay I render 3 hour for these renders.
All resize at 1920px. No noise reduction. Some little post.
ok thanks
Why do you say it’s not cool? I think it’s AWESOME! Everything is perfect - models, textures, materials, lighting. Only one thing bothers me - how do you open the wardrobe that is touching the desk/bed? Also, can you even seat by this desk or is it some crazy moving machine? ![]()
I don’t know. the 3d model is not mine
It comes from the company.
Here some WIP.
() MSI looks like a VRay GI caustic. So, with high MSI we can see the caustics generated by GI (not caustics from glass)
() MSI is a “threshold” and VRay GI caustic is only ON or OFF.
() MSI high = more GI caustic = more noise but better quality.
() MSI 00 = a lot of firefly

You are right. But it also affects glass caustics. Basically it’s pretty much what it says - maximum allowed sample intensity.
btw, just visited your website and I’m speechless.
Thank you
I would like to use Corona for some exterior project.
But I’m a little bit worried cause Corona VFB eats a lot of RAM. And my exterior are very complex (I use a lot Multiscatter)
Don’t worry about the multiscatter part, Corona can render instances fast and efficiently (with low memory usage) ![]()
Hi Cecofuli, nice images you have posted here ![]()
Also…i bought your book years ago!
I know, but in my test, if I lunch a 5000 px render, Corona uses, just for VFB, 4-5 GB of RAM!
For this scene, Corona eats 14 GB RAM. Too much in my opinion.
I don’t know what happen with a scene like this
But, I have to try ![]()
yes, I know I’ll have to rework VFB in the future… probably with reintroduction of (progressive) bucket rendering and better contrast function/some tonemapping curves. But for now I’m doing more urgent features like IES and DR
I agree 100% with you! DR and IES are a priority.
btw by setting internal res. to 1 you’ll cut the memory usage to 25%, but you won’t get antialiased highlights…
Maybe for my heavy external project, highlights are not so important
Good to know.
Ok, I’ll try in my next project ![]()
Caustic in vray very approximated because it is calculated by LightCache. Here are a few different algorithm, which allows you to get a much better caustic and even from light sources.







