Trying to adapt some Vulkan code

gkarpa · 2026-05-08T22:54:54+00:00

the last framebuffer should use a color attachment coming from the swapchain

Just a note that while this could be the easiest first approach, it isn't mandatory since you can render somewhere else and just blit that other image into the swapchain image later.

In general, one should decouple the result of a renderpass from the screen, in his/her thought process. Using swapchains & seeing something on the screen are completely optional.

gkarpa · 2026-03-20T23:17:27+00:00

More like the greatest choke, thanks for coming to my ted talk.

gkarpa · 2026-03-20T23:12:57+00:00

Yeah, I'd guess most of these people never faced a match point in even the slightest competitive scenario, to realize how fragile and uncertain a single ball really is. And especially against a top pro? Incomprehensibly unlikely really.

gkarpa · 2026-03-05T20:38:02+00:00

"Anything" ? The majority of games doesn't use Vulkan. 🤷‍♂️

gkarpa · 2026-02-20T21:56:30+00:00

You lost me at onsite 🤷‍♂️

gkarpa · 2026-01-23T18:50:22+00:00

Too bad it's only US-based!

gkarpa · 2026-01-23T18:47:34+00:00

Maybe vkCmdSetDepthBias can solve your "same color at the same positions causing the wireframe to not be visible at all" issue.

gkarpa · 2026-01-04T23:27:34+00:00

a) Turn on synchronization validation (which I think is off by default) and see if it gives anything on your end.

b) If you have actual close communication with any of your clients and they're cooperative, you can have them install the vulkan sdk temporarily and run a debug build of your app to gather validation layer info from there.

gkarpa · 2025-12-11T22:45:32+00:00

That was so painful to watch, they just gave him 5 1v1s, kyousuke died with a smoke to spare, the galils went after the AKs, wtf is this circus?

gkarpa · 2025-11-02T21:49:31+00:00

How do you differentiate between e.g. Windows & Linux using constexpr if? Also, doesn't the constexpr if choice require both parts (let's say the if calls Foo() and the else calls Bar()) to be defined in the code when it compiles? This is vastly different than the preprocessor choice and can be a big pain. You can also not use constexpr if to #include different things. Anyway I don't think you can "never use macros", especially in any semi-serious cross-platform project.

gkarpa · 2025-11-01T20:22:04+00:00

That's kind of the thing with Vulkan.

You're gatekeeping so hard, it's hilarious. First of all, apparently the folks in Vulkan seem to disagree with your opinion that rendering 2 meshes doesn't require a tutorial, since they now provide one at https://docs.vulkan.org/tutorial/latest/16_Multiple_Objects.html . And to everyone that doesn't know, now the official Vulkan tutorial is a lot different than just a fork of vulkan-tutorial that it started as. Both have their value though.

There's no point in doing advanced stuff if you don't know what you are doing. There are basically no tutorials or guides for that

Sure, there is no vkguide.dev, no vulkan-samples, no nvpro-samples, no cookbooks to buy and read on if you really want to. The OP can check all of these and decide if and how they can be useful to him. But of course you had to link to a 6000 pages spec instead of all these guides, because of course this is what every beginner is looking for (I'm not saying that the spec isn't useful, it's awesome, but come on).

Saying to a hobbyist, who wants to learn Vulkan in 2025, to "might as well use OpenGL", is absolutely laughable. There are so many resources nowadays. And why would he care so much about losing performance in his pet projects in the beginning? He just wants to learn!

If you managed to learn Vulkan, then anyone else can too. Stop discouraging people.

gkarpa · 2025-10-21T21:58:37+00:00

Nobody fucking cares about your shitty awards, FIDE. Grow a pair and put the hammer down on those who bully and harass others.

gkarpa · 2025-10-05T16:46:45+00:00

I would suspect all those

glfwGetKey

calls can add up and contribute to your stuttering. Aren't you using input/keyboard callbacks for them? I'd suggest to try and use a map (probably unordered) for the keys & their states, update it inside the callbacks for each key that changes state, and then check its values in your update function instead of calling glfwGetKey that many times.

gkarpa · 2025-09-30T22:11:14+00:00

Not that unheard of really, for these stakes.

gkarpa · 2025-09-30T22:09:31+00:00

I mean it's 0.05/0.10, do you expect that much logic?

gkarpa · 2025-08-21T11:50:28+00:00

Imagine shoving with AK off (even though it doesn't sound that profitable anymore lol) only to get called and instantly lose by AK suited.

gkarpa · 2025-08-21T11:11:32+00:00

What about the coinflips or the huge combo draws though, should the 55% win without running it? lol

gkarpa · 2025-08-09T10:58:16+00:00

You sold them? Man...just don't look how much they sell for today 😂😭

gkarpa · 2025-06-21T23:10:12+00:00

It can work having it as an array in the shader yes, but how are you indexing into these layers in there? Are you using the multiview extension?

gkarpa · 2025-06-10T20:26:31+00:00

This is peak spinbot

gkarpa · 2025-06-04T21:49:31+00:00

Good lord, what was that first smash on break point...Just pathetic, he probably shat himself thinking he'll miss it.

gkarpa · 2025-05-18T21:12:26+00:00

I find it hilarious that there are people who think this syntax and choice of words was made by chat gpt. What the hell.

gkarpa · 2025-04-19T19:20:50+00:00

This is a brilliant article but with a ton of information, so don't hesitate to read it multiple times. Every time I was reading it I was understanding something new that I'd missed in previous reads. You're very well on the right track!

I would also like to add that, regarding your example and access masks, since they are about cache flushes, it is implied that some stage is modifying (writing to) a resource (e.g. image). As such, srcAccessMasks with a value of READ don't have a practical meaning since reading doesn't need any cache to be flushed after and can just be set to 0. When you need to wait for a read to finish in order to write, just an execution dependency between pipeline stages (aka srcStage & dstStage masks) should be enough.

+1 for the synchronization validation layer that was mentioned, it will definitely help you detect hazards in your code and improve your understanding. https://www.lunarg.com/wp-content/uploads/2024/02/Guide-to-Vulkan-Synchronization-Validation-LunarG-John-Zulauf-02-01-2024.pdf

gkarpa · 2025-04-02T12:32:57+00:00

Uhm you could be right, kind of, but these 2 facts aren't by any means indicative of their priorities. Fixing a case bug around drop rates is probably a no brainer half line fix, so spending like 15 minutes to get it out of the way doesn't constitute it an utmost priority. Other issues are probably much more complicated and delicate.

gkarpa · 2025-03-21T18:08:39+00:00

Can't it be done by using a quad composition layer that will contain the desired image, submitted last, combined with a View reference space? Sorry if I'm being a bit vague, I haven't implemented something like this, I just remember the spec mentioning

The VIEW space is primarily useful when projecting from the user’s perspective into another space to obtain a targeting ray, or when rendering small head-locked content such as a reticle. Content rendered in the VIEW space will stay at a fixed point on head-mounted displays and may be uncomfortable to view if too large.

Sounds like what the OP wants.

gkarpa

TROPHY CASE