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

Add support for Direct2D Compute Shaders #351

Open
rickbrew opened this issue Aug 15, 2022 · 1 comment
Open

Add support for Direct2D Compute Shaders #351

rickbrew opened this issue Aug 15, 2022 · 1 comment
Labels
proposal 💡 A proposal for a new feature untriaged 🧰 A new issue that needs initial triage

Comments

@rickbrew
Copy link
Collaborator

Filing this for ... the future :)

At some point I'll want to start dipping my toe into compute shaders so I can convert the remaining CPU-based effects in Paint.NET over to the GPU. These effects require the use of compute shaders because they need to build a local histogram.

https://github.com/MicrosoftDocs/win32/blob/docs/desktop-src/Direct2D/custom-effects.md#adding-a-compute-shader-to-a-custom-transform

@rickbrew
Copy link
Collaborator Author

rickbrew commented Mar 2, 2024

I have converted my remaining CPU-based effects over to the GPU by using compute shaders. Sadly without ComputeSharp.D2D1! But that means I am eager to port my interpolated strings over to proper CS.D2D1 shader structs, and I have compute shader HLSL code that can be used to validate this effort.

(btw "eager" does not mean "omg I need it now", there's not actually any time pressure here)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal 💡 A proposal for a new feature untriaged 🧰 A new issue that needs initial triage
Projects
None yet
Development

No branches or pull requests

1 participant