วีดีโอ

🎉

I found it really difficult to find good vulkan tutorials but yours are very easy to understand and well explained. Would be awesome if you could explain the code a little bit more for people not as experienced with C++

This series is awesome! Please don't stop doing these tutorials like other youtubers.

thank you for this! any chance you'll be working with the new dynamic rendering / shader objects extensions? they're pretty new but supposedly provide a much nicer API for working with vulkan. they can even provide a render-pass-free workflow

I'm a little confused about the difference between vk::Instance and VkInstance. You said that VkInstance is the "handle," I assume this mean whatever data is necessary to identify the instance in the driver/gpu. Then what is vk::instance? Is that also a handle?

I also appreciate that you are focusing on structuring the program. I would love if you keep focusing on that + renderer structure if the series continues to some more advanced rendering

Thanks for this series, I wasn't planning on learning vulkan, but I think it might be fine if I follow along with you. Though, I would honestly prefer if you had one repository where you hosted the code, and made one commit per episode. It would make it easier to track the changes between them.

yo, i think they updated winit since this tutorial was posted, since they removed window::WindowBuilder, and moved window creation to be done by the ActiveEventLoop, which is available as a parameter of a required function for the implementation of the ApplicationHandler trait. i will admit i'm not very experienced with rust. i like this change because its more readable in my opinion, but i'm having a lot of difficulty figuring out where i need to create the wgpu surface for example (inside the ApplicationHandler resumed function? in a struct that the app which implements ApplicationHandler will have ownership of?) i would love to see a working example of a simple program that uses wgpu and winit with these changes. please, any tips of a point in the right direction would be appreciated 🙏

Thanks great work.

Please keep doing this course, it's so good it's a hidden gem, i have been struggling a lot with Vulkan and i already understand better by just watching your 2 videos :D

Hi there loving the series so far but I keep running into the following error message when I try and run the shaders: File "C:\Users\Gamer\AppData\Local\Programs\Python\Python39\lib\site-packages\OpenGL\plugins.py", line 18, in load return importByName( self.import_path ) File "C:\Users\Gamer\AppData\Local\Programs\Python\Python39\lib\site-packages\OpenGL\plugins.py", line 45, in importByName module = __import__( ".".join(moduleName), {}, {}, moduleName) File "C:\Users\Gamer\AppData\Local\Programs\Python\Python39\lib\site-packages\OpenGL\arrays umpymodule.py", line 28, in <module> from OpenGL_accelerate.numpy_formathandler import NumpyHandler File "src/numpy_formathandler.pyx", line 1, in init OpenGL_accelerate.numpy_formathandler ValueError: ('numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject', 1, <OpenGL.platform.baseplatform.glGenVertexArrays object at 0x000001A746009DC0>) I've copied and pasted the code from the github and the same message comes up so I have no clue what to do from here. I really hope this is an easy fix and that someone can help. Thank ypu

nice new intros!

You don't need to copy anything. Instead of indexing, use a method get_mut.

There is so little knowledge about metal out in the web so thanks for recording this series!

inverse kinematics... for hair...?

I'm truly perplexed how this affected performance in any direction except negatively... please help :) What was described on paper, putting every single cube and transformation into a single class of multiple arrays, shouldn't be any different from having each in an array in a different class - the objects of that class should still be references to their components, with each pointer still being O(1) since there are no list traversals, and each object in the heap would be stored contiguously. And given the size of the arrays we'd expect from all transformations, unless we preallocate a HUGE amount of memory space, we're still going to be hindered (speed and cache misses) by the single virtual memory space being separated throughout the core. If, instead, you're truly creating a single OBJECT with all of the cubes and transformations in a single set of arrays, I'd expect the still constant time calculation of the indices for lookup to be at least twice as computationally intensive as pointing directly to them. Not to mention - if this is all a single array - what this would do to insertion and removal times! Even implementing with a search tree instead of an array should still be slower, if I'm understanding this correctly (which I am clearly not :D) Is this just a python thing, to trick the interpreter into doing what you want? I've never done graphics programming, and I know nothing about how Python works under the hood... someone please explain what I'm getting wrong here :)

Damn! The beginning is like something out of a "House of Wax" movie. Creepy. :)

Do you plan on trying out vulkan.hpp's unique pointers? You won't have to do much cleanup with them :)

Also, you can consider WebGPU instead of Vulcan

Glfw is cool and all but there are no tutorials related to SDL3

Please Please Please stop this course because C++ is stupid language, should not use any more, Please re-do this course but by Rust language please 😘😘😘😘🥰🥰🥰🥰

i found your intro sequence with paper sketches and voiceover to be impressive

I was watching the Python and OpenGL tutorial series, how did I get here? 💀

Cloth physics should be similar to this right?

Cool, I guess you can speed it up substantionally by storing everything in numpy annd processing without "for" loops

I was just thinking about boobs, perfect timing for this video

I'm gonna bookmark this video. Will need this later

I just learnt Metal off this channel, then I look for a WebGPU tutorial series and you're here again! Thanks :D

this will really boost my characters' personality! uh, please disable autofocus and autoexposure lol

not super interested in implementing this, but the physics behind it is certainly... interesting!

Very important work

Pls vulkan.h plsplsplsplsplsplsplsplsplsplsplsplsplspls you already have a series that uses vulkan.hpp so can't u use vulkan.h this time.

What a time to be alive

Look like boob bone in blender.

I'm running into a problem with this lesson. My code so far appears to be exactly how it should be up to video 2 (this one) But, when I hit compile I just get a blank Python window with out the triangle showing up. I was wondering if anyone could give me some advice on what I'm doing here that might be a roadblock I can't see.

Well, this columns are so confusing in the code. I should have taken Javascript classes before starting to learn WebGPU. I thought my C/C++ knowledge would be fine for the whole course.

How hard to run a Xcode template😅

I would suggest using a printf-like function for the logger. In c++ it is pretty easy to do using templates. It reduces the print calls a lot. It's something like template<class ... Args>

That content is amazing we love to see you work on it. For record I don't think it's much but the app pointer never gets deleted. And cleared. Love your work.