We are releasing first daily build of Corona for Cinema 4D Beta 2. This is the first daily build so some parts of the plugin are not finished yet, it can be unstable and there is probably a lot of bugs.
No, but if you are asking because of low memory checker, it was implemented in Core for a long time so we added support for it to Cinema plugin. Actually, new core consumes less memory then before but new motion blur implementation in plugin consumes more memory (only when used of course) to be able to support motion blur of e.g. particles.
1- Is it updated of beta 1 or just it is different Beta2… with xxxxx fixes as you mentioned…?
2- Beta1… It will expire soon or I can use it will beta2 stable…?
3- In Beta2.. I am not seeing roadmap features… hair, converter, new shaders… it will be added later…?
Thanks.
…
p.s.: I did some job in beta1… I should go for Beta2 or stay in beta1 till job finish…?
It is the new “unstable” version of Corona plugin and not the update of Beta 1. This is the reason why it is called Beta 2, but it is of course based on Beta 1. Beta 1 is current “stable” version and it will be the most actual stable version until Beta 2 stable version is released. The first two features which we managed to finish from the roadmap are “Skin material” and “Material preview responsiveness” other features implementation is in progress, but I still have to update the roadmap. If you started some job in Beta 1 we recommend to finish it in Beta 1 because Beta 2 is in daily builds phase so it can be quite unstable. More info about versions you can find here: [https://forum.corona-renderer.com/Version differences and their purpose ](https://forum.corona-renderer.com/Version differences and their purpose )
p.s.: B1 Activation until 30-03-2018, after that…?
Will be reactivated again don’t worry Back to the previous question, when you start some project in some version (regardless it is daily built or stable version) we recommend to finish it in that version this is the reason why we have all released versions on our google drive.
Can you test an IES light in a simple scene? IES does introduce directionality to the lighting, so could just be that the light no longer hits the character (and the previous version of Corona may not have been processing the IES, there were some issues with file paths if I remember rightly, so could be the IES profile was not being loaded and so the light was not having that directionality applied).
For more info - which was the previous version of Corona you were using? Are these C4D native lights with IES, or Corona Lights with IES?
Actually, does seem to be something up with IES - it is ignoring the rotation of the light, so the distribution is “fixed” in 3D space. I used a Corona Light, with IES, and the IES pattern always appears in the same place when I rotate the light, rather than rotating with the light itself.
Hi, I don’t use much displacement and I don’t use IR that much as the scenes I am working on are pretty complicated but I have been using the new beta for a couple of days in my normal workflow and have notices a bit of a speed increase on mac os. Also pretty stable for me. Great job, looking forward to the next update.
Maybe have found a small bug though, render region doesn’t seem to work at first attempt, I need to turn it on and off a couple of times before it kicks in
quick question cause I didn’t have time to test.
Does this support light blocking geometry(ie. bones) or does it stay completely opaque as the SSS option in the standard shader?
I like the simplicity of the SSS mode but sometimes, the volumetric, even though much slower, gives a more accurate result. Especially with the scatter bias.
Bones are just quicker to generate than painting new transmission maps. That’s why I ask.
