raylib VS ComputeSharp

Fetch Packages... raylib... ./ray_test_zig/build.zig.zon:7:20: error: url field is missing corresponding hash field .url = "https://github.com/raysan5/raylib/archive/refs/tags/5.0.tar.gz", ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ note: expected .hash = "1220c28847ca8e8756734ae84355802b764c9d9cf4de057dbc6fc2b15c56e726f27b",

libGDX is great, but I can understand if it's not for some people. This also applies to love2d, raylib and Monogame

Raylib library

Here is a cool C project you could learn from: https://github.com/raysan5/raylib Its an open source game lib.

Did I miss something or is raylib 5 really coming next saturday? https://github.com/raysan5/raylib/commit/737cd0be7fb009bf837a00847128b00051c5f096

RayLib (ZLIBL/C/Lua) https://github.com/raysan5/raylib

A couple other options than what has been suggested so far: - TerraFX.Interop.Windows. Raw, blittable, 1:1 bindings for all Win32, D2D/D3D11/D3D12 APIs (there's also a version with Vulkan bindings). As close to doing #include as you can get in C#. This is my personal favorite, I use it in my own ComputeSharp library, and transitively we use it in the Microsoft Store too 🙂 - Silk.NET another version of high-performance bindings, more opinionated than TerraFX and with some additional helpers to make it a bit easier to use.

A hello world .NET console app with NativeAOT is 1.08 MB. Goes down to 1.08 MB with some tweaking. Goes below 1MB with more tweaking. I have a fully self-contained NativeAOT sample app that renders some fancy animated shaders with DX12 that's about 2MB in size.

I dont think it's exactly what you're looking for, but I've found ComputeSharp to be a great C# GPU tool

Here's some: - MVVM Toolkit - PolySharp - ComputeSharp

If you don't mind being Windows only, I would also recommend trying out (shameless plug) ComputeSharp. You can find it on NuGet and it's available for UWP and WinUI 3 as well with ready to use XAML controls. The point is that it would allow you do your entire rendering via pixel/compute shaders, so it could basically run entirely on the GPU. That'd allow you to render even millions of particles with pretty good performance 🙂

Create a UWP or WinUI 3 applicaation and use the AnimatedComputeShaderPanel from ComputeSharp. The library lets you write shaders (ie. code to run on the GPU) entirely in C#, and handles all the logic to setup a DX12 animated swapchain, similar to Win2D. If you look at the repo you can also see a whole bunch of examples, which you can also try out for yourself. There's also several wiki pages with lots of info.