PATHHW

Discussion related to the LuxCore functionality, implementations and API.
Post Reply
User avatar
Dade
Developer
Posts: 4249
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

PATHHW

Post by Dade » Fri Apr 17, 2020 3:12 pm

Today, I have achieve another major step toward CUDA support: (RT)(TILE)PATHOCL now uses LuxRays for all interactions with the GPUs (i.e it doesn't include any direct call to OpenCL API anymore).

This means the once I have completed the LuxRays support for CUDA, (RT)(TILE)PATHOCL will auto-magically work with CUDA too. So the "OCL" in PATHOCL name is now outdated and it should be replaced with a generic "HW" suffix in the future(i.e. we are going to need some nomenclature change once all this work is finished).

This work is currently on "cuda_rendering" branch.
Support LuxCoreRender project with salts and bounties

User avatar
lacilaci
Donor
Posts: 1913
Joined: Fri May 04, 2018 5:16 am

Re: PATHHW

Post by lacilaci » Fri Apr 17, 2020 3:29 pm

:D just pathGPU contrary to pathCPU should be fine, no?

User avatar
Sharlybg
Donor
Posts: 2009
Joined: Mon Dec 04, 2017 10:11 pm
Location: Ivory Coast

Re: PATHHW

Post by Sharlybg » Fri Apr 17, 2020 4:13 pm

lacilaci wrote:
Fri Apr 17, 2020 3:29 pm
:D just pathGPU contrary to pathCPU should be fine, no?
Yes ! i have seen a lot of people thinking that luxcore doesn't support Nvidia card because it is opencl. completely HS thinking but we should care about clear naming.
Support LuxCoreRender project with salts and bounties

Portfolio : https://www.behance.net/DRAVIA

User avatar
Dade
Developer
Posts: 4249
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

Re: PATHHW

Post by Dade » Fri Apr 17, 2020 5:00 pm

lacilaci wrote:
Fri Apr 17, 2020 3:29 pm
:D just pathGPU contrary to pathCPU should be fine, no?
To be totally accurate, OpenCL supports many type of accelerators: GPUs, CPUs, FPGA, etc. I think you can also run CUDA on CPUs too. So we may need a quite generic name.

P.S. Technically, it is more PathMIMD (Multiple Instructions Multiple Data) Vs. PathSIMD (Single Instruction Multiple Data).
Support LuxCoreRender project with salts and bounties

User avatar
lacilaci
Donor
Posts: 1913
Joined: Fri May 04, 2018 5:16 am

Re: PATHHW

Post by lacilaci » Fri Apr 17, 2020 5:07 pm

Dade wrote:
Fri Apr 17, 2020 5:00 pm
lacilaci wrote:
Fri Apr 17, 2020 3:29 pm
:D just pathGPU contrary to pathCPU should be fine, no?
To be totally accurate, OpenCL supports many type of accelerators: GPUs, CPUs, FPGA, etc. I think you can also run CUDA on CPUs too. So we may need a quite generic name.

P.S. Technically, it is more PathMIMD (Multiple Instructions Multiple Data) Vs. PathSIMD (Single Instruction Multiple Data).
I understand but lets be realistic here.

People recognize in general gpu and cpu rendering. So if you're on mac-os you will expect metal, win+gtx you will expect cuda, win+rtx you will expect optix, win+amd = vulkan? . If anyone ever expect anthing from opencl i don't know, but name it pathmimd and pathsimd and people will not know what is going on for sure.

Maybe even take it a step further and drop bidir and tilepath, and lets call it LuxGPU and LuxCPU :D

kintuX
Posts: 558
Joined: Wed Jan 10, 2018 2:37 am

Re: PATHHW

Post by kintuX » Fri Apr 17, 2020 10:55 pm

Code: Select all

PATHXPU
would, could do... ;)

marcatore
Donor
Posts: 404
Joined: Wed Jan 10, 2018 8:04 am

Re: PATHHW

Post by marcatore » Sun Apr 19, 2020 7:35 am

I'm with lacilaci.

A simple LUXcpu and LUXgpu is more than enough for everyone.
Than, if you want to be more precise and make culture, it's possible to add any more technical information in the wiki.

Post Reply