New Managed DirectX bindings
amerkoleci opened this issue · comments
Hi @xoofx ,
Due to inactivity of SharpDX I've decided to start new DirectX bindings but with some standard stuff.
- I target net standard 2.0 and use mathematics from System.Numerics (Vector2, Vector3, etc).
- Use Unsafe instead of Interop patching.
- API strict to native C++ API so porting will be easy.
- Won't bind Direct3D9 probably nor Direct3D10.
- Not sure about XAudio or Multimedia framework.
- No DirectInput, DirectSound, DirectManipulation, DirectComposition or RawInput.
- Will support recent Windows 10 SDK and I plan to add raytracing support as well.
- I took some approach from SharpDX for some bindings part.
The repo is here: https://github.com/amerkoleci/SharpWindows
And here you can see some example of API usage: https://github.com/amerkoleci/SharpWindows/tree/master/src/samples/Vortice.SampleFramework
If you want you can update README with links to thoose bindings.
I've been looking at the back log of issues raised on Sharpdx and I will be trying to be more active in contributing back into Sharpdx with my own pull requests. But their seems to be a backlog of pull requests that haven't been dealt with.
Sharpdx I feel is pretty integral to game dev. Hopefully we can look at clearing the contribution backlog and get things moving.
Gl on the new bindings. If you get your Ray tracing support working, would be good to see how this can be pushed back into Sharpdx at some point.
So, why doesn't M$ take care of this? It's their API. It's even their freaken programming language. -.-
This wrapper is maintained by a 3rd party @xoofx who has put alot of time into it. Slimdx before that I believe was from MIT. MS really hasn't shown any interest since they dropped interest in their own C# DX APIs.
So xoofx has done a lot of work bringing this to the community. It's now the community as a whole who needs to keep this alive.