Render module to consider ?

Here's the place for discussion related to coding in FreeCAD, C++ or Python. Design, interfaces and structures.
User avatar
zbigg
Posts: 136
Joined: Tue Dec 19, 2017 1:11 pm

Render module to consider ?

Postby zbigg » Mon Apr 09, 2018 4:43 pm

cheers,
User avatar
yorik
Site Admin
Posts: 12238
Joined: Tue Feb 17, 2009 9:16 pm
Location: Brussels, Belgium
Contact:

Re: Render module to consider ?

Postby yorik » Mon Apr 09, 2018 9:59 pm

Wow, fork/new version of luxrender it seems... It should be easy to adapt then.
User avatar
NormandC
Posts: 18534
Joined: Sat Feb 06, 2010 9:52 pm
Location: Québec, Canada

Re: Render module to consider ?

Postby NormandC » Tue Apr 10, 2018 1:20 am

More info on LuxRender.net:

http://www.luxrender.net/forum/viewtopi ... 73#p127888
Why Lux(Core)Render v2.0 ?

Because LuxRender project was dying under the weight of a lot of old abandoned code. All active developers had the strong feeling a fresh start was required. The "Core" between "Lux" and "Render" is there to highlight the new project focus. However the "v2.0" is there to re-mark the continuity with 10 years of development and experience.
And

https://luxcorerender.org/history/
User avatar
zbigg
Posts: 136
Joined: Tue Dec 19, 2017 1:11 pm

Re: Render module to consider ?

Postby zbigg » Tue Apr 10, 2018 5:37 am

A quick test proves its really fast, utilizes both cpu and gpu, supports OpenCL/dont know about CUDA for now/ has nodes etc etc., lack of denosing for now but shall be amended.

A list is short I would say:

1. Cycles - open
2. LuxCore - open
3. Mitsuba -open
4. Kerkythea: outdated, /developed now only as commercial Thea Render/,nodes??
5. CadRays -semi-open, nodes??
cheers,