I've been waiting for Vulcan related videos to pile up. You are doing great job. Thanks man.

Can you also make a video on how to compile shader text into spir-v from c++? And thanks for the series btw. I have watched your whole series on vulkan that you have previously made and learnt quite a lot from it.

Cool man. Finaaaally we come closer to render something. One question, what's your onboard GPU? I have to manually switch to my onboard NVIDIA A1000 for this to work. Seems like something older couldnt work though.

@GetIntoGameDev

Ай бұрын

I know right! Hoping to get something visible onscreen before I leave the country next week. On my windows machine I've got an RTX 3070, mac doesn't support shader objects as they're quite a new feature, haven't had a chance to try them on my integrated GPU yet.

@dell_p1

Ай бұрын

@@GetIntoGameDev haha, no wonder why you switched from the Mac one. Turns out, something older which doesnt support DX12 is sufferring from the same issue. here in my case is Intel UHD 770 one. What I see here is, the program on my machine complains about "VK_KHR_shader_object" extension. I think I must update the is_suitable function to make some switch here and there... Good job as always. Hope you have a great day.

Sir can you pls help me! I am following the vulkan tutorial and in the swap chain recreation chapter when we check if the swap chain is out of date then we call the recreate function and we return out of the render loop. Why are we even returning out of the render loop. Pls answer

@GetIntoGameDev

Ай бұрын

Great question, does the program work if you don't return from the loop? Does it give any validation errors? My guess is that the current work on the queue needs to be completed before the swapchain is recreated.

So you are telling me there is no more VkPipeline? Why are we using setters instead of assigning the properties ourselves like in other vk objercts?

@GetIntoGameDev

Ай бұрын

You're still welcome to use vkPipelines if you like! I just didn't find it was worth the extra fuss. As for setters over direct assignment, no particular reason, I was just surprised to see setters so I used them.