Just realised how much easier it is to follow along when the coder is making and correcting mistakes as they go. Coding in this video almost seems god like. However without this level of editing I'd imagine this video can easily be 6 X 1hour vids. I appreciated it though
@@Mr12funkymonkeys I would MUCH prefer this style. It pisses me off to no end when I'm following a tutorial and the creator goes, "OH that whole chunk of code I just wrote actually causes an error, let's delete and retry" because as a beginner I'm following along bit by bit, and if something doesn't go right I spend 20-40 minutes troubleshooting to no avail. It's a pain in the ass.
@@MistereXMachina Its actually good to see when a mistake is made and how someone might go about fixing it because programming is all about squashing bugs.
As a programmer, mainly databases, but programmer non the less, I always wondered how fps games are made. It's a wonderful tutorial and education. Thanks for sharing your hard work with the world! Greetings from Honduras!
This is really like a dream come true tutorial. Keep making these awesome tutorials. You are helping thousands of developers who can now understand how 3d games are coded.
As a beginner, I just copied the code myself, because I understand the math very well, but I can not program. With the very good structure and very good explanations, and because I repeated many parts of the tutorial over and over again, I learned a lot in the process. Thank you for the very much and hard work you put into these tutorials of high quality. For me, they are the first tutorials that I really understood and motivated me to continue.
@@to.sungyongcho Yes, I still don't fully understand the code and some concepts of Python but it doesn't matter. I had fun learning new stuff because for me it was logical and easy to follow. It's the same like learning a new language. It doesn't matter knowing all the rules and translations, it's about the ideas and that you like speaking it.
Thank you very much! I started programming a few months ago, I started in Python. I learned a lot from this video, I spent a whole day on it. I already had the math basics, so I wasn't scared of raycasting, pathfinding algorithms and projection. I even improved the game a little bit: added levels, enemy lifelines, the menu, even a map in the corner that can be switched on and off, with different coloured dots depending on the enemy type. I've also improved my object-oriented approach. I have improved in several areas, so thank you!
This is so freaking cool! The project is incredible for picking up and building something yourself. I am certain it will blow up in recommendations one day.
This is a great demonstration of gradually adding features and testing along the way. I find when scripting, I try to jump ahead to the end state of full functionality sometimes, causing me to encounter errors and get stuck in debugging. This video offers good insights into how to break up a complex set of interacting functions, attacking them individually and gradually integrating things together.
So there are some things I'd improve: 9:13 in so far -Compute player movement without using two (slow) trig functions every frame the player moves (Update: checked the underlying C source code for pygame, it's using a sqrt() function, not any sort of optimized square root approximation, so it's likely the trig is faster.) -Use a clamping method to make the player's whole circle, not just its central point, get stopped by the wall but this is easily the highest-quality pygame tutorial I've seen so far, I'm excited to follow it.
People like you are heaven sent, I can imagine the sleepless nights you spent on this, thank you. Continue creating similar with lenghth 1-2 hours, your content is invaluable
This was awesome, love how the raycasting part is just 15 minutes. Really dissected the that part and now I finally understand every single thing about it!
An hour is about max for my attention span when watching a programming video, and most tutorials end up being too slow for me to follow up on once I start. This one hit the sweet spot. I don't know much about pygame or game development in general, but pretty much all of the questions I had about it were answered-at some surface level at least-during the time it took to watch this. Really well done 👏
Even though this is a scary project to tackle as a beginner like me, by coding along I'm still able to learn a few new things and improve, so thank you for the effort you put into this! Also, I really enjoy how well structured and organized your code is. I'll definitely try to adopt this style on my own projects. I haven't watched the whole video yet, but it would be awesome if you covered the "Doom fire algorithm" in python/pygame, it's really interesting! Cheers!
I found this fascinating! As a competent programmer, but having never written games, this was awesome! Thanks for taking the time to make it and get the presentation super slick! 😁
Thank you so much for this. Your video/project was the base I needed to create my own version of the game. I managed to make multiple levels in which you have to defeat all enemies and advance to the next. I also added more enemies and the more you progress the more enemies will be on the level. Oh and I gave each level its own music
Aww man, this is so cool. First time I see something like that. Ive always wanted to actually see someone program like that. I kinda knew who it theoretically works, but watching it like that, with your explainations, just awesome. Thank you so much. I actually recently played Doom 1 again, so funny.
Brother, this is a piece of art. This entire work... is a piece of art. Thank you for your dedication and hard work in creating it. You really made it count!
Thank you for this! I've so far only been able to accomplish super simple projects. By having everything laid out so explicitly I am going through the motions of a more complex project and learning a lot as I go and building confidence. Thanks so much!
You are continously increasing the quality of your tutorials, this one is in my opinion the best and most interesting one. Congratulations and thank you for your great work!
Great video! I've seen many of these ray-casting treatments, and have done a couple ones myself, this is one of the best and full treatments. That said, basically in almost all of them, one fish-eye lese effect is still left unadressed. There are actually 2 kinds of those in a typical ray-caster, for 2 different reasons - the second one is more slight, and also more subtle to spot where it comes from - which is the choise of using angle deltas to compute ray directions: In a rectilinear projection as the one used here, that choise makes the rays hitting the projection plane distributed along it non-uniformly, where they get more spread-out around the center and more clumped together closer to the right and left edges of the screen (where this second fish-eye lense effect becomes noticeable). The full fix for that is to instead step along the projection plane itself (in this case, a projection-line, as it's 2D ray-casting), at a constant step corresponding to a fixed width of the columns. Then, the ray direction are the vectors from the player's position to those points on the projection-line - but normalized.This ensures the distribution of the rays is uniform across the screen, removing that fish-eye lese effect.
Don't be deceived by the short run time... this project is beefy and it comes at you real fast. Thank you for this... the math makes my head hurt but I feel it's getting clearer the more I look at it and practice.
Me too. I usually only make ascii graphic games. Which good and all but love the opportunities this opens up. Im not good at math tho so the visual was nice help
First of all Thank you so much for all your hard work and dedication !!! Great job mannnn ! When I initially show the game, I thought its going to be highly difficult to understand, but you really made it look nice and worth trying. Path finder part was just awesome intro to the game. A good learner will not only learn coding part but also about managing modules and files properly, what an experience !!! Thank you again.
Damm, this looks impressive. I'm currently watching just for entertainment, but maybe after I finish my current pygame project I'll actually follow this tutorial.
I had texture smudging and ended up having to do a little bug hunting. I accidentally had a: objectToRender = [] Instead of: objectsToRender = [] Always remember to check your variables! I've been doing this tutorial when I'm getting distracted from school work. I've been putting my own spin on things, with plans to make it more modular so it functions more as an engine. Very good tutorial!
Man I found your videos a while ago, and just now watched this. I needed to learn about many topics covered in this video. Your code structure is very clean also and has been an excellent example, thanks!
Damn... clean n swift! after almost 30 years I finally understand the hell that Carmack went trough while creating their masterpiece at id. Thanks bro! very educational!
I spent about two hours to understand and write the code of the first seven minutes of this video. Absolutely incredible work, looking forward to finish this!
Amazing tutorial! I fooled around with pygame a few years back, but I could never quite figure it out. I guess that I would be the one creating the sprites while a real programmer would put together the code such as this one. Loved watching you work!
Just started learning python and thought of creating a simple snake game. This video came in my feed and after watching this i truly understand how much work goes into creating a game. I will save this video to motivate myself time to time to complete the game project i started whenever i face a roadblock
This is a great video! I like how you go in depth on the mathematics and the visual representation with lines and colors really help a lot. Would love to see a tutorial on a Duke Nukem 3D / build engine style game with stairs and vertical movement :)
GREAT JOB! I started teaching my kid how to program in Python. Your code is a great resource and a motivator for him to see what he can achieve with less than 1000 lines of code.
Excellent, I only used pygame for 2D games, so far. This was very educational, and I think the first thing I'll add is the controller support to save my keyboard. 😁
can u make video regarding this game that how can we make .exe of this game and thanks a alot i am ur new subscriber thanks for teaching can u just reply in y or n
OH MY GOD !! Super Awesome !! Love you a lot for sharing your knowledge. You just inspired me to learn to code and study more math even though I don't quite understand the math part but I really enjoyed watching. 😆😆
Very nice Python tutorial for creating a DOOM style game. The only major issue that I can see here is the mixing of the "Engine" code with "GameLogic/Rules" code. With this type of approach it will make it quite difficult to reuse the "Engine" code within future projects. Coming from a C++ background the "Engine" code should be completely agnostic of any Game Logic code. It should only be responsible for knowing how to draw elements, knowing how to process sound and to trigger user events, calculating basic physics - collisions, processing animations, networking, and resource(assets) management. Anything that is game related such as the assets themselves(textures, sprites, audio files, etc...), game logic, rules, personal settings, etc. should be abstracted out of the engine into its own project. The Game project would rely completely on the Engine project where the Engine project should have no dependencies on the game itself. This would allow for more of a modular and generic programming style to give the developer ease of use of reusable code down the road. In simple terms if you wanted to make a second game with this approach all of the "Engine" code or boilerplate code would already exist as a library. You would only then need to include or import it into a new "Game Project" and add the necessary game logic for the next title. Maybe in the next title you want the player movement to be different, maybe you want a different camera style such as 3rd person, maybe you want to add new abilities such as crouching and or jumping mechanics... Having these layers of abstraction early on helps in the long run. Other than this type of programming philosophy, this video is very well done on quickly explaining all of the required steps into making a DOOM style game. Then again one could argue that "Pygame" is that engine... I'm use to writing the actual DirectX, OpenGL, and or Vulkan code to implement the renders and shader modules.
@@CoderSpaceChannel Yeah, your code implementation looks great, your code style is good. In the future if you decide to make another game, you wouldn't have to start all over, you can just import your engine. You may have to make minor changes based on the type of game your making though. A FPS compared to a RTS compared to a RPG type game does use different frameworks, but even these for the most common parts can still be abstracted away. Yeah, keeping the game code seperated from the engine code helps in the long run. You don't have to go back later and try to figure out what is game code vs what is engine code to rip it out with a high chance of breaking the engine code. It can save a lot of future headaches, head scratching, and hair pulling.
Impressive. Python is probably about my 4th language after C#/C++/JS, not done anything large apart from a Django ecommerce project, so a pygame would be interesting, just never had to use anything other than Unity or UE to create a large game. Good stuff and interesting to see python used outside of server side web dev. 👌🏽
This video probably took 500 hours to make. That is; the code; the video; the editing; the script and planning. Like not kidding this wasn't quick and for that you get my thumbs up.
I'm pretty sure figuring all that out and making it work took him a liiiiittle bit longer than one hour. (nevertheless absolutely remarkable performance!!)
That is a great guide! Maybe you also have an advise about how to make a non-static floor? I mean, if I would like to have different textures, like in the case of walls, how would you do that?
I get this error 'line 18, in get_objects_to_render wall_column = self.textures[texture].subsurface( ValueError: subsurface rectangle outside surface area' And I don't know what to do. Tried looking up on the internet, but the explanations are far beyond my comprehension at this time. Did anyone else encounter this problem? How did you solve it?
While this tutorial definitely had some great merits and I really learned a lot, there are some areas that I felt needed improving. The speed of the automatic voice narrator was very fast, along with showing what to do, but at least that was remedied by adjusting the playback settings in TH-cam to a slower speed. And, rewinding a lot. Also, towards the end I noticed that some parts of what was shown in the final result of the game did not match up with the coding you showed along the way. It appears that a lot of information was left out: the extra soldier sprite and Hell Demons, the "Victory" screen, background music, larger map layout, and the additional red torches. I was confused as to why my final result didn't match up to what was shown in this video until I compared the files on your GitHub and noticed some code blocks were never mentioned in the tutorial. While I do understand that a tutorial can help give a basic understanding of some things, I feel that it would be beneficial to also mention that the final result shown on screen will differ to what was presented code-wise, and to use the knowledge given in the video to try and implement the rest on one's own.
Lol this moves a hundred miles a second. To understand some of the math and stuff in detail you need to spend time on small pieces and understand what it does.
Hey there, Wanted to give a big thanks for going through likely days of researching, testing, and editing together this project. Used to be reluctant about following along videos because it seemed too much like copying, but I also learned that’s how we learn. I learned a lot about organization by getting used to how everything was structured, learned how to coordinate my mental reasoning more efficiently, and most of all, learned a lot more about bringing python beyond the shackles of 2D. I have 15 pages of notes. I’d take time to first code along with the video during my homeschool week, then during the weekend, I’d dissect all the mathematics and mechanics on paper. Mind you, my previous game was just two-player atari breakout (and god, how horrified I am about my old code, no words). Previously, I only learned code just for the sake of being able to read it, being able to pass tests on documentation, never intended to make anything. But ever since, I’ve been working towards game development as a side.
I love how at its core, the game is just a bunch of High school math working together. I am a ML Engineer and I find graphics to be fascinating and this is one of those gold examples
This video is one of the best tutorials I have ever seen. Perfect for a beginner who wants to learn the basics of raycasting. The mathematical explanations were really interesting. For my part it was my first experience in Python. Very easy to set up and run things quick with just VSCode. As I have a lot of experience in javascript and C#, the next step for me would be to explore the whole thing in the unity universe :). I also really like the idea to start from this project and build biggest maps (or even a tiny virtual world) with this pseudo-3d retro style.
That's awesome! So glad to see cool games and tutorials coming with pygame library.
9 หลายเดือนก่อน
Amazing video tutorial! Inspired by this, I created a shooter game with multiplayer option. We created our own sounds and played with friends and it was so much fun. 😀
I used to programme when 1 was 16yo with game maker 8 (a very simplified c++ (runtime) and c#(ide) language, where most commands were replaced with icons). This one offered a similar tutorial for almost the same game. My best was when i made and published in their website a super mario game called new super mario revived. It had 55%rating. However programming in a real language like puthon is much more exciting. I wish i manage someday to restart proper game programming (java, c++, c#, python and/or pascal are ok to me). You made my day and earned a sub in no time. The video was awesome from start to end ❤
I corrected the thing about game maker 8. It is based on c++ and c#. This also explains that my games were not laggy (despite very complex and extensive commands) and actually had quite small file size because of memory dump and more efficient code- less code lines, taking into account that the icon styled commands can readily converted into code text as well- all the icon commands in game maker 8 can also be written directly in c++/c# code- (needs less size)
49:22 Quick tip for people not seeing numbers on their screens: I had to add (i + 2) to the first row of the if statement, change the second row to (i + 3), and change the zeros to 100 to scale it to my screen. It’s not the only place where I had to scale things to my resolution because I have a small laptop. So if you have been retyping things and still don’t see numbers, check your scalings.
i am a web devoloper and illl see your video dont know why becouse i am not game devoloper and ill enjoy in this video alot what a great coder you are😍😍😍
I cant imagine the amount of editing that went into this, thanks for making the world a better place brother
Trolling?
Cound't think of a more precise and humane comment, thanks
Just realised how much easier it is to follow along when the coder is making and correcting mistakes as they go. Coding in this video almost seems god like. However without this level of editing I'd imagine this video can easily be 6 X 1hour vids. I appreciated it though
@@Mr12funkymonkeys I would MUCH prefer this style. It pisses me off to no end when I'm following a tutorial and the creator goes, "OH that whole chunk of code I just wrote actually causes an error, let's delete and retry" because as a beginner I'm following along bit by bit, and if something doesn't go right I spend 20-40 minutes troubleshooting to no avail. It's a pain in the ass.
@@MistereXMachina Its actually good to see when a mistake is made and how
someone might go about fixing it because programming is all about squashing bugs.
As a programmer, mainly databases, but programmer non the less, I always wondered how fps games are made. It's a wonderful tutorial and education. Thanks for sharing your hard work with the world! Greetings from Honduras!
Nowadays with open world multiplayer scenario, its a wholeother game. This work with a 2d local setting
Clean and simple-looking implmentation. When you see this type of code, you know the person knows his stuff.
Yep, all by myself forever.
This is really like a dream come true tutorial. Keep making these awesome tutorials. You are helping thousands of developers who can now understand how 3d games are coded.
I'm a python dev also and the level of organisation you displayed was wonderful. I would love to manage planning steps like that.
How long are You a Phy Dev?
@@tomekwenecki4826 About 4 years now.
Shame it's not doing all the talking.
As a beginner, I just copied the code myself, because I understand the math very well, but I can not program. With the very good structure and very good explanations, and because I repeated many parts of the tutorial over and over again, I learned a lot in the process.
Thank you for the very much and hard work you put into these tutorials of high quality. For me, they are the first tutorials that I really understood and motivated me to continue.
lol it means you still don’t understand
@@to.sungyongcho Yes, I still don't fully understand the code and some concepts of Python but it doesn't matter. I had fun learning new stuff because for me it was logical and easy to follow. It's the same like learning a new language. It doesn't matter knowing all the rules and translations, it's about the ideas and that you like speaking it.
Knowing and understanding advaced math helps with any type of programming.
I understand the everything BESIDES the math ;-;
i haven't done whatever class that is yet, the sin and cos stuff
is that geometry or trigonometry?
@@Bl0xxy Sine, Cosine and Tangens is trigonometry.
Someone literally took this game's source and selling it on Steam as Project 0. LOL
I Bet that the person who did literally never played doom before or think its abandonware lmao
Even Project 0 is what the Fatal Frame games are called. That person is just a thief with no regard for anything 😆
Hmmm.. there is a digital publication date for this video could prove ownership and sue the jerk 😎
This is why CURATION should exist.
You are kidding lol ?
Thank you very much! I started programming a few months ago, I started in Python. I learned a lot from this video, I spent a whole day on it. I already had the math basics, so I wasn't scared of raycasting, pathfinding algorithms and projection. I even improved the game a little bit: added levels, enemy lifelines, the menu, even a map in the corner that can be switched on and off, with different coloured dots depending on the enemy type. I've also improved my object-oriented approach. I have improved in several areas, so thank you!
This is so freaking cool! The project is incredible for picking up and building something yourself. I am certain it will blow up in recommendations one day.
it did in mine
I love how you compartmentalize your classes and methods. You’ve inspired me.
Can't believe how organized the code is, you're a beast!
This is a great demonstration of gradually adding features and testing along the way. I find when scripting, I try to jump ahead to the end state of full functionality sometimes, causing me to encounter errors and get stuck in debugging. This video offers good insights into how to break up a complex set of interacting functions, attacking them individually and gradually integrating things together.
So there are some things I'd improve:
9:13 in so far
-Compute player movement without using two (slow) trig functions every frame the player moves
(Update: checked the underlying C source code for pygame, it's using a sqrt() function, not any sort of optimized square root approximation, so it's likely the trig is faster.)
-Use a clamping method to make the player's whole circle, not just its central point, get stopped by the wall
but this is easily the highest-quality pygame tutorial I've seen so far, I'm excited to follow it.
is it the same legendary fast inverse square root algorithm of Quake?
@@MrNeelthehulk The very same, yes.
People like you are heaven sent, I can imagine the sleepless nights you spent on this, thank you. Continue creating similar with lenghth 1-2 hours, your content is invaluable
This was awesome, love how the raycasting part is just 15 minutes. Really dissected the that part and now I finally understand every single thing about it!
An hour is about max for my attention span when watching a programming video, and most tutorials end up being too slow for me to follow up on once I start. This one hit the sweet spot. I don't know much about pygame or game development in general, but pretty much all of the questions I had about it were answered-at some surface level at least-during the time it took to watch this. Really well done 👏
A whole engine in the first 15 minutes, great job man and amazing code structure!
Even though this is a scary project to tackle as a beginner like me, by coding along I'm still able to learn a few new things and improve, so thank you for the effort you put into this! Also, I really enjoy how well structured and organized your code is. I'll definitely try to adopt this style on my own projects.
I haven't watched the whole video yet, but it would be awesome if you covered the "Doom fire algorithm" in python/pygame, it's really interesting!
Cheers!
If you want i have on JS, got from Felipe Deschamp (brazilian youtuber)...
learing python now
@@sophiacristina i want! i think i can translate to python
@@snaiktavares5356 TH-cam blocks link now, let me try to find a way.
The video code:
fxm8cadCqbs
Check the description. :)
I found this fascinating! As a competent programmer, but having never written games, this was awesome! Thanks for taking the time to make it and get the presentation super slick! 😁
Thank you so much for this. Your video/project was the base I needed to create my own version of the game.
I managed to make multiple levels in which you have to defeat all enemies and advance to the next. I also added more enemies and the more you progress the more enemies will be on the level. Oh and I gave each level its own music
Aww man, this is so cool. First time I see something like that. Ive always wanted to actually see someone program like that. I kinda knew who it theoretically works, but watching it like that, with your explainations, just awesome. Thank you so much. I actually recently played Doom 1 again, so funny.
Brother, this is a piece of art. This entire work... is a piece of art. Thank you for your dedication and hard work in creating it. You really made it count!
Thank you for this! I've so far only been able to accomplish super simple projects. By having everything laid out so explicitly I am going through the motions of a more complex project and learning a lot as I go and building confidence. Thanks so much!
You are continously increasing the quality of your tutorials, this one is in my opinion the best and most interesting one. Congratulations and thank you for your great work!
Great video! I've seen many of these ray-casting treatments, and have done a couple ones myself, this is one of the best and full treatments. That said, basically in almost all of them, one fish-eye lese effect is still left unadressed. There are actually 2 kinds of those in a typical ray-caster, for 2 different reasons - the second one is more slight, and also more subtle to spot where it comes from - which is the choise of using angle deltas to compute ray directions: In a rectilinear projection as the one used here, that choise makes the rays hitting the projection plane distributed along it non-uniformly, where they get more spread-out around the center and more clumped together closer to the right and left edges of the screen (where this second fish-eye lense effect becomes noticeable). The full fix for that is to instead step along the projection plane itself (in this case, a projection-line, as it's 2D ray-casting), at a constant step corresponding to a fixed width of the columns. Then, the ray direction are the vectors from the player's position to those points on the projection-line - but normalized.This ensures the distribution of the rays is uniform across the screen, removing that fish-eye lese effect.
Thank you, I had a really hard time following what was going on in the video but you explained it perfectly.
BRILLIANT, now I just got the perfect tutorial to start the games dev and understand deeply how engines work. GOOD JOB BRO
Never seen anything like this before. Everything from the explanation of maths to the coding is spot on 😯😊
Don't be deceived by the short run time... this project is beefy and it comes at you real fast. Thank you for this... the math makes my head hurt but I feel it's getting clearer the more I look at it and practice.
Amazing tutorial, I always look forward to your videos
Es lo mejor que he visto, lo intente y voy en SPRITES....es increible y genial GRACIAS HERMANO POR ESTO !!!!
So detailed yet brief, excellent work
Finally I found someone who help me udnerstanding Ray Casting from scratch, Thanks man.
And thank you too!
Me too. I usually only make ascii graphic games. Which good and all but love the opportunities this opens up. Im not good at math tho so the visual was nice help
First of all Thank you so much for all your hard work and dedication !!! Great job mannnn ! When I initially show the game, I thought its going to be highly difficult to understand, but you really made it look nice and worth trying. Path finder part was just awesome intro to the game. A good learner will not only learn coding part but also about managing modules and files properly, what an experience !!! Thank you again.
i'm amazed how much algebra and geometry is involved for a simple game.
Wow, this is an impressive tutorial, nice stuff
just one of the best tutorials i've ever seen ! Excellent works thank you so much !
Damm, this looks impressive. I'm currently watching just for entertainment, but maybe after I finish my current pygame project I'll actually follow this tutorial.
The organization in this code is absolutely beautiful, makes me fucking smile
I had texture smudging and ended up having to do a little bug hunting. I accidentally had a:
objectToRender = []
Instead of:
objectsToRender = []
Always remember to check your variables! I've been doing this tutorial when I'm getting distracted from school work. I've been putting my own spin on things, with plans to make it more modular so it functions more as an engine. Very good tutorial!
10 minutes of this video has given me 2 days of study. you've done a great service, thank you.
Man I found your videos a while ago, and just now watched this. I needed to learn about many topics covered in this video. Your code structure is very clean also and has been an excellent example, thanks!
thank you! I wanted to combine my python learning with a new game design and this gives some great insight on what you can do with python
ngl i never watched long videos but this one made be watch it through the end without even realizing the time, such a slick video, Great work
your videos are incredibly high quality, not sure how you don't have more subscribers yet but if you keep this up you're guaranteed to get them
Damn... clean n swift! after almost 30 years I finally understand the hell that Carmack went trough while creating their masterpiece at id. Thanks bro! very educational!
as someone who recently started learning python, this is absolutely mind blowing
Is it possible tho? Cz im a beginner too lol
Holy shit i just skipped to the raycasting
I spent about two hours to understand and write the code of the first seven minutes of this video.
Absolutely incredible work, looking forward to finish this!
Amazing tutorial! I fooled around with pygame a few years back, but I could never quite figure it out. I guess that I would be the one creating the sprites while a real programmer would put together the code such as this one. Loved watching you work!
Just started learning python and thought of creating a simple snake game. This video came in my feed and after watching this i truly understand how much work goes into creating a game. I will save this video to motivate myself time to time to complete the game project i started whenever i face a roadblock
Nice, I would love to learn from it!
This is great, a sort of crash-course in pygame as well as brilliant simplicity of Wolfenstein / Doom. Thank you!
This is a great video! I like how you go in depth on the mathematics and the visual representation with lines and colors really help a lot. Would love to see a tutorial on a Duke Nukem 3D / build engine style game with stairs and vertical movement :)
yeah but with this video and maybe others you can make it yourself
GREAT JOB! I started teaching my kid how to program in Python. Your code is a great resource and a motivator for him to see what he can achieve with less than 1000 lines of code.
Excellent, I only used pygame for 2D games, so far. This was very educational, and I think the first thing I'll add is the controller support to save my keyboard. 😁
holy code! That's fast pace, but it's incredibly smooth and clean. Awesome tutorial!
And if you get errors when running the source code, first make sure you have Pygame version 2.x.x
I get error and my pygame version 2.1.2.why I get error? please reply me?
@@gamingyuvi9512 what kind of errors do you get ?
Traceback (most recent call last) error
can u make video regarding this game that how can we make .exe of this game
and thanks a alot i am ur new subscriber thanks for teaching
can u just reply in y or n
my game doesnt draw the background or map and i copied everything correctly and im only at 3:42 can you help please?
OH MY GOD !! Super Awesome !! Love you a lot for sharing your knowledge. You just inspired me to learn to code and study more math even though I don't quite understand the math part but I really enjoyed watching. 😆😆
Very nice Python tutorial for creating a DOOM style game. The only major issue that I can see here is the mixing of the "Engine" code with "GameLogic/Rules" code. With this type of approach it will make it quite difficult to reuse the "Engine" code within future projects. Coming from a C++ background the "Engine" code should be completely agnostic of any Game Logic code. It should only be responsible for knowing how to draw elements, knowing how to process sound and to trigger user events, calculating basic physics - collisions, processing animations, networking, and resource(assets) management. Anything that is game related such as the assets themselves(textures, sprites, audio files, etc...), game logic, rules, personal settings, etc. should be abstracted out of the engine into its own project. The Game project would rely completely on the Engine project where the Engine project should have no dependencies on the game itself. This would allow for more of a modular and generic programming style to give the developer ease of use of reusable code down the road. In simple terms if you wanted to make a second game with this approach all of the "Engine" code or boilerplate code would already exist as a library. You would only then need to include or import it into a new "Game Project" and add the necessary game logic for the next title. Maybe in the next title you want the player movement to be different, maybe you want a different camera style such as 3rd person, maybe you want to add new abilities such as crouching and or jumping mechanics... Having these layers of abstraction early on helps in the long run. Other than this type of programming philosophy, this video is very well done on quickly explaining all of the required steps into making a DOOM style game. Then again one could argue that "Pygame" is that engine... I'm use to writing the actual DirectX, OpenGL, and or Vulkan code to implement the renders and shader modules.
thanks, I'll take note 👍
@@CoderSpaceChannel Yeah, your code implementation looks great, your code style is good.
In the future if you decide to make another game, you wouldn't have to start all over, you can just import your engine. You may have to make minor changes based on the type of game your making though. A FPS compared to a RTS compared to a RPG type game does use different frameworks, but even these for the most common parts can still be abstracted away.
Yeah, keeping the game code seperated from the engine code helps in the long run. You don't have to go back later and try to figure out what is game code vs what is engine code to rip it out with a high chance of breaking the engine code. It can save a lot of future headaches, head scratching, and hair pulling.
please keep doing long video formats like this! this is awesome
Impressive. Python is probably about my 4th language after C#/C++/JS, not done anything large apart from a Django ecommerce project, so a pygame would be interesting, just never had to use anything other than Unity or UE to create a large game. Good stuff and interesting to see python used outside of server side web dev. 👌🏽
This video probably took 500 hours to make. That is; the code; the video; the editing; the script and planning. Like not kidding this wasn't quick and for that you get my thumbs up.
What has the world come to, we can now write DooM in one hour.
He can*
I'm pretty sure figuring all that out and making it work took him a liiiiittle bit longer than one hour. (nevertheless absolutely remarkable performance!!)
Great work, thank you so much for this content. I have a new appreciation for what it took to create this genre of games. Incredible job!!
That is a great guide! Maybe you also have an advise about how to make a non-static floor? I mean, if I would like to have different textures, like in the case of walls, how would you do that?
I am more than impressed with the quality of your tutorial and your explanations, congratulations! I subscribe directly :)
I get this error 'line 18, in get_objects_to_render
wall_column = self.textures[texture].subsurface(
ValueError: subsurface rectangle outside surface area'
And I don't know what to do. Tried looking up on the internet, but the explanations are far beyond my comprehension at this time. Did anyone else encounter this problem? How did you solve it?
i got recommended this. your format is fantastic. i can tell that a lot of effort goes into these videos. kudos.
While this tutorial definitely had some great merits and I really learned a lot, there are some areas that I felt needed improving. The speed of the automatic voice narrator was very fast, along with showing what to do, but at least that was remedied by adjusting the playback settings in TH-cam to a slower speed. And, rewinding a lot. Also, towards the end I noticed that some parts of what was shown in the final result of the game did not match up with the coding you showed along the way. It appears that a lot of information was left out: the extra soldier sprite and Hell Demons, the "Victory" screen, background music, larger map layout, and the additional red torches.
I was confused as to why my final result didn't match up to what was shown in this video until I compared the files on your GitHub and noticed some code blocks were never mentioned in the tutorial. While I do understand that a tutorial can help give a basic understanding of some things, I feel that it would be beneficial to also mention that the final result shown on screen will differ to what was presented code-wise, and to use the knowledge given in the video to try and implement the rest on one's own.
Lol this moves a hundred miles a second. To understand some of the math and stuff in detail you need to spend time on small pieces and understand what it does.
Thank you! Fantastic tutorial and so well explained. I was never good at trig, but you've explained it well.
Someone's seriously trying to sell this on Steam.
Thanks I just saw this...
Wow, real shit head behavior
Hey there,
Wanted to give a big thanks for going through likely days of researching, testing, and editing together this project. Used to be reluctant about following along videos because it seemed too much like copying, but I also learned that’s how we learn. I learned a lot about organization by getting used to how everything was structured, learned how to coordinate my mental reasoning more efficiently, and most of all, learned a lot more about bringing python beyond the shackles of 2D. I have 15 pages of notes. I’d take time to first code along with the video during my homeschool week, then during the weekend, I’d dissect all the mathematics and mechanics on paper. Mind you, my previous game was just two-player atari breakout (and god, how horrified I am about my old code, no words). Previously, I only learned code just for the sake of being able to read it, being able to pass tests on documentation, never intended to make anything. But ever since, I’ve been working towards game development as a side.
we've got problems, somebody published your doom tutorial on Steam without changing any of the assets, and called it "Project 0".
thanks for the info, that's sad...
@@CoderSpaceChannel Can't you report it to Steam so they can take it down?
This is an amazing walk through, thank you for sinking so much time into this video.
4 lines into the main script, got 7 errors and gave up.
Thats the avg experience of coding
NEVER BACK DOWN NEVER GIVE UP!
@@Cr1tic9lI want it louder
Thank you so much for this! Also love the How It's Made Vibes
I love how at its core, the game is just a bunch of High school math working together. I am a ML Engineer and I find graphics to be fascinating and this is one of those gold examples
I always wondered how raycasting worked being a huge doom fan, and python makes it so simple and easy to do vs something like C
This is an amazingly detailed tutorial and explanation. Thank you so much for sharing your knowledge
This is insane material. Thank you for sharing.
TH-cam is a great place for such a great piece of explained knowledge! Thanks!
This video is one of the best tutorials I have ever seen. Perfect for a beginner who wants to learn the basics of raycasting. The mathematical explanations were really interesting. For my part it was my first experience in Python. Very easy to set up and run things quick with just VSCode. As I have a lot of experience in javascript and C#, the next step for me would be to explore the whole thing in the unity universe :). I also really like the idea to start from this project and build biggest maps (or even a tiny virtual world) with this pseudo-3d retro style.
That's awesome! So glad to see cool games and tutorials coming with pygame library.
Amazing video tutorial! Inspired by this, I created a shooter game with multiplayer option. We created our own sounds and played with friends and it was so much fun. 😀
Amazing work. Learnt a lot from this. Thank you!!
the whole raycasting portion just flew over my head
Amazing work :-) I appreciate the way your work is so well organized.
Excelent tutorial. Hard work is celebrated!
what an awesome tutorial. everything was explained perfectly and the it worked quite well. thanks
51:25 looks like the player traspasses the candle XD. nice vid!
I was so happy when I found this game. I really enjoyed it and it made me say things out loud in Optimus Prime’s voice when I played him.
I used to programme when 1 was 16yo with game maker 8 (a very simplified c++ (runtime) and c#(ide) language, where most commands were replaced with icons). This one offered a similar tutorial for almost the same game. My best was when i made and published in their website a super mario game called new super mario revived. It had 55%rating.
However programming in a real language like puthon is much more exciting. I wish i manage someday to restart proper game programming (java, c++, c#, python and/or pascal are ok to me).
You made my day and earned a sub in no time. The video was awesome from start to end ❤
I corrected the thing about game maker 8. It is based on c++ and c#. This also explains that my games were not laggy (despite very complex and extensive commands) and actually had quite small file size because of memory dump and more efficient code- less code lines, taking into account that the icon styled commands can readily converted into code text as well- all the icon commands in game maker 8 can also be written directly in c++/c# code- (needs less size)
It's fast-paced, but a really, really great tutorial!
Wow! It's amazing the power and simplicity of python. Thanks for the tutorial.
One of the best video I'll ever see, great work.
This gonna be a wild journey taking this on and learning and it’s a type of game I grew up on and favor compared to the others 🔥🔥🔥😂 thanks
49:22 Quick tip for people not seeing numbers on their screens: I had to add (i + 2) to the first row of the if statement, change the second row to (i + 3), and change the zeros to 100 to scale it to my screen. It’s not the only place where I had to scale things to my resolution because I have a small laptop. So if you have been retyping things and still don’t see numbers, check your scalings.
Thank you for making this. This is a good capstone idea.
You deserve million subs for sure! Thank you for sharing this with us for free!
Sick video man, I always look forward to your next video
i am a web devoloper and illl see your video dont know why becouse i am not game devoloper and ill enjoy in this video alot what a great coder you are😍😍😍