instead of compiling every shader as a build step, how about like lets say try to figure out if its modified, then if it is, compile it? can we do something like save every shader file's last modify date and then compare them, if its newer then it means its modified. then we only compile those?

This is a great tutorial. However, one question I have is on the lve_device files. This file was not create in the last tutorial and it is not discussed in this tutorial, nor are we asked to download it. Obviously we need it to make this example work, so I downloaded it from the github repository. Is the creation of this file discussed in another tutorial?

Hey I might have missed it but is there a particular reason that we want to represent every operation as a linear transformation? Is it just so that we can evaluate the composition of all the transformations into a single matrix?

I keep getting this error on arch linux: libdecor-gtk-WARNING: Failed to initialize GTK Failed to load plugin 'libdecor-gtk.so': failed to init

Nice explanation, thank you.

The vkCreatePipelineLayout throws an segmentation fault

The 3 body problem will be solved in 3D VR Maths #Metaverse

Darn.. this series never progressed far enough to teach textures 😅

This, along with Cem Yuksel's 3D Transformation video really explains the subject well. I've reviewed this subject multiple times throughout the years but I gotta say, this 2-step approach (perspective projection = perspective transformation + orthographic projection) is IMHO the most intuitive and easy to remember way of teaching/studying this subject. Most books/resources tend to focus on deriving the perspective projection matrix from the ground up, often times skipping the inherent connection to orthographic projection. Thank you for a job well done. Cheers!

It made an actual spiral, this is really cool

4:32 because you changed the path, cmake doesnt recognize the source files before regeneration, and reopening vscode automatically generates cmake files. You can just regenerate from command palette

I'm using Visual Studio 2019 and I can't figure out how to add a custom build step. Anyone have any luck with that?

I have tried to implement the projection and view matrix in my vulkan application but my screen still blank even after using this method.

hey was there ever a "device setup" video made about the classes you created?

3 years after, this is still a Masterpiece, following the tuts rn. I can already tell you play a small part in changing my life. And for that, I want to thank you.

The 3 billion body problem.

if i stretch the window to be 0 pixels tall then it stops accepting input

So in the end the frustum matrix is simplified to a ‘pyramid’ matrix so that angles from the center are displayed with respect to their tangential value. Right? 😅

great tutorial but how come its B8G8R8A8 not R8G8B8A8?

Imagine if you could do this with games like Sims 3 or Sims 4!!!

