Hi,
i dont know,
i will work this afternoon without slaves and will see.
Version 2.22.2 - TEST3 - Updated on 03.04.15
Moderators: ChrisHekman, aoktar
:::::::::::::::::
pxlntwrk.net
pxlntwrk.net
What options do it, because I need this working on 6 computers and ASAP. We have a very specific workflow for consistency and I do it 10-30 times a day. Until I figure out how to do it, I'm screwed. So what do I need to play with, render layers? Passes? What? The shadows are entirely too black rendered with Alpha and shadow catcher.aoktar wrote:Hi,rodross wrote:Switching from 2.16 to 2.22.2, I can't keep my environment background anymore while having my Alpha still...how do I fix this. I need this feature many times a day here at work.
It's removed and will not be available no longer.
You should play with other options to get what you want.
It's not removed by me. You should use environment render pass to get environment+alpha.rodross wrote:What options do it, because I need this working on 6 computers and ASAP. We have a very specific workflow for consistency and I do it 10-30 times a day. Until I figure out how to do it, I'm screwed. So what do I need to play with, render layers? Passes? What? The shadows are entirely too black rendered with Alpha and shadow catcher.aoktar wrote:Hi,rodross wrote:Switching from 2.16 to 2.22.2, I can't keep my environment background anymore while having my Alpha still...how do I fix this. I need this feature many times a day here at work.
It's removed and will not be available no longer.
You should play with other options to get what you want.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
I know. Ok I'll try that. Hopefully that gives me the lighter shadows. The environment isn't really that important to me, it's the fact that it makes sure the shadows aren't ridiculously black.aoktar wrote:
It's not removed by me. You should use environment render pass to get environment+alpha.
We're going to have to revert our whole farm and workstations back to 2.16.
Our process is as follows:
-Set HDRI to a studio with a gray floor
-Disc as poly floor for shadow catcher with matte material
-turn on alpha
-render
-take into photoshop or Ae and use alpha to delete everything but objects and shadows then replace background with 80% gray
I do this to 5-30 animations and stills in a day. I cannot use 2.22.2. Unless there is a quick way that I'm not seeing, using alpha still creates nasty dark black shadows. I love the new features, but we don't have time to add 2 extra steps to each still or animation: Render Alpha, Environment, and shadow passes, then composite it all and lighten shadows. Nor do we really want to double or triple the space used for each thing we render by saving more img sequences for shadows and/or env. If there is a way to have ONE file, with an alpha layer and not black as night shadows, just like the renderer used to do very well, then I would love to know. In the meantime, we'll have to revert all of our computers back to 2.16.
Our process is as follows:
-Set HDRI to a studio with a gray floor
-Disc as poly floor for shadow catcher with matte material
-turn on alpha
-render
-take into photoshop or Ae and use alpha to delete everything but objects and shadows then replace background with 80% gray
I do this to 5-30 animations and stills in a day. I cannot use 2.22.2. Unless there is a quick way that I'm not seeing, using alpha still creates nasty dark black shadows. I love the new features, but we don't have time to add 2 extra steps to each still or animation: Render Alpha, Environment, and shadow passes, then composite it all and lighten shadows. Nor do we really want to double or triple the space used for each thing we render by saving more img sequences for shadows and/or env. If there is a way to have ONE file, with an alpha layer and not black as night shadows, just like the renderer used to do very well, then I would love to know. In the meantime, we'll have to revert all of our computers back to 2.16.
Can you post a scene and a render result of what you are doing in 2.16? Thanks.rodross wrote:We're going to have to revert our whole farm and workstations back to 2.16.
Our process is as follows:
-Set HDRI to a studio with a gray floor
-Disc as poly floor for shadow catcher with matte material
-turn on alpha
-render
-take into photoshop or Ae and use alpha to delete everything but objects and shadows then replace background with 80% gray
I do this to 5-30 animations and stills in a day. I cannot use 2.22.2. Unless there is a quick way that I'm not seeing, using alpha still creates nasty dark black shadows. I love the new features, but we don't have time to add 2 extra steps to each still or animation: Render Alpha, Environment, and shadow passes, then composite it all and lighten shadows. Nor do we really want to double or triple the space used for each thing we render by saving more img sequences for shadows and/or env. If there is a way to have ONE file, with an alpha layer and not black as night shadows, just like the renderer used to do very well, then I would love to know. In the meantime, we'll have to revert all of our computers back to 2.16.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
This is 100% network render related, I'm getting the same nasty looking output when using Net render, no issue when using the local machine.abstrax wrote:Does this also happen, if you disable network rendering?pxlntwrk wrote:Here, kind of glitches i have sometimes in PV since i have updated from 2.14 to 2.22.2 t3 ( never happened like this before )

