vulkan-guide VS The-Forge

I totally agree, and so do the people working on it as well as some of the volunteers who write tutorials.

There's an ongoing effort to create beginner friendly introductory material which was discussed in the recent Vulkanised conference. And an effort to make a better documentation site that's easier to browse than the specification.

On the volunteer front, there's a Vulkan 1.3 -based introductory tutorial (work in progress) over at https://vkguide.dev/

I think there should be a Vulkan tutorial that doesn't start with the boring stuff of initialization and window creation. It's stuff that you write once and forget about, and nothing particularly interesting happens in it.

Looking at my hobby project, excluding the boring stuff (which is reusable), a "hello compute" example is around 100 LOC and a "hello triangle" around 120 LOC. GLSL shader sources included.

Maybe someday I'll get around to writing a "learn Vulkan the hard way" blog post with examples.

Also, use https://vkguide.dev/ rather than vulkan-tutorial.

Once you're beyond the "introductory" phase, resources become more specialized based on what you'd like to learn -- there are Vulkan tutorials like https://vkguide.dev/ which will teach you the API and also give a bit more insight in how modern GPU hardware is structured, there are books like the "GPU Zen" series that do deep-dives on specific techniques, and there are tons of recorded GDC and SIGGRAPH talks on interesting new techniques. :)

Personally, I'm a hands on learner who actually wants to use this stuff in my career, so I'd recommend these tutorials: https://learnopengl.com/ https://vulkan-tutorial.com/Overview https://vkguide.dev/

vkguide teaches some good practices regarding code/renderer structure, but I'm afraid it doesn't go as deep as you'd like. It's certainly deeper than most other tutorials, though.

https://vkguide.dev/ This is my favorite.

Oh, I forgot a few major ones:

https://github.com/ConfettiFX/The-Forge was used in No Man's Sky, Hades and Starfield.

https://github.com/jrouwe/JoltPhysics is the physics engine in Horizon Forbidden West.

To my understanding, every source I've read says that this should cause issues, but in practice it doesn't. What gives? Did I miss something? Here are multiple examples using the latter approach.

This is a toy project that I've been working on for the past few months. Essentially, I've rewritten all the rendering code for the engine using BGFX. This means that all the fixed function OpenGL 1.2 code has been removed from the engine. BGFX supports OpenGL 3.3 and DirectX11, but there are still some rendering artifacts with DirectX11, so the engine still uses OpenGL when running on Windows. I've been considering switching to The Forge (https://github.com/ConfettiFX/The-Forge) if I want to have more control over the rendering pipeline. However, this is a complex topic with significant implications for the codebase. I've already done the hard work of eliminating clumsy abstractions in the engine and simplifying the render pipeline, so it's just a matter of deciding what direction I want to take.

The-Forge might fit:

So, I'm not sure if it is widely known, that Starfield is going to be running on a lot of "The Forge." The creators of The Forge says it was added to Creation Kit in 2019. This will open a LOT of new systems for Bethesda games.