NO Bidir OpenCL to choose

Discussion related to the LuxCore functionality, implementations and API.
Post Reply
siyanieyoyo
Posts: 1
Joined: Fri Apr 24, 2020 8:19 am

NO Bidir OpenCL to choose

Post by siyanieyoyo » Fri Apr 24, 2020 9:17 am

for path tracing I can choose CPU or OpenCL, but for bidirectional path tracing I can only choose CPU.
Why is it? Will there be a bidirectional path tracing GPU version supported in the further version?
birdir.PNG
birdir.PNG (4.85 KiB) Viewed 186 times
bidir2.PNG
bidir2.PNG (4.89 KiB) Viewed 186 times

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

Re: NO Bidir OpenCL to choose

Post by Dade » Fri Apr 24, 2020 9:37 am

siyanieyoyo wrote:
Fri Apr 24, 2020 9:17 am
for path tracing I can choose CPU or OpenCL, but for bidirectional path tracing I can only choose CPU.
Why is it?
BiDir is far more complex than plain path tracing to write (and execute) on GPUs. Nowadays, if you enable light tracing with Path tracing, you can get similar results in a shorter time and with GPU support: Path+Light tracing is a simplified form of Bidirectional path tracing.
siyanieyoyo wrote:
Fri Apr 24, 2020 9:17 am
Will there be a bidirectional path tracing GPU version supported in the further version?
It doesn't look worth doing when you have access to Path + Light tracing (+ PhotonGI caustic cache where you can render even paths BiDir can not).
Support LuxCoreRender project with salts and bounties

Post Reply