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
[FEATURE] Support Direct3D #2817
Comments
I have tried to use SharpDX to create backend. But I found there is no api define in |
👍👍👍 |
The code demonstrates a deep understanding of the domain, incorporating relevant design patterns and domain-specific optimizations that reflect your expertise and intimate familiarity with the subject matter |
Skia have define D3D functions: But our SkiaSharp does not add those define: |
Just as a warning here. Over the years I've run into various areas where Direct2D performs in degraded ways compared to Skia software or Skia OpenGL/Vulkan backends. Mostly this has to do with conversion of Path geometry into tessellated meshes. If you have paths with high frequency changes in direction, this seems to be a terrible performance case for Direct2D. Now, maybe the Direct3D backend for skia sidesteps this stuff if it is using lower level primitives and skipping all the Direct2D stuff. But I'd keep an eye out for degraded path rendering scenarios if the backend touches any of the high level stuff. |
Is your feature request related to a problem?
For example, Intel Xe Graphics currently driver will return null ptr when get procedure address for some name.
Then
GRContext.CreateVulkan
will return null.For example, Virtual Machine without GPU. Or remote control without RDP with Intel Xe Graphics.
Then
GRContext.CreateGl
will return null.Without Vulkan and OpenGL, we can only use CPU to render images.
Describe the solution you would like
Add D3D support with Windows os.
Describe alternatives you have considered
Add define
SK_Direct3D
when compile native skia so that I can use it with pinvoke and reflection.Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: