LuxRender v1.5RC1 release

News & Announcements regarding releases, features, exporters and project coordination.

Moderators: Dade, coordinators

Re: LuxRender v1.5RC1 release

Postby J the Amateur » Sun Jun 21, 2015 12:50 pm

burnin wrote:Great work, nice to see it going on well.
Though using LuxCore API (Experimental), Material Preview doesn't work:
NameError: name 'BlenderSceneConverter' is not defined

Classic API works as usual.

Removed all previous versions, cleaned registries, done clean install...
OS: win7, Blender2.75RC2
Is it still on to-do list or should it work already?

Thanks for all.


Take a look at the last few posts where I had the same problem. SATtva's suggestion worked but I needed to also download the latest 1.5 LuxBlend as they accidentally included 1.4 in the installer files.
"Giggidy"
J the Amateur
 
Posts: 63
Joined: Sat Mar 05, 2011 6:59 pm

Re: LuxRender v1.5RC1 release

Postby burnin » Sun Jun 21, 2015 12:56 pm

Ahhhh, OK... works :D
Thank you
burnin
 
Posts: 223
Joined: Mon May 03, 2010 8:04 pm

Re: LuxRender v1.5RC1 release

Postby mib2berlin » Sun Jun 21, 2015 1:10 pm

Hi, first impression, cool.
RC1 is working on CPU with LuxCore API and Biased PathOpenCL and Path OpenCL.
Caching kernel in /tmp is working too.
Render Preview is working with CPU and OpenCL and all Sampler methods.

Building Biased PathOpenCL kernel for GPU need 536424ms and up to 10 GB Ram on my system.
Building PathOpenCL kernel for GPU need 97120ms and about 2 GB Ram.

Testfile: https://www.dropbox.com/s/yb2sa692cunx8 ... blend?dl=0

Render with Classic API and Biased Path OpenCL work with "Extern" LuxGUI but crash Blender using "Intern":

[Lux 2015-Jun-21 19:55:48] Starting LuxRender
terminate called after throwing an instance of 'std::runtime_error'
what(): Unterminated quote in property: opencl.gpu.use


Talk with jensverwiebe about light settings in Lux and understand setting better now.
Still wondering about to bright results using Hemi and a Gain setting of 0.0000001!
Testfile attached.

All test with Luxrender 1.5RC1, included Luxblend and Blender 2.74.

Opensuse 13.2/64
Intel i5 3770K
GTX 760 4 GB
Driver 352.21
Intel opencl_runtime_15.1_x64_5.0.0.57

Thank, mib
Last edited by mib2berlin on Sun Jun 21, 2015 1:56 pm, edited 1 time in total.
Opensuse Leap 42.1/64 i5-3570K 16 GB
GTX 760 4 GB GTX 670 2 GB 361.42 Blender 2.7 Octane 3.0
mib2berlin
 
Posts: 181
Joined: Mon Jun 22, 2009 3:18 pm

Re: LuxRender v1.5RC1 release

Postby acasta69 » Sun Jun 21, 2015 1:44 pm

Thanks for the great work, the amount of new or fixed features is impressive!
Hope I can try it as soon as possible.

Ale
Windows 10 64 bits, i7-4770 3.4 GHz, RAM 16 GB, GTX 970 4GB v376.54
acasta69
 
Posts: 280
Joined: Fri Dec 20, 2013 3:18 am

Re: LuxRender v1.5RC1 release

Postby SATtva » Sun Jun 21, 2015 11:44 pm

mib2berlin wrote:Building Biased PathOpenCL kernel for GPU need 536424ms and up to 10 GB Ram on my system.
Building PathOpenCL kernel for GPU need 97120ms and about 2 GB Ram.

This is a known issue -- Biased OpenCL integrator hasn't been properly split into microkernels yet, so it may put some pressure on OpenCL drivers or even fail in some cases.

