vulkan-guide VS Vulkan-ValidationLayers

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.

If this works then it might actually be a game bug and the game I guess passes invalid shaders when the cache exists... but it seems to work fine on windows vulkan drivers. You could try to run the game with https://github.com/KhronosGroup/Vulkan-ValidationLayers

For debugging these kinds of issues, I would recommend enabling the synchronization validation layer.

I would use the debugger to produce a stack trace and look into the validation layers source code. https://github.com/KhronosGroup/Vulkan-ValidationLayers Then I would either file an issue or make a PR there.

Currently validation layers might generate false-positive errors: https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/3450

A'rightey... I was able to reproduce this issue with Sascha Willems basic triangle example, so I am fairly certain, that this is a bug. I've opened an issue.

I am really at loss here, I found this issue but it doesn't really help me (I am starting to doubt it's even possible, maybe I'm a clown and doing it wrong...)

Can you post a reproduction case at https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues so we can take a look at it.

Which is why a GPU debugger with frame tracing is so much better option.

By the way, there are actually ways to expose a print function on shader code, provided there is driver support.

https://github.com/KhronosGroup/Vulkan-ValidationLayers/blob...

Huh yeah. Looking through the header the function you want works with c but there are others using c++ features. The reason given is understandable.