vulkanizer
GamePlay
vulkanizer | GamePlay | |
---|---|---|
6 | 2 | |
545 | 4,357 | |
- | 0.5% | |
0.0 | 0.0 | |
22 days ago | 3 months ago | |
C++ | C++ | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vulkanizer
-
Two-Pass Occlusion Culling - Blog Post
You can find its implementation on my GitHub page and you can follow me on Twitter for more graphics related stuff.
-
[Part 7] Update of my Vulkan renderer: LODs, Multiple different meshes, Memory Allocator, Render architecture and more
You can follow my progress on Twitter and Git. You can find more screenshots and videos over there.
- [Part 4] Update of my Vulkan toy renderer: Mesh Shader Pipeline, Reversed-Z Depth Buffer, SPIRV-Reflect and many more
-
Part 3 update of my new Vulkan toy renderer. More info in comments.
You can follow my journey on Twitter and GitHub.
-
Part 2 update of my new toy Vulkan renderer
Part 2 update of my new toy Vulkan renderer: Implemented Programmable Vertex Fetching, Vertex size is significantly smaller now (12 Bytes), Normals use only two 8 bit vector components where the third component gets reconstructed in the shader, Vertex positions and UVs are 2 Bytes in size, started using VK_KHR_push_descriptor which is much nicer to work with compared to traditional descriptor sets. Sebastian Aaltonen gave a very good explanation for Programmable Vertex Fetching. Normals use only two 8 bit vector components where the third component is reconstructed in the shader. You can follow my journey on Twitter and Git.
-
I started implementing modern Vulkan renderer
I recently started working on my toy Vulkan renderer. The plan is to implement many modern graphics and Vulkan features along the way. As a starting point I made a single mesh renderer and basic CPU/GPU profiler. You can follow my journey on Twitter and Git.
GamePlay
-
Alternative Game Engines for Marooned Unity Developers
Gameplay: Another promising MIT licensed engine for both 2D and 3D. Doesn't seem like there is much in the way of learning material though.
-
Libraries
GamePlay
What are some alternatives?
SoftwareRenderer - Software rendering engine with PBR. Built from scratch on C++.
flixel - Free, cross-platform 2D game engine powered by Haxe and OpenFL
tinyrenderer - A brief computer graphics / rendering course
Godot - Godot Engine – Multi-platform 2D and 3D game engine
drmingw - Postmortem debugging tools for MinGW.
Cocos2d - Cocos2d-x is a suite of open-source, cross-platform, game-development tools utilized by millions of developers across the globe. Its core has evolved to serve as the foundation for Cocos Creator 1.x & 2.x.
meshoptimizer - Mesh optimization library that makes meshes smaller and faster to render
ClanLib - ClanLib is a cross platform C++ toolkit library.
HybridRenderingEngine - Clustered Forward/Deferred renderer with Physically Based Shading, Image Based Lighting and a whole lot of OpenGL.
nCine - A cross-platform 2D game engine
polymer - 🎨 graphics/interaction prototyping sandbox
Polycode - Polycode is a cross-platform framework for creative code.