vulkanizer
drmingw
vulkanizer | drmingw | |
---|---|---|
6 | 2 | |
545 | 269 | |
- | - | |
0.0 | 6.4 | |
23 days ago | 4 months ago | |
C++ | C++ | |
MIT License | GNU Lesser General Public License v3.0 only |
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.
drmingw
-
Thanks, I hate manual stack traces
Try Dr.Mingw instead. I've been using this for years, for applications that cannot be run within a debugger (usually started as a Windows service).
-
I don't think it's just me, but MS4 keeps quitting on me out of nowhere
Install Dr. Mingw https://github.com/jrfonseca/drmingw. Whenever Musescore4 suddenly crashes, Dr. Mingw should attach to it and provide a backtrace. Like:
What are some alternatives?
SoftwareRenderer - Software rendering engine with PBR. Built from scratch on C++.
libbacktrace - A C library that may be linked into a C/C++ program to produce symbolic backtraces
tinyrenderer - A brief computer graphics / rendering course
meshoptimizer - Mesh optimization library that makes meshes smaller and faster to render
HybridRenderingEngine - Clustered Forward/Deferred renderer with Physically Based Shading, Image Based Lighting and a whole lot of OpenGL.
GamePlay - Open-source, cross-platform, C++ game engine for creating 2D/3D games.
polymer - 🎨 graphics/interaction prototyping sandbox
VulkanMemoryAllocator - Easy to integrate Vulkan memory allocation library
bgfx - Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.