Page 3 of 7

Re: Luxcore 2.1 Benchmark

Posted: Wed Sep 12, 2018 1:17 pm
by lacilaci
B.Y.O.B. wrote: Wed Sep 12, 2018 12:19 pm I uploaded the fixed file. Please test if it works now.
it works

Re: Luxcore 2.1 Benchmark

Posted: Wed Sep 12, 2018 1:50 pm
by provisory
It works now, thank you!

Nevertheless I have a warning:
Material "Glassxgo green": 'bpy_prop_collection[key]: key "Gamma" not found'

Re: Luxcore 2.1 Benchmark

Posted: Wed Sep 12, 2018 2:30 pm
by B.Y.O.B.
Damnit, I forgot one (I guess this only happens in viewport render?)
I'll fix it later.
Anyway, to fix it, you just have to create a new imagemap node, select the same image as on the old node, rewire everything and delete the old node.

Re: Luxcore 2.1 Benchmark

Posted: Wed Sep 12, 2018 2:35 pm
by lacilaci
B.Y.O.B. wrote: Wed Sep 12, 2018 2:30 pm Damnit, I forgot one (I guess this only happens in viewport render?)
I'll fix it later.
Anyway, to fix it, you just have to create a new imagemap node, select the same image as on the old node, rewire everything and delete the old node.
I guess, the error didn't pop-up with f12 but viewport rendering triggered it

Re: Luxcore 2.1 Benchmark

Posted: Thu Sep 13, 2018 7:22 am
by provisory
B.Y.O.B. wrote: Wed Sep 12, 2018 2:30 pm I guess this only happens in viewport render?
Yes, you're right.
B.Y.O.B. wrote: Wed Sep 12, 2018 2:30 pm Anyway, to fix it, you just have to create a new imagemap node, select the same image as on the old node, rewire everything and delete the old node.
I can live with that warning. :)
(Don't wanna go through all the materials...)

Re: Luxcore 2.1 Benchmark

Posted: Thu Sep 13, 2018 8:42 am
by marcatore
CPU (Xeon E5-1650 @3,5Ghz) = 42'58"

GPU Quadro k5200 + CPU = about 11' . I had a problem with the rendering, during the rendering phase the preview was ok, when render finished, the image was completely white.

Re: Luxcore 2.1 Benchmark

Posted: Thu Sep 13, 2018 8:46 am
by B.Y.O.B.
provisory wrote: Thu Sep 13, 2018 7:22 am (Don't wanna go through all the materials...)
The warning tells you the name of the material. Just pin the material node tree in node editor, then search for the material name in the node editor's tree selection dropdown.
marcatore wrote: Thu Sep 13, 2018 8:42 am during the rendering phase the preview was ok, when render finished, the image was completely white.
Sounds like the image is screwed up during the compositing stage?

Re: Luxcore 2.1 Benchmark

Posted: Thu Sep 13, 2018 12:45 pm
by provisory
B.Y.O.B. wrote: Thu Sep 13, 2018 8:46 am The warning tells you the name of the material. Just pin the material node tree in node editor, then search for the material name in the node editor's tree selection dropdown.
OK, thanks

Re: Luxcore 2.1 Benchmark

Posted: Thu Sep 13, 2018 5:36 pm
by jensverwiebe
marcatore wrote: Thu Sep 13, 2018 8:42 am [snip] I had a problem with the rendering, during the rendering phase the preview was ok, when render finished, the image was completely white.[/snip]
Same happens here randomly on linux Mint 19 and NVidia ( 2 x gtx 1080 + gtx 980ti ) as well as on macOS 10.12 NVidia ( amd 7970 + gtx 980 webdriver ).
Switching to non-opencl imagepipeline did not help. No idea atm. what triggers this, but the renderlayer vs. composite is okay.

EDIT1: Found that oddly sometimes the compositor node connection from renderlayer to the colorbalance node gets lost :?: ( did oversee the new denoise slot )

EDIT2: Aah, could be a test error from myself, i disabled denoise for faster seeing the result, so this slot is gone aka connection gets lost.
-> user error, marcatore, can you confirm you did same ?

EDIT3: checked over, the white composite comes from disabling denoise, one must reconnect the renderlayer with plain color output then
( or reenable denoise )

So, false alarm, mea culpa.

Jens

Re: Luxcore 2.1 Benchmark

Posted: Fri Sep 14, 2018 12:49 am
by Sprocket
4 min, 46 sec on four 7950's.