Nodes are all running 2.22.2
Main rig is Win 8.1 / Nvidia 350.05 / R16.038
cheers
brasc
Rig#1 Win 10 x64 | GTX 1080Ti | GTX 1080Ti | GTX 1080Ti | i7 7900K 4.7GHz | 64GB
Rig#2 Win 10 x64 | GTX 1080Ti | GTX 1080Ti | GTX 1080Ti | i7 3930K 4.4GHz | 32GB
Rig#3 Win 10 x64 | GTX 1070| GTX 1070| GTX 1070| i7 2600K 4.8GHz | 32GB
Rig#2 Win 10 x64 | GTX 1080Ti | GTX 1080Ti | GTX 1080Ti | i7 3930K 4.4GHz | 32GB
Rig#3 Win 10 x64 | GTX 1070| GTX 1070| GTX 1070| i7 2600K 4.8GHz | 32GB
Could you please send me the scene? And which OS and GPUs are on the master and on the slaves?brasco wrote:This is 100% network render related, I'm getting the same nasty looking output when using Net render, no issue when using the local machine.abstrax wrote:Does this also happen, if you disable network rendering?pxlntwrk wrote:Here, kind of glitches i have sometimes in PV since i have updated from 2.14 to 2.22.2 t3 ( never happened like this before )
Nodes are all running 2.22.2
Main rig is Win 8.1 / Nvidia 350.05 / R16.038
cheers
brasc
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
I couldn't reproduce this problem here. Maybe use the driver 350.12. 350.05 is not a WHQL driver. If the driver is not the problem, please send me the scene so I can try to reproduce the issue with that. Thanks.brasco wrote:This is 100% network render related, I'm getting the same nasty looking output when using Net render, no issue when using the local machine.abstrax wrote:Does this also happen, if you disable network rendering?pxlntwrk wrote:Here, kind of glitches i have sometimes in PV since i have updated from 2.14 to 2.22.2 t3 ( never happened like this before )
...
Nodes are all running 2.22.2
Main rig is Win 8.1 / Nvidia 350.05 / R16.038
cheers
brasc
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Hi Abstrax, sorry for the delay.
I've worked out that it's VRAM related, so I inadvertently maxed out the VRAM on the slave (Titan & 2x780ti) which lead to the nasty errors, when I dropped the output resolution and therefore the vram it doesn't show the error! Should there be a fallback to just not use the ones that can't fit the RAM?
It's currently late here, I'll zip up the scene and PM you a link first thing.
cheers
brasc
I've worked out that it's VRAM related, so I inadvertently maxed out the VRAM on the slave (Titan & 2x780ti) which lead to the nasty errors, when I dropped the output resolution and therefore the vram it doesn't show the error! Should there be a fallback to just not use the ones that can't fit the RAM?
It's currently late here, I'll zip up the scene and PM you a link first thing.
cheers
brasc
Rig#1 Win 10 x64 | GTX 1080Ti | GTX 1080Ti | GTX 1080Ti | i7 7900K 4.7GHz | 64GB
Rig#2 Win 10 x64 | GTX 1080Ti | GTX 1080Ti | GTX 1080Ti | i7 3930K 4.4GHz | 32GB
Rig#3 Win 10 x64 | GTX 1070| GTX 1070| GTX 1070| i7 2600K 4.8GHz | 32GB
Rig#2 Win 10 x64 | GTX 1080Ti | GTX 1080Ti | GTX 1080Ti | i7 3930K 4.4GHz | 32GB
Rig#3 Win 10 x64 | GTX 1070| GTX 1070| GTX 1070| i7 2600K 4.8GHz | 32GB