LuxCoreRender Forums

Checked over, can verify following: Its now like a Brontosaurus, aka starts smaller at the beginning, reaches a peak in the middle and the geos down to low renderspeed again. :roll: Odd. My results: GPU GPU.jpg CPU cpu.jpg With hotel i could reproduce your slow render with pascal and maxwell gpu's....

A bit vague what you report, but i would try with/without cpu on a less powerful machine. Very slow compile time. And poor performance compared to CPU.But will add more after testing on AMD GPu. Checked over, can verify following: Its now like a Brontosaurus, aka starts smaller at the beginning, re...

Also notice poor performance on Nvidia GPu. I've to comfirm with a render onn AMD. A bit vague what you report, but i would try with/without cpu on a less powerful machine. NVidia drivers tend to need a bit more "feedpower". I personally can not reproduce less speed generally, can you be ...

Sharlybg wrote: ↑Thu Mar 08, 2018 12:15 pm On my side it happen randomly. It happen on tile/render cpu .....

I can confirm it with tilepathcpu

It occurs also here on windows, but apparently on first render after blender startup only, from second render on everything is ok. Also, it seems it is only the time counter and screen refresh that goes on, not really the render, as CPU usage drops to zero when halt time is reached. Untitled.png He...

Sharlybg wrote: ↑Wed Mar 07, 2018 3:20 pm Render continue after halt time/sampling count.

Also it stop refreshing when it reach halt condition while continue to render.

Cannot reproduce on linux.

Linux users can still test my optimized builds, no crashing, no instabilities so far.

Thanks for the response. The thin film interference I was referring to is the optical phenomenon https://en.wikipedia.org/wiki/Thin_film_interference The OSL shader I was referring to: https://blenderartists.org/forum/showthread.php?403299-UPDATE-v1-6-Cycles-PBR-thin-film-interference-and-metals I ...

@Dade
You erratically wrote "Fitler" ( instead of Filter ) across the commit, just fyi so you won't run into
issue next round of commits.

I recently found some files line endings borked on linux ( touched with windows ? ) I suggest adding * text=auto to .gitattributes It is the default as far as I remember :?: I had exactly the opposite problem with Git replacing CR/LF in .ply (binary format) and corrupting the files. So I had to add...