Daily Builds 1.6

[peterguthrie]

I was converting an old vray scene to corona over the weekend and the lack of vignetting was very frustrating.

[peterguthrie]

The darkening of the top right is how it shouldn't look, the other one is made by rendering two different exposure values in corona and masking them together in photoshop

[tolgahan]

It was brilliant release date 31 st. MARCH.I think we stay in 13 december version for a long long time :(

[romullus]

So you'd rather want rushed out release with many bugs, instead of waiting one more month for thoroughly tested build? :]

[rozpustelnik]

Long time no daily builds...

[denisgo22]

Long time no daily builds...

Are features with interactive zooming and 2d interactive zooming is stunning and very comfortable....
it remains only to debug DR mode render, and for me--- new daily has become as production version for work////
eagerly looking forward to the release of new version :))

[Ondra]

Long time no daily builds...

I am currently merging new features and debugging. I was sick for 14 days and abroad for another week, so it is taking longer than I wanted. I am hoping for one build by the end of day with everything new we did. So far these are things we have ready:

Generally improved speed by using better random sampling
Reduced flickering of the stats VFB panel
Added image sharpening/blurring to postprocessing controls
Bloom&Glare is now always disabled on Corona DR slaves, slightly lowering memory/cpu usage
Added collapsible groups to WX vfb
Relative error statistic improvements
Relative error is now shown with 2 decimal places
Fixed incorrect characters sometimes appearing in autosave filenames, disabling them: https://corona-renderer.com/bugs/view.php?id=2433
Improved the way expanding variables in autosave works - now it is possible to use for example D:/autosave/%f/autosave.exe to save each scene autosave into different subfolder (with subfolders created automatically)
Vfb regions improved
scaled together with image instead of being removed on render start
saved in max scene
can be disabled and later re-enabled
Added linear exposure to Corona Output map
Added object space normal and object gradient modes to CoronaDataTex
Added tone mapping on/off checkbox to Corona VFB
Added on/off checkboxes to lightmix groups in VFB
Added lens distortion support (3ds Max physical camera) - both cubic and texture modes are supported
Added option to bake lightmix into the scene - TODO
DR bugfixes
fixed a bug preventing user from cancelling DR
fixed textures not working when rendering with backburner
fixed CPU load on slaves when no render is running
fixed rendering of black images on slaves when VFB region is used
fixed DR not being cancelled when render is stopped during GI precomputation

[pokoy]

All great improvements! Didn't expect to see camera distortion added, very nice! Are improvements to the LayerMtl still planned?

Also, will there be fixes for these bugs?:
- Glossy reflections darkening (there was a thread were overriding visibility of lights/LightMtl objects would produce dark reflections in glossy reflecting materials)
- Physical Cam/CameraMod severely lag with IR rendering (this one drives me crazy...)
- Shadow terminator

Looking forward to the release, and take the time it needs, really. Thanks!

[rozpustelnik]

Thank You Ondra, hope You are feeling much better now. Keep up the good work!

[Ondra]

All great improvements! Didn't expect to see camera distortion added, very nice! Are improvements to the LayerMtl still planned?

Also, will there be fixes for these bugs?:
- Glossy reflections darkening (there was a thread were overriding visibility of lights/LightMtl objects would produce dark reflections in glossy reflecting materials)
- Physical Cam/CameraMod severely lag with IR rendering (this one drives me crazy...)
- Shadow terminator

Looking forward to the release, and take the time it needs, really. Thanks!

1 - not sure what this is now
2 - definitely
3 - hopefully. But it may come to a tough decision whether to release 1.6 without this fix, or push back release date because of it

[pokoy]

...
1 - not sure what this is now
...

It was this thread: https://forum.corona-renderer.com/index.php/topic,13860.15.html

Thanks!

[ihabkal]

Hope you are feeling much better, any thoughts about the claim that Vray 3.5 is 7 times faster?  I feel it is over-marketing.

[Christa Noel]

I hope you're well ondra, stay healty.
btw, layeredmtl still sit there in trello for 1.6. and so does the corona standalone app :D
and a question, sorry, what is IR subsampling?

- Shadow terminator

3 - hopefully. But it may come to a tough decision whether to release 1.6 without this fix, or push back release date because of it

imho I will choose to pushback release date :) as long as it doesn't meant to delay it for weeks :)

[Ondra]

Hope you are feeling much better, any thoughts about the claim that Vray 3.5 is 7 times faster?  I feel it is over-marketing.

"up to". it is the happy path where the scene matches what they were targeting. We had similar speedup when we introduced this feature in Corona 1.4, and we marketed it similarly, with disclaimer, that it affects only scenes with a lot of lights

[ihabkal]

Hope you are feeling much better, any thoughts about the claim that Vray 3.5 is 7 times faster?  I feel it is over-marketing.

"up to". it is the happy path where the scene matches what they were targeting. We had similar speedup when we introduced this feature in Corona 1.4, and we marketed it similarly, with disclaimer, that it affects only scenes with a lot of lights

I want to say something but I hope Vray users won't hate me, I used Vray for 10 years and switched to Corona after one night of testing, I actually tested Fstorm last night and I like it but I still prefer Corona, what I want to say is I watched the vray 3.5 webinar, I logged in 15 minutes late and the lady started saying :"we introduced new feature, it used to be you had to tweak this this and this setting, now you only have to tweak that and that and that setting, it is better now", I immediately switched off!!! so still we need to tweak several settings for anything!!!
I definitely appreciate Vray and I still love it, but honestly to get crystal clean non flickering result in animation you need to render all in Brute Force, Hollywood producers can afford it because they have 500 machine render farms, I can't because I don't have 400 millions for my small animation. I have 10 small machines. In Corona I can render an animation with 5 minutes a frame. it is up to me to make it sharper and add more time. In Vray the flickering doesn't go away unless you work really hard for it and render for 30 minutes to an hour a frame.