Luxcore 2.1 Benchmark

Our forum gallery for displaying your finished renders.
lacilaci
Posts: 148
Joined: Fri May 04, 2018 5:16 am

Re: Luxcore 2.1 Benchmark

Post by lacilaci » Wed Sep 12, 2018 1:17 pm

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

provisory
Posts: 7
Joined: Wed Aug 01, 2018 4:26 pm

Re: Luxcore 2.1 Benchmark

Post by provisory » Wed Sep 12, 2018 1:50 pm

It works now, thank you!

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

User avatar
B.Y.O.B.
Developer
Posts: 1466
Joined: Mon Dec 04, 2017 10:08 pm
Location: Germany
Contact:

Re: Luxcore 2.1 Benchmark

Post by B.Y.O.B. » 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.
Support LuxCoreRender project with salts and bounties

lacilaci
Posts: 148
Joined: Fri May 04, 2018 5:16 am

Re: Luxcore 2.1 Benchmark

Post by lacilaci » Wed Sep 12, 2018 2:35 pm

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

provisory
Posts: 7
Joined: Wed Aug 01, 2018 4:26 pm

Re: Luxcore 2.1 Benchmark

Post by provisory » Thu Sep 13, 2018 7:22 am

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...)

marcatore
Posts: 100
Joined: Wed Jan 10, 2018 8:04 am

Re: Luxcore 2.1 Benchmark

Post by marcatore » Thu Sep 13, 2018 8:42 am

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.

User avatar
B.Y.O.B.
Developer
Posts: 1466
Joined: Mon Dec 04, 2017 10:08 pm
Location: Germany
Contact:

Re: Luxcore 2.1 Benchmark

Post by B.Y.O.B. » Thu Sep 13, 2018 8:46 am

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?
Support LuxCoreRender project with salts and bounties

provisory
Posts: 7
Joined: Wed Aug 01, 2018 4:26 pm

Re: Luxcore 2.1 Benchmark

Post by provisory » Thu Sep 13, 2018 12:45 pm

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

jensverwiebe
Supporting Users
Posts: 141
Joined: Tue Jan 09, 2018 6:48 pm

Re: Luxcore 2.1 Benchmark

Post by jensverwiebe » Thu Sep 13, 2018 5:36 pm

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

User avatar
Sprocket
Posts: 20
Joined: Fri Mar 09, 2018 12:31 pm

Re: Luxcore 2.1 Benchmark

Post by Sprocket » Fri Sep 14, 2018 12:49 am

4 min, 46 sec on four 7950's.

Post Reply