28-yr SWE & Architect. Building open-source .NET dev tools. Creator of Velaptor (2D framework) & CASL (audio).

github

Calvin Wilkinson  • Peerlist

<h3>About</h3>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.<h3>Core Features</h3>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.<ul><li>Flexible Content Loading &amp; 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.</li><li>Extensible &amp; Lightweight: Built on top of robust frameworks like <a target="_blank" rel="noopener noreferrer nofollow ugc" class="break-all link-break text-gray-500 hover:underline" href="http://Silk.NET">Silk.NET</a> and powered internally by CASL for audio performance.</li><li>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.</li></ul><h3>Architectural Pillars</h3>When building Velaptor, the engineering decisions are guided by a few core principles:<ol><li>Low Allocation &amp; High Velocity: Constant optimization to minimize garbage collection overhead in performance-critical rendering loops.</li><li>Developer Autonomy: Providing clean interfaces and abstractions that allow you to swap out or extend internal systems (like input or content loading) effortlessly.</li><li>Explicit over Implicit: The framework avoids "magic" behaviors, ensuring thatinitialization, lifecycle management, and resource disposal are clear, predictable, and deterministic.</li></ol><h3>Current Project Status</h3>⚠️ 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.<h3>What I'm Looking For on Peerlist</h3>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:<ol><li>Architecture &amp; Code Reviews: Feedback on the rendering pipeline, lifecycle management, and cross-platform structure.</li><li>Stress-Testing: Developers interested in testing cross-platform inputs, window scaling, or caching behaviors.</li><li>Contributors: Anyone looking to get their hands dirty with performance-critical C# framework development!</li></ol>Feel free to check out our documentation or grab the preview packages on NuGet! Pull requests, bug reports, and discussions are always welcome.