Tutorial 1 had 150k views, this, the second to last tutorial only has (almost) 10k views, only 7% of people actually finish (I didn't do last tutorial, because people probably skipped ahead and just watched to see what they were making, as its got a lot more views than this.

you... are.. the shit bro, str8 up. This is simply amazing, ty for making these videos. You should follow it up with a part two of an engine creation but instead of vulkan using glfw for 3d graphics in a window, you should do it for OpenXR technologies, focusing on either PCVR or better, the Android / C++ native implementation of OpenXR for the meta quest 3. I am learning a lot from you, as opposed to the numerous books I could not quite grasp fully until I found your videos.. not even in the university I attend have I learned as much as I have in the past 20 summin videos of yours I binged in 4 days.. so far thanks

Could ChatGTP help you to continue with Vulkan tutotials?

How to make the makefile? What’s .env?

Wow, these drawings are so cool, they have a 2000's vibe. Nice.

I’m working on my NEA project but I am super confused, can I get any contact details to ask for help? Or can you suggest any tutorials that could help me understand this?

where have discord ink

in what coding language?

The way you say homogeneous is strange, I know its the proper way, but its not fluid, hum odge unis

how does the non linear z buffering effects the light calculations? or are they too small to care about?

If anyone is wondering "Why is he doing most of the legwork for us - HOW WILL I EVER LEARN MYSELF?!!!!" .... Let me tell you ... I had that same thought. So I stopped watching this series and put it to one side. I then proceeded to go through the Vulkan-Tutorial chapter by chapter, reading everything and typing it all out...line....by....line. It was a freaking painful SLOG. 1000+ lines of code later, most of which I barely understood what I was copying out (and I'm an experienced C++ programmer just new to graphics) and you've JUST ABOUT rendered a simple triangle on the screen. It's a real motivation killer and I think that is EXACTLY what Brendan's example code aims to solve. Tuck away the excruciating detail in a few classes and let the learner understand the core concepts rather getting bogged down in why the VkImageViewCreateInfo::subresourceRange.baseMipLevel must be '0' in this particular example. I'm still working through some of the final chapters / more advanced topics, and I have a 'better' understanding on things but the reason I've now gone back to re-watch/continue this video series is to actually learn what the heck I was just typing for many hours :D

The problem with this tutorial is that this is a Vulkan tutorial. Although this series is most likely completed, I wanted to point out that what makes copying code so bad is that it's defeating the entire purpose of Vulkan, by copying code which is integral to Vulkan and what actually makes Vulkan it's own. The main goal of Vulkan is not to render a cube, this could be done with OpenGL or any other API, but what makes Vulkan different from an OpenGL tutorial is it's verbose low level design like setting up a logical device, etc. You can't learn a language like Spanish by using google translate. Of course this is just my opinion but again the viewers should not be dependent on downloaded code that they don't understand as beginners, which should have been the main talking points of this tutorial. Anyways that's my only issue with it, I do really like the quality of this series and how beginner friendly it is (excluding the copying).

What is advantage of uniform buffers over storage buffer? If it has so big limitation in size, which big loose over storages, there should be something bad side of storage buffer over uniforms. What's that?

4:00 "Since we've not using Vulkan" I assume you meant to say OpenGL?

Wooot!! Red triangle!! I gotta call home for this. Hey Mom! check this out😅

Making a vulkan game engine by myself just wanted to see how to link it lol

I'd like to use something like this for my game, you have to find a ring in a haunted house but the townsfolk are terrified of the ghosts. the ghost is not all that scary but he IS mean however, so you could defeat it by using a magic stone. Once you defeat the ghost another quest could show up to defeat a demon that is in a building

I love your tutorials! I am following the official Vulakn Tutorials but I think it is hard for me to understand how it works. Your explanation is very clear!

Great explanation!

Your videos are some of the best on 3D programming!

Bruh made a whole universe

This is almost the perfect derivation of perspective projection (especially since it includes both the off-axis and FOV versions!). However, I wish you would have talked more about why applying the first perspective transform gets us into a space that allows for trivially transforming with the orthographic projection matrix. It doesn't seem intuitive to me. Firstly, I think it would have helped to emphasize that multiplying by n and dividing by z actually turns the slanted edge of the frustum into the right-angled straight edge of the desired rectangular prism because everything on that will end up landing at the exact same x value (or y, for the top, respectively). Secondly, however, we should note that what we get after multiplying with our perspective matrix is *not* a 3D rectangular prism, since its components haven't been divided by the w component (i.e. z value) yet. It's a seemingly somewhat arbitrary 4-dimensional entity, and so it's unclear from my limited linear algebra skills why doing the perspective divide and then applying the orthographic projection is equivalent to doing the orthographic projection and then the perspective divide. There seems to be a deeper "truth" to homogeneous coordinate equivalence that is more than just a notational convenience. If you had touched a little on that, this would have been the de-facto, perfect explanation.

Are you the same person as Joseph Anderson? The guy who makes game critique videos? You sound so similar...

6:55 why isn't that possible exactly?

Brilliant video.

This is beautiful! What happens when its in 3D though?

This represents our world peace! Galaxy collisions!!!🐼🐾

Bro got me good with the code to download, unfortunatelly for me, im implementing the tutorial with other names so i'll take my time translating everything. Still think that i`ll end up learnng a lot, so thanks!!! I`m really enjoying thinks so far! Edit, it was actually very fast, nice.

opengl looks down the positive z-axis? it is the y-axis that are swapped?