Look into the Slotmap datastructure to deal with a consistent_id/handle into an array that you can always pack to front where removals and inserts are O(1)

this is awesome, though this does make me wish roblox had shader support...

2:27 You're not using the dx, dy parameters

what's the game in background?

Good work!

Nice stuff. Motivating me to get my project going.

I'm making a game engine too, let's go! 🎉 It's not a game but I'm more focused on making a good game engine.

Wow this is what using in Playcanvas game engine ❤

Cool

just use rust traits

Does mix() just give the average?

thumbnail cringe, heap allocating, casual programmer 🤓

i didnt understand the math, but it works :D

0:09 I felt that

Please do more of these!

Loved the content in the video--as someone who is interested in using the depthBuffer for more effects, like the intersection shader you demoed, this video was/is a fantastic inspiration. My one issue with my watch was the code jumping around in the background. I think out of focus typing may work, if there was greater contrast between it and the writing in the foreground, but where it got really difficult, and unnecessary, was the page scrolling/jumping around. Happy other people liked the effect but it was a hard no for me--the graphics that you made were cool already!

Good info, but one suggestion. Clearer dictation and some effort into improving audio quality. I had to rely on the captions.

W vid

What engine did you use? Would love to mess with shader code

This is put together really well. I hope to see more tutorials from you!

i want to get into game development but then i realise how complex coding languages look to me and i get super overwhelmed lol

Bro forgot he was using C++ which has multiple inheritance lmao

Since it is exponential/logarithmic comparisons for distance, can't you just use square it...? ;w;

Why not just pass an ortho proj matrix and use that to calculate depth? Would that work?

I just got into OpenGL recently, so it's fascinating learning all the tricks about how things are rendered. Amazing idea, subscribed. Using the difference in depth coordinates before vs after rendering the bubble is clever

This is a great video, and I was quite interested in how your approach differs from how I would've done it. I'd like to present an alternative because I think there are a couple flaws with your approach. Those flaws being: - If you placed a sphere centered on the shield, and made it almost the same size, your approach would make the shield light all around despite there being no intersections because of how it uses the depth buffer. - Viewing objects at 90 degree angles makes them not be outlined properly Here's what my approach would've been: - Render the scene like normal - Render a second scene where the shield is opaque blue (textured with noise if desired) and everything else is solid white, only drawing depth for the shield itself. This could be done more quickly when you realize you don't actually have to render anything other than the bubble, you can just render the bubble on a white background using the depth buffer as a mask - Blur the shield render - Blend the normal and shield render using the depth mask of both renders That way the white from the second render would sorta bleed out around the edges of the object, and the blur step, or colors of the render could be customized to make it stronger or less strong. Of course, I don't mean to suggest this method in bad faith. Your approach is probably still better due to the following flaws of my approach. - Being screenspace, it has the potential to look really weird and not exactly 3D in some cases - Blurring will cause corners to be abnormally bright in comparison to what you might expect - If you wanted to texture the bubble you'd have to render it again because the blur would get rid of any detail, unless you specifically wanted a blurry texture - Objects far in front would still have an outline, which is kinda a REALLY big problem and the main reason why I think your approach is much better. Possibly solvable by some fancy depth stuff but I can't think of a method of ignoring things close to the camera without causing there to potentially be holes in walls I just wanted to suggest another method as I think it could add valuable insight to anybody who wants to achieve this effect.

Omg I love that you jhsd the music from the shapez ost! One of my favorite osts

🦍👍

What's the benefits of storing the data in separate lists when all lists contains data for all entities instead of baking it all into one entity struct? Like the Move function. Why read physics and transform from their lists when they just be part of the entity itself?

I understood nothing but watched the whole thing all the way through 😅

is that shapez music

subscribing

Very cool. I hope one day i can apply the information i got from this video.

This video is incredible, wow! Great explanation and great visualization! Thank you for sharing this with us, this has inspired me to try to implement something similar :D

Subscribed! Thanks for the video!

confused webdev + ovewatch player here - honestly watched the entire before seeing how few subs you had. This was very high production quality and one of my favorite parts was how you showed just random code writing from the project as the unfocused background while focused on a particular snippet. Similar to those goofy subway-surfers-background videos because everyone has a negative attention span.

I was literally looking for this type of videos. Great job ❤

Great video! You did well to recreate the effect and also explain it perfectly

Wait, I understood that...

`virtual ~IComponentPool() = default;` is a bit better than `{}` due to how compilers might look at this line of code

Great video, very accessible. Pleased to see your thorough explanations going into NDC and clip space. In my opinion this is a great example to learn about many aspects of graphics programming at once. Screen-space effects are the backbone of all modern real-time renderers.

this is awesome work!

I've been learning OpenGL for about a year now and this really helped me more than anything. Keep doing this mate.

this was really cool, definitely subscribing to watch more videos like this

suchs good content, earned yourself a sub

this is a fantastic video, and you explained z linearization so well. I have been confused about that exact topic for years, and you just pulled me out of that confusion

Great video! Super informative and interesting. Also love the editting

Man you're hitting it out of the park! The production quality, the substance! Hope you post more like this.

Clear, concise, complete and absorbing explanation - Nice style & editing - Quality video!

Very good video! Really thought the visuals, diagrams, and editing helped succinctly give a good idea of what an ECS is for those unfamiliar. Just wanted to clarify one thing for others and the future. Data Oriented Design is not actually packing data close together, keeping objects in memory linearly is tight packing and linear memory iteration/access. Data Oriented Design is the concept/practice of keeping all data isolated in objects, without any logic, and having functions (usually global functions) operate directly on that data from other sections of code.