vulkan-guide VS AMDVLK

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.

Budeš je muset sám compilenout z open source kódu.

If RADV hangs rdr2 at the moment you can temporarily switch to amdvlk, you can also switch on a game-to-game basis without rebooting or anything. You can get it from the release section of their github: https://github.com/GPUOpen-Drivers/AMDVLK. But keep in mind that amdvlk will make itself the default as long as you have it installed.

Other parts of the stack can be released, and I'd bet anything that AMD's vulkan driver, amdvlk, is at least very similar to the windows implementation, just with a different PAL backed by whatever the windows systems are instead of libdrm.

Switching from RADV to AMDVLK fixed the issue. I haven't noticed any performance differences once the shaders are compiled.

Looks like an issue with a more recent version of amdvlk (https://github.com/GPUOpen-Drivers/AMDVLK/issues/278). Some people resolved by uninstalling amdvlk, but I was able to launch it with amdvlk still installed by using the launch options settings I've provided with this report.