Great update!!!!it is artistic decision - the SSS effect is not always visible, but it always slows down rendering. There are situations where it would be definitely useful, but for the general material it is probably better to keep it fast by default
One question. The new SSS in Corona Material says to use the new SSS mode for more solid objects like marble...... But if you drag out a marble material from the new Corona Material Library it is not using the new mode. Is this a artistic decision, materials made before 1.7 shader update or some other reason that is not important?
Download speed of Material Library is incredibly slow as expected. Any other hosts?We have 2*100mbps mirrors but it is still not enough ;). We are researching other options for the future (even though they are way more expensive). But it might end up being not necessary, because the material library is not downloaded again if it was not changed on our server, and we can upgrade it asynchronously with the corona core/plugin version - so we can update the library multiple times before Corona 2 is out, and ask people to reinstall 1.7 to get it - so when Corona 2 is out, people already have current mtl lib version
Thank you for the new version.
A question.
The installer dose not automatically install the materials.
So were do they go, what folder do I drop them into?
Thank you
phil
By the way, can anyone direct me to a place for future requests on new implementations or changes?
I already have some stuff in mind.
Great!!!!!! Can't wait to come home from vacation and install it!I second to that, bring Ludvík back on tutorials, he is great!
Will Ludvík Koutný make some follow up tutorials after this release? We miss him!
Count my voice too. We need those great Corona tutorials on the new features (skin, hair, sss).Great!!!!!! Can't wait to come home from vacation and install it!I second to that, bring Ludvík back on tutorials, he is great!
Will Ludvík Koutný make some follow up tutorials after this release? We miss him!
- Is the Corona Light Lister implemented in this release? This would be a major reason for us to upgrade sooner.
- What's the deal with the new light sampler that appears to be optional. Am I right in understanding that it's faster but in some cases results in splotches/leaks? Can we simply use the old sampler and carry on as usual to avoid this?
- Any major issues you're planning to squash in a forthcoming hotfix?
Probably a stupid question, but here I go: does the Material Library need to be installed on the rendernodes or not ?
Probably a stupid question, but here I go: does the Material Library need to be installed on the rendernodes or not ?
It shouldn't be needed. All material data should be uploaded from master to DR nodes like any other assets.
Probably a stupid question, but here I go: does the Material Library need to be installed on the rendernodes or not ?
It shouldn't be needed. All material data should be uploaded from master to DR nodes like any other assets.
ok, thanks for your answer, that's what I suspected :)
("occlude other lights" off)
("occlude other lights" off)
I have this on every single Corona Light I have ever created :- ), in 100perc. of my scenes. I didn't even consider it fake it due to being part of analytical light (not to the same degree as "ignore this object" ).
Will test if it causes artifacts all the time.
Thanks maru! As Juraj and Alex i can't remember any project where i turned off "occlude other lights" but will keep an eye on those artifacts. Is "visible directly" OFF considered "fake" in the same regard?Logicaly I guess that must be categorized as FAKE thing too
("occlude other lights" off)
I have this on every single Corona Light I have ever created
I'd say we use this on pretty much every project too
As Juraj and Alex i can't remember any project where i turned off "occlude other lights"
Same here, i never set the "occlide other light" on. Never.
Is "visible directly" OFF considered "fake" in the same regard?Probably yes. It is really hard to tell. That's why the new solver is off by default.
The new sampler is off by default and is enabled by toggling a single checkbox somewhere in the render settings (it's in the regular settings, not in the devel/experimental), so you can easily switch it on/off to see if it introduces any problems in your scene. The new sampler still has some problems (produces misc. rendering artefacts) when the scene contains non-physical fakes and few users report slowdowns on CPUs with high number of cores.
DR seems to be broken in final release of 1.7, worked fine in RC10 and earlier release candidates - now it just goes round in a loop without ever joining the render...Can you gather all DR logs - https://coronarenderer.freshdesk.com/support/solutions/articles/12000002065
DrLog attached
Edit - Rolled back to RC10 and DR is working fine. Anyone else having DR issues with 1.7 final release?
It might be that its written somewhere - but I haven't been able to find it.
How can I install the new Material Library another place than in the default place - i.e. on my fileserver.
And in which file are the path pointers to the library, if I need to move it manually?
It might be that its written somewhere - but I haven't been able to find it.
How can I install the new Material Library another place than in the default place - i.e. on my fileserver.
And in which file are the path pointers to the library, if I need to move it manually?
If I am not mistaken this is currently not possible. And I hope we get the option very soon.
It might be that its written somewhere - but I haven't been able to find it.
How can I install the new Material Library another place than in the default place - i.e. on my fileserver.
And in which file are the path pointers to the library, if I need to move it manually?
If I am not mistaken this is currently not possible. And I hope we get the option very soon.
Critical. We centralise all resources, as do all studios.
DR seems to be broken in final release of 1.7, worked fine in RC10 and earlier release candidates - now it just goes round in a loop without ever joining the render...Can you gather all DR logs - https://coronarenderer.freshdesk.com/support/solutions/articles/12000002065
DrLog attached
Edit - Rolled back to RC10 and DR is working fine. Anyone else having DR issues with 1.7 final release?
And then contact us using https://coronarenderer.freshdesk.com/support/tickets/new
But, the new DR will send missing assets to the nodes. So, it's not a big problem, I think.
Hi guys,Not possible in the same Max session because of the Max <> plugin architecture.
Is it possible to have an older version of Corona installed along with the newer 1.7 release? In the same version of Max.
Thanks!
DR seems to be broken in final release of 1.7, worked fine in RC10 and earlier release candidates - now it just goes round in a loop without ever joining the render...Can you gather all DR logs - https://coronarenderer.freshdesk.com/support/solutions/articles/12000002065
DrLog attached
Edit - Rolled back to RC10 and DR is working fine. Anyone else having DR issues with 1.7 final release?
And then contact us using https://coronarenderer.freshdesk.com/support/tickets/new
I should be able to reinstall 1.7 final release early next week, until then I'll have to stay on RC10 as I have deadlines looming. Happy to supply the logs once I get back to having the DR issue. I only grabbed the DrLog this time around
I wonder what`s the experience of everyone with corona 1.7 in regards of the speed?.., i found a video on youtube where someone renders the same scene in corona 1.6 HF3 and 1.7 and in 1.6 HF3 is faster, here is the video:There was a long discussion to this video on FB, but I can't find it now. Tom should be able to find it.
Yes, there is: https://coronarenderer.freshdesk.com/support/solutions/articles/5000577837-how-to-run-different-corona-versions-at-the-same-time-