🔥 How the Doom Fire Algorithm Works

Показать описание

Pygame Tutorial on Implementing the Doom Fire 🔥 Algorithm in Python

Github:

#doomfire #python #coderspace #pygame

Рекомендации по теме

Комментарии

I'm sure one day you'll get the recognition you need bro, reall good stuff

metehansert

I've been doing fire/water since 1990. Things never change. :)

nacnud_

Freaking subscribed. Again. Awesome content, mate!

DrIngo

This made my day! hahaha You are the best!!

jvsvogler

Interesting algorithm to produce some really cool fire effects, thanks for sharing!

harleyfillus

i remember the first time when i created a fire effect i used as a pallete a value between 0 and 256*3-1 and it started with increasing the red value from 0 to 255, when it capped it increased green (ultimately reaching yellow) and when green capped it increased blue (ultimately reaching white). somehow that worked fine

danb

wow cool I always wondered how the heck they did that. That was always my favorite part of doom on PSX it looks so cool even today.

wildwest

Amazing tricks, thanks for the tutorial

jkazulyblanco

You never fail to impress, keep it up w the amazing vids! :)

joelmontgomery

I have always wanted to learn Python because it is so widely used (in addition to R and C++), but these tutorials, as professional and informative as they are, expose the aspects of Python that are deterring me from learning it. Is it the things like ‘we use 3.10 because it is the last version supported by Numba for compilation’ or the horrendous drop in the frame rates every time something simple is added that are putting me off. Maybe there is a way to speed it up via some sort of vectorisation? E.g. in R, replacing loops with vectorised ‘apply’-like operations (i.e. map) sometimes yields a 10x speed-up just owing to not invoking the high-level type stuff at every point of the double loop. Yes, writing in Python is quick, but the amount of time necessary to optimise every inefficient operation and make things run smoothly requires a lot of time and Carmack-level knowledge that... kind of ruins Python (intended, among other things, for fast and user-friendly prototyping), and could have been done in C++ with SDL straight away. How can I convince myself otherwise?

ffs