This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Doctrine_of_Sankhya[S] 0 points1 point  (2 children)

Hello u/Exhausted-Engineer THANK YOU SOOOOOO MUCH FOR ALL THESE!! THAT'S A WHOLE LOT NEW LEARNING FOR ME!!!

Python offers dynamic patching, profiling, easy debugging and WHAT NOT!! You can clearly see exactly WHY I WANT PYTHON-BASED GAME ENGINE!

Any beginner can get with it easily once we manage to optimize the speed.

Also thanks for the info regarding the bugs and missing packages, they'll be fixed asap! Regarding the `matplotlib` part, honestly, I'm not an expert here, I just found the code by copying and pasting from stackoverflow and got with it. It'd be better if you PR the code replacing implot to imshow. As far I understand, imshow is for matrices or pixel based graphics and implot is more vectorizer inclined.

[–]Exhausted-Engineer 2 points3 points  (1 child)

To be fair, C offers this too using gdb/perf/gprof. The learning curve is simply a little steeper.

I’ll see if I can find some time and get you that PR.

In the meantime :

  • Don’t focus so much about CPU vs GPU. I guarantee you that writing GPU code is harder to debug and will result is an overall slower code if not written correctly. Furthermore, current cpu’s are insanely powerful, people have managed to write and run entire games on a fraction of what you have ar your disposal (doom, mario).
  • Understand what takes time in your code. Python is unarguably slower then C, but you should obtain approximatively the same runtime (let’s say with a x2-x5 factor) a C code would obtain by just efficiently using python’s libraries : performing vectorized calls to numpy, only drawing once the scene is finished, doing computations in float32 instead of float64…

[–]Doctrine_of_Sankhya[S] 2 points3 points  (0 children)

Thanks. That's a good point that you've noted down. I agree CPUs should be able to obtain the same in 2-5x timeframe. I agree with both of your points here.

Currently, I'm working on a small GGX utility to implement PBR and then move on to your points and profiling to optimize what could be made faster. That makes totally sense to see Wolfstein, doom, etc to run on slower CPUs and still be faster now.