Hazel VS Vulkan-Samples

I used a workflow template for MSBuild-based projects. When doing this lab exercise I referred to this video by TheCherno, who used the same template for his Hazel Game Engine developed using Visual Studio. The Microsoft Build Engine, MSBuild, is what Visual Studio uses to load and build managed projects. Since I'm also developing my project using Visual Studio, this template seemed like the best option.

Don't write a full blown abstraction, you won't use it. Also Hazel is a great game engine which relies on Vulkan that you could use as well.

And sometimes I feel like 50% of those are copy-pasted from Hazel, which is also far from being commercially viable, despite its popularity.

They're coming from the precompiled header in that project: https://github.com/TheCherno/Hazel/blob/dcdbfe13ac1d06a1650f66719cb4f79ecf310c85/Hazel/src/hzpch.h

https://github.com/TheCherno/Hazel there's a youtube series following the development of this engine, and other useful series on the same channel

Also, I just created premake configurations for the Vulkan SDK. Actually, this is only for the shader compiler and spirv-cross, so there might be more stuff from the SDK to be added.

IIRC, all those engines provide an ECS that could be compared to entt.

Also, there is Hazel[0] which is based on entt and is the subject of an amazing youtube series[1].

IMHO, tinier means less features, at that point what could be considered comparable?

  [0] - https://github.com/TheCherno/Hazel

Vulcan is a driver-level API. It competes with DirectX and OpenGL.

CUDA is a language you write kernels. It competes with OpenAI's Triton language.

Here's what CUDA looks like: https://github.com/tspeterkim/flash-attention-minimal/blob/m...

This is what Triton looks like: https://triton-lang.org/main/getting-started/tutorials/06-fu...

By contrast Vulcan looks like this: https://github.com/KhronosGroup/Vulkan-Samples/blob/main/sam...

(It's true to some extent that maybe you could use Vulcan shaders to write deep learning kernels, maybe? I'm not aware of anyone doing it though)

Hi, i'm looking into descriptor indexing and was looking at the Vulkan-Samples repo. I finally thought i understood how the set binding invalidation works (like a stack?). In the code below both the non_uniform_indexing pipeline and the update_after_bind pipeline use the immutable sampler descriptor in their fragment shader. But since the descriptor set = 0 is rebound, won't the immutable sampler in set = 1 from the "non_uniform_indexing" pipeline be "disturbed" and have to be rebound?

and see if it works.

[1] https://github.com/KhronosGroup/Vulkan-Samples/blob/main/sam...

In this new sample, we see how to incorporate the Vulkan extension VK_EXT_mesh_shader and introduce per primitive culling in a mesh shader. https://github.com/KhronosGroup/Vulkan-Samples/tree/main/samples/extensions/mesh_shader_culling

Also beginner here, I think you can learn other's codes to get a better understanding of the API by learning how others can abstract these concept into higher level. They're many great projects out there like Google's pbr renderer filament https://github.com/google/filament, AMD's gltf sample https://github.com/GPUOpen-LibrariesAndSDKs/glTFSample and also as many suggested, the Sascha Willems's repos https://github.com/SaschaWillems and the official sample https://github.com/KhronosGroup/Vulkan-Samples

Another way I saw some projects start was by using example base classes (either Sascha Willems' implementations or the framework used by Khronos Samples).