Converter Now Works with LuxCore

I had some time to go over the changes that new update to LuxRender has unleashed.  I am very happy and impressed.  I have been avoiding LuxCore API, as previously mentioned, mostly because node implementation was incomplete.  The gaps have been closed and materials all seem to work in nodes.  There are a few things that may be not implemented at this writing, such as ‘Energy Conserving’ on Matte translucent material, etc.  It may be there with Python, but the node GUI does not show it.

Updating my Converter Code is complete and currently testing with various models and scenes.  The speed of LuxCore 2.7 blows away the Classic API modes with my 3D modeling rig.  I had to update my AMD video card to catalyst 15+ or ‘Crimson‘ to get it to even go beyond freezing up in OpenCL.  I can get it to work with LuxCore now, but not all settings complete.  I haven’t nailed down the best settings to get it to complete a render at all times.  Right now I am getting very fast renders with using CPU settings only.  So far, my favorite render settings in LuxCore are Path engine and Metropolis sampler.  Pulled back the consecutive rejections to 425, with a Power light strategy.  I use 6 out of my 8 cores and let ‘er rip.  I am using a fairly large scene for testing with gobs of materials.

london_OBJ_scene_materials

Yes, that is what I am playing with.  If my Converter does not blow up on that, then I can release it into the wild.  That scene has helped in many ways for correcting and updating code.  It caught lighting conversions I overlooked in some of the simpler scenes I was testing with.  This also has a skydome, which I switched to a hemi HDRI light after conversion.

cvtr_gui_update

I am still testing, especially the different LuxCore settings.  In the meantime, I have uploaded the new updated Converter, which is now version 1.6 here.

Posted under Uncategorized