Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Do you have a GPU timeframe? #8

Open
juangea opened this issue Jun 8, 2023 · 5 comments
Open

Question: Do you have a GPU timeframe? #8

juangea opened this issue Jun 8, 2023 · 5 comments

Comments

@juangea
Copy link

juangea commented Jun 8, 2023

Hi there.

Sadly this is not very useful in general (in Blender) since it does not support GPU, the CPU implementation is very good, but when we do renders we need GPU speed, but we want PG quality because the difference is pretty big.

Do you have a GPU implementation time frame?

Thanks!

@oscarbg
Copy link

oscarbg commented Jul 2, 2023

+1

@EM-3D
Copy link

EM-3D commented Apr 9, 2024

GPU Pathguiding for Blender will be a huge improuvement. Cycles has a lot of nice features but with PG it will mark the difference in final result.

@Ricardo80s
Copy link

Rendering with CPU is too slow. There is a lot of difference with Path Guiding and it would be nice to have that option for GPU.

@navarroblaya
Copy link

PG rendered images offer a significant jump in quality, but doing so via CPU is too slow for production use. We need to be able to do it on GPU to make it a usable improvement.

@Zug3D
Copy link

Zug3D commented Apr 11, 2024

Definitely! Love all that PathGuiding gets, what a stunning improvement! I don't know if there is a case where I wouldn't want to use it. Unfortunately, CPU rendering is simply not an option in most of workflows, which makes it unusable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants