Buogiorno all I noticed that with version 1. 7 CMasking_ID the channel is incorrect if you use Distributed Rendering.
It also happens to you?
Andrew
Buogiorno all I noticed that with version 1. 7 CMasking_ID the channel is incorrect if you use Distributed Rendering.
It also happens to you?
Andrew
Is this happening all the time, or only sometimes randomly?
Can you send a sample scene to us? Chaos
It looks like the nodes/node is rendering a black image.
The error was given to 5 different scenes.
Enter now for one of the scenes so that you can verify.
Thank you!
Hi the same problem, i tnk because each node generate random colour different. ..on all scene, all view ![]()
Hi,
what CPUs do you have on master and on slave(s)?
yeah it actually happened to me aswell, my slaves are 2670v1, and main one is i7 7700k.
And also maybe somehow related, when I do region render with the DR active, it also renders the outside of the region with this kind of strips.
Is there a chance you are rendering from a Vray camera?
If the question is to me, no, I always use physical camera
No physical camera
I did a test with CoronaCamera does not even render
Hello!
We have the same problem. Win 7 sp1 + max 2018.3 + corona 1.7. i7-6600k, i7-4700k, i7-3930k, i7-820. While rendering with Distributed Rendering the light somehow interferes with CMasking_ID, CGeometry_NormalsShading, and few more. The same scene rendered using backburner without Corona DR renders just fine on each rendering node. This problem makes corona 1.7 useless.
After checking EXRs that are effect of " Save sent images" i can tell that they are fine. No interference is visible.
It is not just that - there is also a visible increased noise in render passes along those interference lines. Interior rendering with 300 passes has bands of slight noise. The rest is just clean.
Best regards,
Mike.
“Masking/other render elements coming out mixed with some other kind of image - like focus sampling mask or beauty”
To all users experiencing this:
Just a note: we are not sure if this has anything to do with V-Ray, but it seems that in at least two cases the solution was to either re-install V-Ray, or to stop using V-Ray camera. It could as well be a false trail, but in such case maybe we will be able to find the correct one.
Another idea:
Make sure there are no leftovers from an older version of Corona on your PCs - go to Windows “Programs and Features” list, uninstall Corona Renderer, and then install 1.7 again. Make sure 1.7 is installed on all computers taking part in DR, and make sure that you are using DR server 1.7 on all of the nodes.
This happens with both phys and corona cam. Wasn’t an issue prior to 1.7. Has been like this since the daily builds and still persist after clean 1.7 final build on both workstation and rendernode. Images renders fine when just using workstation or the node via backburner (no DR). Will try and send you some DR logs.
To all users with this issue (masking elements coming out “mixed” with other ones), or similar:
We have just released Corona Renderer 1.7 Hotfix 1: Renderer for architectural visualization - Corona | Chaos
It contains some important DR fixes, so please download and install it.
Please make sure that Corona Renderer 1.7 Hotfix 1 is installed on all computers, and that DR server 1.7 Hotfix 1 is running on all of the slaves.
If the issue will remain after installing this version, please contact us, and we will continue looking for a solution.
Do you need to uninstall 1.7 manually?
when I try to install the version tells me that it is already present on the PC
TNKY
Andrea
Are you sure you are installing 1.7 hotfix 1? It has been removed due to a bug we discovered in it just after the release. The download at our website is currently a regular 1.7 version. We will release hotfix 2 asap.
do I have to install what I find :
right here?
Ok, hotfix 2 is out. ![]()
Please download it, and if there are any problems with the installation, remove the older version first (from Windows “Programs and Features”) and then install the new one.