Collisions/Tiles/Physics - Pygame Tutorial: Making a Platformer ep. 3

bonk

You lost me on all of the mistakes you that you corrected and when you delete code and move it, you do it so fast with no explanation that it's hard to code along with you. I find myself rewinding it often and having to rewatch it. Right now, I'm stuck trying to get the code to work at the end of this video, correcting all of the mistakes you mentioned with missing 's's and stuff. Good overall series though, just wanted to point out for you to slow down a tad. I would just copy and paste your code, but I have commented my own code in a way that overexplains every bit of your code, which I guess I can xfer over after copying and pasting your finished code.

Thank you for the series, just wanted to provide some feedback. Overall, this is very very good.

Thanks!

my player became too big when i scaled up the resolution what do i do

from where the fuck did you create "tiles" ????????????

In the move() function I noticed that not returning the rect causes a HUGE performance hit over time, but I have no idea why. After a few minutes of the game idle the FPS drops uder 30 and doesn't go back up to 60.

I thought that just changing the values of the rect would be faster, similar to taking the rect by pointer in something like C. Could you explain when to return the changed type or class in python.

Would the collisions be faster if it checks only some points with x and y pos, and without rectangles

ty for giving the source code. I was stuck and it helped! Keep up the good work!

Hi! Lovely tutorial, but was just wondering why you didn't discuss scaling each image when you load it. I can understand if there are a lot of images then this might be more annoying to code but it would remove the need for a separate display and screen, making it more beginner friendly

i just might be stupid but where did you declare the x and y variables for the list? (those in near the while loop dont work)

sorry for the simple and off topic question but how do you get the pygame readout (and presumably error messages) to display at the bottom of your atom screen? I've been really frustrated because whenever my game crashes I can't read the crash report cuz it disappears when the game screen closes.

I need help. I found a bug in your moving code. Basically when you press and hold the right key then press and hold the up key u jump to the right, but if you let go of the right key while airborne and then hold the left key u just keep going right. I really can't figure out why.

BONK

is made me so happy

ty help alot

i can predict the fture

TYSM! I've been looking for a solution that was simple and easy to understand.

my gawd, using the display variable and adding images around it then scaling up to the WINDOW_SIZE variable, very ingenious concept but a bit too sparse.

what is not air? plz help