Velaptor is a code-first, native 2D game development framework written in modern C#. Game development can be unnecessarily complex when managing lower-level infrastructure.
Velaptor abstracts away the complicated, low-level mechanics—like windowing, input handling, content caching, and audio processing—so you can focus entirely on your game logic or multimedia application.
It is designed specifically for engineers who prefer code-driven architecture over heavy, GUI-reliant game engines. This gives you full control.
Cross-Platform by Design: Prioritizes unified cross-platform dependencies to deliver a consistent environment across operating systems, switching seamlessly to native platform-specific implementations where required without exposing complexity to the core API.
Flexible Content Loading & Caching: Natively handles single textures, texture atlas data, and sound content. Loaded assets are cached in memory to optimize performance and prevent redundant disk I/O. The API can be completely extended to implement custom asset loaders.
Extensible & Lightweight: Built on top of robust frameworks like Silk.NET and powered internally by CASL for audio performance.
No UI Bloat: Velaptor is purely code-first. You retain 100% control over your application lifecycle, rendering loops, and architectural patterns without dealing with restrictive editor paradigms.
When building Velaptor, the engineering decisions are guided by a few core principles:
Low Allocation & High Velocity: Constant optimization to minimize garbage collection overhead in performance-critical rendering loops.
Developer Autonomy: Providing clean interfaces and abstractions that allow you to swap out or extend internal systems (like input or content loading) effortlessly.
Explicit over Implicit: The framework avoids "magic" behaviors, ensuring that
initialization, lifecycle management, and resource disposal are clear, predictable, and deterministic.
⚠️ Note: This framework is actively developed and currently in a pre-v1.0.0 preview state. While all major foundational features are operational and ready to use, the API surface is continuously being polished as we march toward a stable v1.0.0 production release.
As a solo creator moving toward a community-backed open-source model, I would love the Peerlist community's eyes on this! I am highly interested in:
Architecture & Code Reviews: Feedback on the rendering pipeline, lifecycle management, and cross-platform structure.
Stress-Testing: Developers interested in testing cross-platform inputs, window scaling, or caching behaviors.
Contributors: Anyone looking to get their hands dirty with performance-critical C# framework development!
Feel free to check out our documentation or grab the preview packages on NuGet! Pull requests, bug reports, and discussions are always welcome.
Built with