mib2berlin wrote:Render with Classic API and Biased Path OpenCL work with "Extern" LuxGUI but crash Blender using "Intern":

Internal Pylux mode may have other issues as well, e.g. imagemap textures aren't likely to work due to image libraries version mismatch with Blender. It was a PITA to work around it for PyluxCore alone, and i'm afraid i don't have neither energy nor time to fix it for Lux Classic internal rendering. And, frankly, i don't see any benefit in using it at all.

mib2berlin wrote:Still wondering about to bright results using Hemi and a Gain setting of 0.0000001!

It depends on the normalization of a specific HDR image. While the Sun lightsource is more or less calibrated to the real Sun lighting output, HDRs are usually provided unitless. There is no issue here, it just how it works, unless you make an HDR itself calibrated to the correct lighting values.
Linux builds packager
聞くのは一時の恥、聞かぬのは一生の恥
User avatar
SATtva
Developer
 
Posts: 7162
Joined: Tue Apr 07, 2009 12:19 pm
Location: from Siberia with love

Re: LuxRender v1.5RC1 release

Postby mib2berlin » Mon Jun 22, 2015 1:36 pm

Thanks SATtva for the information.

Cheers, mib
Opensuse Leap 42.1/64 i5-3570K 16 GB
GTX 760 4 GB GTX 670 2 GB 361.42 Blender 2.7 Octane 3.0
mib2berlin
 
Posts: 181
Joined: Mon Jun 22, 2009 3:18 pm

Re: LuxRender v1.5RC1 release

Postby zukazuka » Tue Jun 23, 2015 5:57 am

The new build is working well.

I am also having a problems using Biased PathOpenCL to compile kernels often is making my system grind to a halt because of memory usage high and it starts using swap file.

The compile kernels is taking a really long time with OpenCL modes.

I noticed it happens more with "Use Blender Texture" and other complex textures - is this an accurate observation?

With really simple scenes with no textures it's really fast... Are there any other steps that can be taken to reduce "compile kernel" time?
zukazuka
 
Posts: 488
Joined: Tue Dec 09, 2008 10:01 am
Location: 西安 China

Re: LuxRender v1.5RC1 release

Postby SATtva » Tue Jun 23, 2015 6:22 am

What GPU are you using?
Linux builds packager
聞くのは一時の恥、聞かぬのは一生の恥
User avatar
SATtva
Developer
 
Posts: 7162
Joined: Tue Apr 07, 2009 12:19 pm
Location: from Siberia with love

Re: LuxRender v1.5RC1 release

Postby Dade » Tue Jun 23, 2015 6:49 am

zukazuka wrote:I noticed it happens more with "Use Blender Texture" and other complex textures - is this an accurate observation?


Yup, the kernel source are tailored on the scene to render (more materials/textures/etc. you use and more code there is to compile and more complex it is).

zukazuka wrote:With really simple scenes with no textures it's really fast... Are there any other steps that can be taken to reduce "compile kernel" time?


The "compile kernel" is a OpenCL driver task and it is out of our control. LuxRender has a kernel cache so you need to re-compile the kernels only if you have some "important" change (i.e. type of materials used, type of texture used, etc.).

A problem under our domain is the meaning of "important" change: at the moment is a bit too large and includes also some detail that may be worth to avoid in the future (for instance, changing the image resolution will trigger a new kernel compilation).
User avatar
Dade
Developer
 
Posts: 8298
Joined: Sat Apr 19, 2008 6:04 pm
Location: Italy

Re: LuxRender v1.5RC1 release

Postby zukazuka » Tue Jun 23, 2015 7:23 am

Is this long compile kernel thing just a Nvidia problem or it also happens on AMD?
zukazuka
 
Posts: 488
Joined: Tue Dec 09, 2008 10:01 am
Location: 西安 China

PreviousNext

Return to News & Announcements

Who is online

Users browsing this forum: No registered users and 1 guest