it works
Luxcore 2.1 Benchmark
Re: Luxcore 2.1 Benchmark
It works now, thank you!
Nevertheless I have a warning:
Material "Glassxgo green": 'bpy_prop_collection[key]: key "Gamma" not found'
Nevertheless I have a warning:
Material "Glassxgo green": 'bpy_prop_collection[key]: key "Gamma" not found'
Re: Luxcore 2.1 Benchmark
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'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
I guess, the error didn't pop-up with f12 but viewport rendering triggered it
Re: Luxcore 2.1 Benchmark
Yes, you're right.
I can live with that warning.
(Don't wanna go through all the materials...)
Re: Luxcore 2.1 Benchmark
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.
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
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.
Sounds like the image is screwed up during the compositing stage?
-
- Supporting Users
- Posts: 141
- Joined: Tue Jan 09, 2018 6:48 pm
Re: Luxcore 2.1 Benchmark
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
4 min, 46 sec on four 7950's.