DirectXTK VS Open-Source Vulkan C++ API

DirectXTK 12 (includes SimpleMath and other goodies)

DirectXTK (basically XNA ported to C++, after it was dropped)

Because you get stuff like DirectXTK and PIX from the company that does the API, while on Khronos stuff you need to go hunting for comunity or GPU vendor specific tooling.

then check up this https://github.com/microsoft/DirectXTK/wiki/Getting-Started

Or the vulkan.hpp RAII samples would be a good place?

For a real-life example: consider the vk::raii namespace of Vulkan-Hpp, where the developers have posted examples. The vk::raii::su namespace has a bunch of free functions that one might think are associated with a Vulkan instance/object (in fact, the Vulkan Tutorial does implement them as member functions), but they are much nicer when used as pure functions. It keeps the class/struct definition itself nice and clean.

VS 2022 has seen a massive increase in performance especially after its move to 64-bit. It lints even the largest headers (ahem, Vulkan-Hpp) in a matter of seconds whereas CLion just chokes and crashes.

So I am attempting to follow the Vulkan Tutorial, but I am trying to use decidedly more C++ than the tutorial suggests, by using the Vulkan-Hpp C++ bindings and the vk::raii classes, in particular.

Its literally a few kb: https://github.com/KhronosGroup/Vulkan-Hpp/tree/master/vulkan Why on earth are you downloading all the samples and what not? Just use the hpp files and be done with it. SMH

All the current major game engines are C++. C hasn't been widely used since the Quake 3 days.

While yes the Vulkan & OpenGL APIs are pure C, that's very, very little of what you actually code against. You very quickly abstract that or use a middleware like bgfx or whatever. In the case of Vulkan while the spec API is C, there's first-class C++ wrappers/bindings provided as well: https://github.com/KhronosGroup/Vulkan-Hpp

And other than Vulkan & OpenGL, you'll find that most other APIs/libraries in the space are C++, not C. Valve's libraries are C++. Dear ImGui is C++. Bullet & PhysX are C++. Microsoft's glTF SDK is C++. etc...

You can argue endlessly about how "true C++" those all are or if they're just "C with namespaces" but that's largely irrelevant - they aren't C and they need a C++ compiler.

Having this on the side and reading the actual implementation is in my opinion the best way to learn about using Vulkan compute and how the different parts of Vulkan are related. On the other hand you need to be at least little bit familiar with concepts of Vulkan (and vulkan.hpp) to understand it and know how would things change if you would change some options.

vulkan_structs.hpp - part of the Vulkan-Hpp library (Vulkan bindings for C++) comes in at 97967 lines of code.

https://github.com/KhronosGroup/Vulkan-Hpp/issues/926#issuecomment-810979142