So I Made My Own Game Engine...

the speed myth is still a myth. opengl is not slower than the other two. and it saddens me that all sorts of people who started making engines believe that : (

The reason why I write game engines is because that's were most of the hard challenges are....compared to the game engine, games are dead simple

javascript would be nice :)

Great info. I just want to know how to create a Lumen system like UE5. The day when someone discovers it will be revolution, because is needed for the open source world.

You should take a hourly payment for using your game engine, where the cheapest option is 50$

I can think of a couple of reasons to make a game engine now.

I feel like there is another good reason now to make a game engine...

This is great, explained what the engine does without fancy frills.

Dude really said programming using pointers in cpp makes life easier. I use pointers on daily basis I still don't understand them fully. What a Chad.

OpenGL definitely doesn't perform worse than DirectX, in fact you could even get VK or DX12 like performance out of it if you know what you're doing. These "frameworks" are actually graphics APIs that send commands to the GPU, period. The performance you get is almost entirely dependent on your engine design/subsystems, draw call optimizations, etc.

I'm also not very bright, but lots of people much smarter than me have all said Vulkan is basically horrible. And who am I to disagree with them. However, OpenGL is really just a graphics library whereas DirectX does a bit of everything.

Oh and I think this engine needs ported to Brainfuck and also F#. As a stretch goal... VBA. Chop chop.

Assembly lol just cause (I am curious if it can do much)

Well, your video is already quite old, so maybe you already figured these things out by yourself, but it looks like you don't quite understand the purpose of OpenGL.
You're not supposed to send an array of pixels as a texture and have it render there. The whole point of OpenGL is that you send to it primitive shapes and then it figures out by itself how the pixels should be. It can do this much faster than CPU code, because it runs on the graphics card.
If you already know how the pixels should be, then you did all the rendering in the CPU, and you don't need OpenGL.
What you're doing is rendering everything in the CPU, sending all the stuff to the graphics card, which puts them on the screen without doing anything.
It would be more straightforward, faster, and give you code with less dependencies if you just opened a pixmap to your OS display server and transfered the pixels there. In Linux Xlib does this, I don't know about Windows, but pretty much any GUI toolkit should have a way to open a pixmap.

are there any good tutorial for making a Game Engine?

Cool to see you take on your own framework! Great video

i definitely had to use learn opengl to make my game engine

Good, now write it in Nim.

This is a fantastic video, nice work! I made a game engine using the opengl wrapper opentk so I could use c#. Trying to create a game engine gives you so much insight into how most game engines work and is great for learning new programming concepts.

This is pretty awesome! I feel like that this could be made pretty well with SDL2 instead of OpenGL, it’s really lightweight and handles everything, like windows, rendering, input, sound, you name it!