What's interesting, is that when testing on linux I get this strange "The Vulkan spec states: commandBuffer must not be in the recording or pending state" Error which I can't get to disappear. The app and resizing is functioning, and I wanted to ask if I should be bothered. (Tested on Ubuntu 24.04 WSL, made using g++ just after the "Updating drawFrame()" section, implemented both fixes in the pinned comment)

Please continue this series, Finding this type of series is like finding a four leafed clover. I understand it's tying to create videos so take your time but do please continue it, We are still waiting for the shader tutorial.

Vulkan the struct heaven. Gives me joy every second

Why you didnt used an r-tree?

Great resource. Thank you.

nice job! so to get it exactly right is impossible for even 3 particles, right? No matter how small you make the steps, there will always be leakage. because all the interactions in between are being skipped. That math just doesn't exist, no matter how super your supercomputer. At least, that's how i thought it works.

guys, I have been a c/opengl dev for a long time. I wanted to upgrade to vulcan, so I started writing cpp. I noticed that the readFile returns a vector of char. Why can't it return an std::string?

can somebody explain this in easy explanation like what exactly the need of homogenous coordinate system .. like why we need an extra dimesion ?

Good Content!🤩

in 15:40 I open the window, the triangle start very fast , but when i re-size the window , the triangle become slower , is this normal ?

when I try to compile the shaders (on windows) I get the following error Error: no binary generation requested (e.g., -V) (use -h for usage) I can't seem to figure out how to solve this problem.

we still wait for texture tutorial and other stuff😇

can anybody help me setup on mac

Makes it looks like a galaxy. or a cluster in fact. a real genuis implementing that kind of optimization. insane how you can run that many at once. how you run it i feel like the clock speed of the cpu divided by 1000 equals the amount of particles.

I keep getting a linker tools error even though I copied the entire files it keeps failing to run if I build with the device

great series, I was wondering wether some future episode might cover mesh/taskshaders or using hlsl instead of glsl

I love you.

But doesn't it mean that people playing this game with your api key will actively burn your money? It's unsustainable to release game like this

Fantastic Content... Thanks so much!. To get it to work on my Mac I had to add something a bit hacky to createInstance() ..... perhaps there is a better way, but this fixed it anyway. createInfo.pApplicationInfo = &appInfo; createInfo.flags |= VK_INSTANCE_CREATE_ENUMERATE_PORTABILITY_BIT_KHR ; /* MJM ADDED */ auto extensions = getRequiredExtensions(); extensions.emplace_back("VK_KHR_portability_enumeration"); /* MJM ADDED */

I guess I do like the sorter videos.

I just discovered this channel and i finally got through episode 0 and 1 over two days. I haven't programmed anything in 6 years. Kinda rusty on the fundamentals, but i think im following along okay sofar. Definitely gonna need to study the basics of c++ while im doing this series.

Hey, Thank you, You helped me great my own Engine :D.

ah youtube compression had a fun time with this one

I have this error: Present mode: Mailbox make: *** [Makefile:63: test] Segmentation fault

quite interesting that despite the implementation classical mechanics being flawed/incomplete, we can still recognizr the forms and shapes of galaxies nontheless

my laptop is heating up watching this video lol

In the end of the last video, you sort of said in the createRenderPass() method, we're passing in VkSubpassDescription subpass with .pColorAttachments and .pDepthStencilAttachment to ultimately create the render pass. The render pass is the blueprint for information for the frame buffer. When did we pass in color and depthStencil information to the frame buffer? Is it in createCommandBuffers() clearValues{}, then clearValues[0].color, clearValues[1].depthStencil? This just clears the values, when did we set the values? Thanks, still just a beginner here.

Can someone explain me from from basics image vs object and its relation with 3D geometry it seams like there should be some connection according to video.

this makes no sense to me whatsoever

n1

I want change the skybox, how i do this?

Seems like the window resizing support costs pretty much if we move the command buffer recording to the render function :c I don't really want to follow those changes but seems like the future changes won't be compatible with the previous one.

By far best tutorial series I've ever watched! It taught me so much - thank you! I really hope you return to making tutorials agian, they are incredible.

