Видео

Walker William Perez Melissa Smith Donald

Bro I barely passed my exam in calculus and still after years I didn't understand the nature of derivatives and integral. UNTIL NOW! Thank you so much for the video!❤

This didn't work, just like every other tutorial. I don't know what I did wrong. edit: I ended up needing 2 extra steps to get it to work. This did help, though

Aleluia! quero ouvir um amém? 🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣

Thanks

best teacher in the world

Awesome work thanks!

Didn't know I wanted to make a PS1 game until I saw this video 😆 your work is always top-notch, Gustavo!!

Awsome content, helped me a lot, made me laugh too "zmol"

You, blew my mind today.

I honestly love these explanations. Maybe i am a mongrel, but not using fancy words before explaining them works for me. I dont know why people cant do that normally 😊

if you're using a square, wouldn't the normal of a side be in the exact same direction (but opposite magnitude) as the normal on the oposite side of the square? you only have to do 2 calculations for squares instead 4 if i undserstand this correctly.

Thank you for making these videos available

Thanks for this informative video. It’s the best video about how to start game engine dev journey.

I’m writing a simple 3D game right now for fun but it was time to implement physics and was struggling until I found an old PDF explaining Verlet integration. The PDF was great, but as I searched on Google for a couple questions I had, RUclips started recommending stuff and that’s how I found this video. This was amazing. Such a great explanation. I’m going to go back and watch the rest in order (watched all of this and also just watched your video on Calculus at the beginning of this playlist) I was pretty happy with the results of my initial (very simple) implementation converting the code to work in 3D, but I still need to implement more to support collisions with polygons, angular momentum, etc. You are a fantastic teacher. I’ve been up all night wondering how I’m gonna implement angular momentum but I have ideas now. I’m also very curious about stability (especially in 3D which seems very prone to instability?) I noticed you have a physics engine course! With a baby I only get an hour here and there to work on this stuff so not sure if I’ll be able to watch the 35 hours- but planning to buy just to support this work and maybe I’ll be judicious about which ones I watch. I can try fill in gaps in my knowledge enough to help me with my project.

I took Calculus I & II in college and did decently (got A & B). I feel like you explained calculus more clearly in 30m than in the entire semester I took it. 😂

Thanks for your great videos. I was trying to access your website and get the ps1 course but it just times out when i click the link

I was wondering, how easy is it to add rotation to these verlet objects, making one in scratch and I feel like that will make it stand out

Great video!! I’m starting to understand 😅😅🫡🫡

This is really good video.

This is an under rated teacher. The amount of knowledge i have collected just from a few hours of watching these videos is probably more than the knowledge i got from my college syllabus. Thanks.

Martin Angela Wilson Eric Hernandez Karen

@pikuma I tried a constraint that is more 'fluid', it continues the velocity of each particle off the wall by reflecting the path, not just hard resetting onto the wall. I tested it in your code and the box hit the wall, bounced a bit and then stayed there flat against the wall, so it seems more stable than the hard reset. What do you think? On line 46 onward you can test } else if (this.x > SCREEN_WIDTH) { this.x = SCREEN_WIDTH - (this.x - SCREEN_WIDTH) this.old_x = SCREEN_WIDTH + (SCREEN_WIDTH - this.old_x) } ...

Hallelujah.

Great video. How does one introduce mass into this equation though?

It's not quite right that the fps doesn't matter as long we use some kind of deltaTime. I run into this problem lately where i didn't activated frame-cap and the game run over 12000 fps. I started and just let some ball bounce and it was somehow wrong. Activating a frame-cap made it right. The problem is simply that running at extremely high fps can lead to extremly small floating point values and floating-point arithmetic starts to break. I guess it is important because not restricting frames and starting with a new project where you literally do nothing will always yield extremely high fps.

Trying to learn to debug 16 bit Assembly programs. The very few GDB tutorials assume you are working in C or C++. Would appreciate any info on how to debug an Assembly program. Got GDB working but can't figure out how to display the program code if it's not an .exe

Why would we want to use a matrix for translation at all? It's just three addition operations.

amazing 👏👏👏

01:04:21 the formula of delta y is wrong, its missing + operator after pl.y

This is really really helpful, I am going to buy your course as well 😊

How can this transfer to, say, 3 dimensions, instead of 2D, for cases of working with a 3D OpenGL/C++ engine?

drghtfbyxc

You're a good teacher

This thing is perfect for Shaders and Compute shaders

Hallelujah! Lots of fun doing it!

damn i have to drop this comment praising how valuable this is. Amazing, truly amazing that you take your time to explain this

feel like theres a filter

Great video! One way of explaining perspective correct texture mapping that was particularly effective for me is as follows: Consider two quads of the same screen-space shape. For a given set of 2D coordinates, you could have either a small object up close, or a very large object far away, mapping to the same exact screen-space position. The close up object will have fine details visible, and the details of the far away object will be harder, or impossible to see, but a 2D rasterizer will have no way to differentiate between these two objects. This is because of depth. Vertexes are affected by depth, the further away they are from the camera, the closer in 2D coordinates they will become, and of course the same must apply to the details of the object (texels). Texels that are further away must be shrunk according to depth.

First, we do not need matrices to calculate Xp and Yp. Matrices will not do much if you do not understand how to manipulate the 3d vertices without them :) Aspect ratio is not needed at all, because you do not change the aspect ratio of displayed objects. In real life cameras eye and lense does not care about aspect ratios - the fov angle is always the same. zfar is not needed at all. People stop complicating easy things.

Looks awesome. Also implemented some stuff of it. But one thing i don't understand is why acceleration is multiplied twice with dt. When i calculate the velocity then it is the velocity between two frames. This is why velocity is divided by dt to get the velocity for one second. But as we are frame dependent we multiply again by dt. So in the end the division and multiplication of dt cancels and we just can add the velocity as it already is the velocity for one frame step. Same goes for acceleration. I would just add (acceleration * dt) to get the acceleration for one frame. But in Verlet it has to be (acceleration * dt * dt). Why?

Great lessons, thank you! About your end question: pseudo racing game (Top Gear, Outrun, Chase HQ, etc).

I love u omg. Best lecture abput homogenous coordinates

Amazing video! Thanks for sharing all that detailed knowledge with us! Gracias, Gustavo!

pretty sure aspect ratio is w/h. or am i mistaken?