No you dont. But you should because good fucking luck

Bruh is going up to that point when he realises he doesn't need an OS as well

bro is ded

Now use vulkan, or no opengl

I have a question. Why are we including glcorearb / glext / khrplatform ourselves? Doesn't windows ship with gl/gl.h? Do those headers not cover everything?

Could you touch on creating a modern opengl context + creating bindings for it (including 4.x extensions)? That's the only thing stopping me from dropping sdl since sdl doesn't do everything I need and I'd much rather just do platform stuff myself. I had a platform from earlier games for linux and win32, but I used vulkan then and I didn't have to do all that opengl context crap and its been so painful to do those, that I just used sdl. some nice resource / starting point would be nice.

well sure you could be a carpenter starting with no tools but you gotta be sure you want to

Rendering a cube with a pure black shadow isn't even remotely close to a game engine, at all. Also, how is Open Graphics LIBRARY not a library? Just code in assembly

are you using opengl 4.5 or 3.3?

Awesome video! Like the idea of your game. Also kudos for making your own game engine. That takes some serious dedication and time to do. It is always interesting to see how others implement certain features to a game engine. Looking forward to your next devlog. Keep it up! :)

well done, very impressive that you created your own custom engine :) I really like the minimal style of the game. I would add a simple art-style (such as only flat colors, no details, simple shapes) and a lot of "juice" (game-feel) to make it pop-out! I also like the idea of having a map, instead of a huge open area! continue the good work :)

add coop multiplayer

This Looks really cool maybe after your done with all important stuff you could add Like a turret Shooting at enemies that lasts for Like 30 Seconds and then its on cooldown

ich sehe einen deutschen akzent, wenn ich ihn sehe!😂

Excuse me, may I ask why you chose to stick with OpenGL instead of opting for Vulkan? Are there any particular reasons or special considerations?

I'm crying right now

When did writing your own game engine become a bad thing? It used to be the norm in early days of game development. Most games I come across could easily be remade with a framework. In the drag and drop approach, you are always limited by what the popular game engine allows you to make, and not what you really wanted. I feel DD encourages a "you don't have to think about what's happening under the hood", and makes it so you never really what understand you are doing.

You are not transparent either. Skip

"you don't need libraries" my brother in christ, windows.h all jokes aside though this is very impressive

You use some keywords that I totally agree with: transparency, educational. I think you have a strong point there. I teach computer graphics, and although I do provide my students with some utility code on top of OpenGL, but it is all *transparent*. No black boxes if I can avoid them, no libraries stashed away where you aren't supposed to read or change them and they are so bit that you can't do that anyway. And this is all about transparency. My students are encouraged to dig into my code, and I try to keep things compact and simple. No GLM, instead a single code file with the essentials, no GLUT or GLFW, instead another single code file (one each for Mac, Linux and Windows). No assimp, instead the smallest reasonably capable OBJ loader I know (smaller than TinyOBJLoader!). Most of these are single header code. I obviously can't have my students digging into the code of OpenGL (although Mesa is open source) but all the other parts. But I am asking myself one thing: Should I skip most of this code and ask the students to write their own? Writing a model loader is a project of its own, but writing your own math library is not very hard at all. So, I totally agree on your approach. I think it is how you learn the best.

Let's be real. You do if you want to actually make something good.

Why you say you don't need libraries then use OpenGL?

Hast du das mit OpenGl erstellt?

Looks great :D can't wait to download!

Nice work so far :) Would it be possible to smooth the camera repositioning when your controllable character moves? It's currently quite jarring. Else, it looks extremely fun!

Writing your own tool is educational, leveraging existing tool is productive.

great now add support for Vulkan, Linux and Wayland 👀

Sure, to make a game with moving cubes we dont need any library. Actually you dont need coding also, you can make same game with something like scratch lol

You have a nice voice!

Open Graphic Lib...

Man can you share the source code for the project?

you are using a graphics lib. Your title does not really make sense

wow, this cpp app couldn’t be further than what I’ve been taught project setup wise. Is there a reason you don’t just use Visual studio to compile your project? As a single platform cpp developer myself, I’m very interested in following the development of this project to see how smoothly it goes. I’m all for making the process streamlined and simple for development, you’ve made some interesting choices here. If it works it works, I always say. Good luck on the project and thanks for sharing.

am i the only one or does he talk like sebastian league?

owww why not sdl ;( opengl is pain

Looks great! Personally, when not using VS Solutions etc., I prefer VS Code - it's a lot more lightweight!

My game design teacher said to never use unity builds but to only include header files. Odd, i guess its just coders choice

0:50 why not just use VS Code then?

you can use the DirectWrite windows api to render text if you want to get rid of freetype

header files exist for two reasons: forward declarations and encapsulation. both c and c++ compilers require things to exist before you can use them in a top to bottom manner; you can get around this by doing what's called a forward declaration, where you define the signature of a variable, function, or class (this is not an exhaustive list of literally everything, but it should give you an idea of what i mean). this signifies to the compiler that this thing doesn't exist yet but it is going to later on in your code, which is a problem that gets passed onto the linker after the compilation step is finished. when you have multiple source files that all share the same code, you will soon find out that things will get very annoying to forward declare which is where header files come into play. now to explain encapsulation, sometimes you don't want a function in one source file to be exposed to another source file because it just doesn't make sense for it to be there. for example, it wouldn't really make sense for a mesh rendering function to be in the same place as enemy ai. with header files, you can describe what's supposed to be accessed from that file instead of leaving people guessing if anybody else was working with your code. this is the same reason public and private exist in classes, you're describing to people who are going to use your class what is and is not okay to directly access.

imagine this, but in 3D, thats my final proyect for oop, i had a 2D version but using assembly, good job

Btw, you don't need to release/free the allocated memory when you are already going to exit. The OS will handle this, and this will just make it slower to close/exit the game.

diing the same in rust

Nice video! If I may comment something, actually mesuring the 60fps with getTickCount is not quite accurate, and it depends on the system precision (10-16ms says the microsoft doc in general). You better want to use QueryPerformanceFrequency instead, and set the OS scheduler frequency of the system yourself (and don't forget to make it back to its default value when exiting the program ^^). One more thing, sleep is not accurate too haha. When sleeping(1), you expect that the system will sleep for exactly one millisecond, but unfortunately it's not really the case and it is usually bigger). If you want better accuracy, you can combine spin lock with sleep to not burn the cpu down, and get a pretty nice accuracy (better than just sleeping ^^)

You really shouldn't include .cpp files ever. You want to split your code across different source files and only include header files across them. Including all your source files into one means your compiler needs to recompile all your code every time you change anything, instead of only having to recompile the files you edited since the last compilation. It can also make for more readable and structured code if you create clean headers.

Amazing video😮.

Cool :D nice to have readable code

Yes, you should be able to directly access the video memory and write to it. But if your goal is to create a game, better to use existing libraries, helps in quick prototyping.

Hello, I want to create MMO RPG. Will your engine be sufficient for this?

hear me out, what if you added a ability to turn a few random enemies around you into explosive enemies, so you can potentially create a huge explosion if you play your cards right