I'm not sure if this is correct but I spent a serious 2.5 hours wrapping my head around the matrices section and wanted to save anyone else curious about the details the hassle of putting this together if they didn't want to, but still want to know what's going on. Sorry in advance if this is unintelligible. Also note that glm is in col major format (this caused me some headache figuring out). Thank you for your great series, but for those writing out the matrices remember that vec3 is a column vector and the dot product of 2 column vectors where the u, v, and w are the normalized basis vectors along their respective x, y, and z axis (not real x, y, z, but like a virtual camera x, y, and z), will result in grabbing the scale and therefore translational magnitude of the position, where you can assume that the position is a vector of p.x, p.y, and p.z: The T at the end is the transpose because it's a column vector with RowxCol (MxN) equal to 3x1, not a row vector which it looks like in text. The values here are in respect to the camera view, u.x, u.y, u.z, v.x, etc, should technically be here, but this is for explanation purposes. Column vector(u) = [1, 0, 0]T Column vector(v) = [0, 1, 0]T Column vector(w) = [0, 0, 1]T Column vector(position) = [p.x, p.y, p.z]T This is why you get -p.x, -p.y, and -p.z for this code (at least from the camera's perspective, but it still works when replacing the above orthonormal vectors with their respective u.x, u.y, u.z, v.x, etc.: m_viewMatrix[3][0] = -glm::dot(u, position); m_viewMatrix[3][1] = -glm::dot(v, position); m_viewMatrix[3][2] = -glm::dot(w, position); Altogether, the Rotation, Translation, and View matrices are: Rotation matrix (R): u.x, u.y, u.z, 0 v.x, v.y, v.z, 0 w.x, w.y, w.z, 0 0, 0, 0, 1 Translation matrix (T): 1, 0, 0, -p.x 0, 1, 0, -p.y 0, 0, 1, -p.z 0, 0, 0, 1 View matrix (V): V = R * T u.x, u.y, u.z, -dot(u, position) v.x, v.y, v.z, -dot(v, position) w.x, w.y, w.z, -dot(w, position) 0, 0, 0, 1 In the code, you negate the value to translate back to the origin (or think of it like traversing to position x, y, z via the position vector and then you negate the values to travel backwards where the arrows lead you to where you came from). Also, the normalize is omitted from v because it is implied since w and u are already orthogonal to each other and facing their respective coordinates. If you took the cross of u, w (backwards instead) you would be getting the opposite direction when using the right hand rule, so order matters.

Great Tutorial! Please continue this!!

In this video I dont understand how duplicating a vertex position twice will allow for the face to be colored in one color

Hi, I have been following your tutorial lectures well, but I have a question. I exported the Suzanne (monkey) model from Blender as an OBJ file and rendered it, but it is rendered upside down. The OBJ file you provided renders correctly, but why is this happening? I suspect it is due to the difference between the OpenGL viewport and the Vulkan viewport. How did you solve this issue?

What if you used that engine to simulate millions of particles, but you combined it with particle life? also 8:53 is a clear example of conservation of momentum, and how galaxies start spinning.

Is there a way to talk to you about it? Because I couldn't find your email or related

I was initially confused about perspective matrix involving orthographic matrix, since we didnt do any calculation for perspective involving ortho in the code, then I realised it was already done for us :D would it be fair to say the following?: 1. there are TWO types of projection matrices here, orthographic and perspective. 2. there is ONE type of transformation matrix here, which is the perspective transform matrix. 3. we can use the orthographic projection matrix on its own, OR we can combine it with the perspective transformation matrix to create the perspective projection matrix

awesome series tysm i finally reached the end. would love to see textures be covered in the event you return to this tutorial series 🎉

is this last video of the series ?

The indices were not creating the cube. I had to change them to: ModelBuilder.Indices = { 0, 1, 2, 0, 3, 1, 6, 5, 4, 5, 7, 4, 10, 9, 8, 9, 11, 8, 12, 13, 14, 12, 15, 13, 18, 17, 16, 17, 19, 16, 20, 21, 22, 20, 23, 21 };

I had to reorder the vertices in the cube for the Right, Top, and Nose faces for it to render correctly.

1, why do I need a orthographic volume 2, why do I need to convert it? 3, why do I need a matrix? 4, have you ever coded before? 5, when you go to college but never actually program 6, you do not need to know this to program a viewport, college jipped you.

i really just watched this entire video even though it felt like someone was rambling into my ear while i was daydreaming 😂

Is this specifically how to project a scene into the Vulcan format?

I get the following at the end of the video when I build and run: Validation Layer: Validation Error: [ VUID-VkGraphicsPipelineCreateInfo-renderPass-09028 ] Object 0: handle = 0xee647e0000000009, type = VK_OBJECT_TYPE_RENDER_PASS; | MessageID = 0x4d0c2b9f | vkCreateGraphicsPipelines(): pCreateInfos[0].pDepthStencilState is NULL when rasterization is enabled and subpass 0 uses a depth/stencil attachment. The Vulkan spec states: If renderPass is not VK_NULL_HANDLE, the pipeline is being created with fragment shader state, and subpass uses a depth/stencil attachment, and related dynamic state is not set, pDepthStencilState must be a valid pointer to a valid VkPipelineDepthStencilStateCreateInfo structure (vulkan.lunarg.com/doc/view/1.3.290.0/windows/1.3-extensions/vkspec.html#VUID-VkGraphicsPipelineCreateInfo-renderPass-09028) I went back through this tutorial again, but I didn't find anything that I missed. Any help is appreciated.

why did you stop this tutorial serie : (

Dude, sick video! I watched it like a year ago, and since I've been getting into compute shaders and stuff for the past year, I was inspired to try myself. For the first one, I tried doing regular parallelized incrementing, which got me about 50 000 particles at 60 fps. Then, I tried with a version of what you did, where each particle compares itself to a lower resolution texture which represents densities in larger areas, and that got about 1 000 000 particles at 60 fps, but it was a bit inaccurate since I learned you can't reliably increment (texture[xy] += 1) on the GPU, which is obvious in hindsight. So then I did exactly the same method you did in this video, and I just gotta ask, why did you stop at 4 mill? On mine, I was able to get 200 million before even dropping below 60 fps. 4 mill got about 140 fps, and the only thing that prevents me from running more than 260 million is the CPU cache size. This was using a few compute shaders in unity. Still, great video and great execution of the simulation, I'm just genuinely curious why you didn't do more particles.