@@somename5632opengl despite its name is in fact something called graphics api. Set of functions that are running on the gpu. We can use opengl drivers on our graphic cards to render things onto a window for example
@@somename5632OpenGL is and API standard, which graphics card vendors implement. This is, so your graphics code can work on graphics cards manufactured from a wide range of vendors, rather than having to write different code for every different kind of card. The OS usually helps you by providing some kind of standard OpenGL header with function pointers to the functions implementation of the graphics card in the PC, so in that sense it is a little bit like a library, but in essence it is not.
Here's my current take on this subject: If you're building an engine specifically to build actual projects or to learn about a specific feature, then just use existing open source implementations for rest of the features you're not interested in or focused on and write a thin API around them for your application to use. These libraries can be replaced with your own implementation if required in the future, I've seen many companies do this like valve and roblox. As an example: I'm interested in learning about entity component systems and I want to write a simple C based engine that utilizes such a system. In this case, I would simply use SDL to handle sound, input and windowing to quickly get started and possibly even a rendering library for visualization. I would then build the ECS system myself since that's what my engine is focused on. Later I can swap out the rendering library with my own renderer, but only if required. The point of saying all this, not as a response to your video necessarily, is people shouldn't worry too much about using existing libraries. They can be swapped out whenever required, focus on what you want to focus on for now. Chances are existing libraries will fulfil your requirements.
I live all of these "you dont need xxx to create game" videos. Like literally, every single video tries to proof that you can roll your own engine and as proof they show empty scene with one colored cube at the end. No it is not "game engine". You don't have input system, multiple rendering pipelines, multiple platforms, audio mixer, netplay, entity managment, shaders, particle systems, physics, component systems, pbr materials, terrain system, level editing tools, animations, ui, scripting systems, lighting systems, ai, navigation, scene graph, (....) I can do it all the day. Of course, I encourage everyone to try making simple 3d stuff by themeselves, its great fun and you can learn a lot with that in terms of low level programming. But please stop with those "you dont need game engine" videos already..
Fun fact, author of video didn't actually mention any argument of "why you should not use any libraries for game engine". If you are making a clickbait title for video, you should at least try to argue why it is good/bad.
I understand why it seems appealing, but now you depend on the Windows API which is even worse in the long run. It makes your game much less portable to other OS-es. Even if you don't want to depend on an existing game engine, you could use a cross-platform library like SDL which is low-level enough to give you great control, but still portable.
You abstract the game logic from the Windows API so it's portable. This is the main problem I had using Unity and Unreal is that it entangles you unless you think very carefully about your code being abstract.
@@rytif I was thinking about Linux specifically, but there are also a great number of Mac fans out there. @victorthevictor1976 Banking on "Unix-like users will just use Wine" is not the right way of thinking. Wine should be considered as a last resort when there are no alternatives available. Games always have alternatives: other games. Though I think you can still go cross-platform later, if needed, just make sure to separate your system calls to distinct modules.
@@rytif IOS Android MACOS WEB Steam Deck(Linux, still better to have native support than using Proton), and Windows is slowly losing popularity. It's also potentially future proof for new platforms, but it's a maybe.
Agreed. I feel like it was hidden from me for a long time that Windows already gives you everything you need to make a game. They have image loaders, they have 3d apis, they even have 3d audio.
@@vesk4000You do anyway if you want to have a toolset that can port to consoles, but better thing to do is abstract the game logic from the renderer, so that you can just change the code in your functions according to the renderer. You can just start with using GDI if you wanted to, then later implement OpenGL, Vulkan or Direct3D.
i made my own 2D game framework using OpenTK and i learned a lot about modern graphics rendering (textures, vertex specification, GLSL, matrices, etc). i have never learned so much from a single project, but it was also the most painful 6 months of my life. also wrote a 3D model loader for AutoDesk but i gave up on learning more about 3D after that (lighting, collision, camera). what did you use for audio when you made your engine using OpenTK?
@@TU7OV I mean yeah it’s *technically* not a library but it is a header file you include that provides functions, typedefs and structs (exactly what libraries do except it’s for interfacing with the OS). I think that’s close enough for you to not be *that guy* on a comment with 10 likes.
The title is imprecise as what he meant is "libraries outside of OS functionality" which as you said is still awesomely impressive as the OS doesn't give you much at all in the way of writing a game. I wouldn't know how to do this myself without at least SDL2 and GLFW
OpenGL is not a library, is an API, it just have "graphics library" in the name because is an open version of IRIS GL, and they did keep the GL in the name, when IRIS GL became open source they named it OpenGL.
OpenGL is a crossplatform standard for graphics. Thats all it is. There is no "OpenGL library code" that is written by the OpenGL creators. They jus say "hey, this is how things should be", and then each vendor implements their part so that everyone can write graphics programs with a common interface. Thats why its an API. If you want, you could manually find a way to interface in different platforms with different graphics cards and use their specific machine languages for their architecture specific instructions. We could also make computers out of sand and stop buying them. The purpose of OpenGL is to prevent having to program a different program for both the main application and for the runtime compiled shaders for each and every single different GPU that exists in the world. If we lived in the simpler times when your OS did not take control over its resources like it does nowadays, and when graphics cards were not a thing, then we could all write our own software renderer and we would actually be doing all the legwork ourselves. But... since we have an operating system that takes control of our resources and doesnt allow us to directly write to memory wherever we want, we cant make our own software renderer that runs on the CPU, we'd have to rely on OS specific drawing commands at some point... and nowadays with all the graphics cards that exist, yeah, im sorry but we're FORCED to used APIs because we live in a world of standards where you cant even do things by hand anymore. Thats why all the people who write software renderers these days always make them export to image files rather than displaying them on the screen. But hey, if you want to write machine code for every single GPU out there, you're free to do it.
@@heliusuniverse7460 he is not choosing the implementation, that's why he needs to use wglgetprocaddress, because he is just using the API and Windows is getting the implementation from the gpu drivers, if you want to blame someone, blame the OS or the Gpu manufacturer for using the OpenGL implementation as a library and not as executing the opengl functions directly. If he was in mac he would be calling OS internal functions instead (using the same API)
I don't know if it is my eyes or my monitor but when you move object in your game I believe I can see interlacing between frames. Was it intentional or a side effect of something ? This looks great btw.
@@The_Simplest_Game Not sure which video editor you're using but usually there's a list of output resolutions when exporting and 1080i for instance is 1080 interlaced as opposed to 1080p which is not.
Are you going to make a tutorial series on doing that? I'm currently kinda stuck moving on from the basic tutorial (console program and stuff) to the more advanced stuff like making GUI and using libraries. I don't even know how to make an installer for my finished programs...
I’m probably not going to make a full on tutorial series about this, but I’m considering going into more detail in some of these aspects. I have written a small immediate mode gui system and want to show that in the future, but that still requires some more work.
I recommend watching the Cherno, victor gordon, or ogldev while waiting. They have good c++ and OpenGL videos. It might be slow at first but there’s a lot to understand before making more complicated graphics things from scratch if that’s what you want to learn.
@@The_Simplest_Gamedefinitely interested in a tutorial series. I have been learning C++ Win32 API graphics programming only utilizing WinGDI so far, so I understood alotta the code, despite never having used openGL. what resources did you use to learn how to do all of this btw?
done the same, just finished rigging my puppet, entirely in c/c++ win32, no blender, took 12 weeks to design it myself. but faster next time. and all my rotations are euler angles. :) and my entire game app is like 700kb haha.
Just wondering if you were going to release it as open source? I'd love to have a look at what you've done as I'm trying to do the exact same thing right now.
@@The_Simplest_Game If you are not gonna sell it, you should make it open source. Free software and open source developer mindset is a good thing not just for other but especially for you to grow and learn more.
I made a 2D Game Engine in DirectX 11/OpenGL and W32. When porting it to MacOS, I couldn't be bothered to learn objective c or metal so I just used SDL 😂😂😂
OpenGL is not a library, it's a specification. If you're using only OpenGL you need to write all the code that implements OpenGL yourself. The actual libraries that do that for you are stuff like glut or glfw3, those are libraries that meet the OpenGL specifications.
@@insentia8424 You are wrong! glut and glfw are on top of openGL and are just extra tools for creating windows and handling inputs. OpenGL itself is implemented with Mesa 3D library on Unix like OSes, not sure about how Windows implements it.
Nice! Also, well done by not using something like SDL, but handling the OS stuff yourself. I started doing that after working in the industry and it's really cool. :)
@@leeoiou7295 well, there are no inherent disadvantages to SDL, its just that not using something like SDL means that if you want to port your program to a different platform, you'll need to do all of the platform specific implementation by hand, meaning you will have more control and understand better how a certain platform works, as well as having to actually do things for yourself. For example, if you want to create a window in Windows, you do it one way, but if you want to do it in a Linux distro you have to do it in another way, which means that you'll have to create your own abstractions or ways to select what piece of platform specific code to use when compiling for different targets. Which is what SDL does under the hood for you.
@@superduper6090 what? i never said that SLD is bad. I said that there is no disadvantage to SDL lmao. Read my comment carefully, cause what i explain is the reason why using SDL is GOOD.
Libraries like GLFW implement Win32 in the backend and fill it up with extra glitter and sparkles to make it very easy to get going, whereas this guy is writing everything from scratch with no pre-made libraries.
Youre always gonna be dependent on someone...Operating Systems, Hardware Manufacturers, User Demand. No matter what you do in life youre always gonna be dependent on someone, because thats how a society works. So avoiding all and any dependencies is not gonna work. But Id still agree that carefully selecting your dependencies is the best course of action.
I agree to a point, but these engines really rope new game developers into becoming entangled and dependent, mainly on their animators. Animation though can be done with shaders, so you actually don't have to make use of Unity's tools, for example, you can just make a single Unity scene, single game object in that scene, single script as an entry point, then just have everything created procedurally, and create your own game object and scene format. Put all the code in a 'Src' folder, then, if it needs to be ported to Unreal engine later, what one could do is just use Chat GPT 3.5 turbo or something to convert it, touch it up, and then work on porting from there.
yes, but every person i'm dependent on doesn't know qi jiguang. or julius orion smith III. all must be removed. people are stupid. people are stupid. i went to school for gifted kids decades ago, you know what? we are more intelligent. people suck. especially microsoft (rofl "microsoft")
If you really wanted to make a game without using any "libraries", youd have to make your own hardware entirely. (Depending on your definition of what is considered a library) But yeah i dont really consider opengl to be a library, i consider low level abstractions not to be libraries in a sense, (how low level something must be to not be considered a library is my arbitrary opinion) relative to other libraries. Though it does the same thing most libraries do; load procedures that allow you to interface with hardware in an abstract way. Not that it really matters, its just cool how the tools we use are the culmination of sometimes hundreds of years of research.
If you really want to use no library, you have to write your own OS and build tool for that OS and your own driver for god knows how many devices you would like to support. Good luck with that. I actually encourage starters to use 3rd party libraries, since libraries themselves are required to be learned as well. But of course you should eventually learn how to code for specific OS too, though it's optional kinda.
Bro this directx kid wont quit yappin smh you don't need to make an os, just a driver for no library and you arent a "starter" for using things like opengl when coding an engine
Use OS specific apis. In case of Windows - WinAPI. And don't use STL at all. Or at least make a custom memory pools and allocators for STL. Just an advice.
@@cheerwizard21 any advice on how to make a simple 2D RPG game engine for instance, without utilizing the STL? I can hack together a game with WinGDI pretty easily, and would like to eliminate any unneeded overhead -- not that my simple pixel projects are even that resource intensive, I just would like to learn.
@@MrValsung 1. As I mentioned, just make memory pools (you can learn about that, just google). And then google how to add a custom allocator structure to STL container. Inside this structure allocate/deallocate methods - just use allocation calls to your own memory pools. 2. If you want to completely eliminate STL, then check Molly Rocket (Casey Muratori) on that, he is doing everything from scratch and is not using STL as well. 3. You need to learn how to build string, vector, hash table, linked list or tree (optional just in case). Do also some research and learn memory managment really well, so you can utilize your preallocated heap memory, big/small chunks of memory, CPU caches (L1, L2, L3), branch prediction inside loops. I personally always choose to customize STL memory allocations with memory pools, since I know STL pretty well and the only thing I really need to is to completely eliminate heap allocations from STL and replace it with getting memory chunks from preallocated heap in the beginning of program - which is thousands times faster than default STL :)
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.
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
I couldn't avoid to notice you're #including cpp files. Why? We normally include .h files only with declarations and let the implementations in .cpp files. That way you don't get duplicated symbol errors.
but why write everything yourself? learning to use well written libraries will save you time and hopefully free you from solving problems thats already been solved.
@@flamingowrangler...but he does have a point, it's great to put something like this on a resume, but the problem that crops up for me, is that we developers need to attend streams and be where the players are more and serve them if we're making games, rather than just serve our own self interests. That's a huuuge lesson I've learned over a long period of time. There's a tendency to stay in the comfort zone where the other artists, developers, etc... are, and it removes us from connecting with the people we're trying to make stuff for. What the players seem to be looking for, is running around a semi-open world with good character driven stories and beautiful visually appealing worlds they can explore around, at least from the streams I've watched and the players I've connected with... So just going where the players are for the games that you loved when you were growing up, and making a prototype for them, and doing it minimum viable product, you would tend to want to use whatever tool you're well versed in and is fastest and easiest.
@@astrahcat1212 who do you think has a higher chance of being hired, a guy with a portfolio where they made a game engine and a game in it, or a guy that made an assetflip in unity?
@@astrahcat1212Sure, but down the line you will want to write shaders to make your game more unique, improve performance, etc. and understanding how things work under the hood helps there. You may even reach a point where a game engine just doesn't support something that you want to do, at which point you can either try to add it to an open source engine, or make your own. Also, it's fun.
@@widgitymaking your own engine just for one feature is completely deranged. You would just end up with slow, clunky garbage with weird api but at least it has that one fucking feature. Writing an engine is a commitment which takes years to turn it into something usable and at this point you aren’t a game dev, you are an engine dev. It is just as dumb as creating your own cpu when you can’t find one instruction that you need.
oh boi he runs windows lmao wait until you need to port to embedded devices/android/linux. those lovely Macroshaft exclusive APIs are gonna be sweet to deal with.
With a little forethought it's really not that bad, add a layer of indirection so you call your own function that calls the windows api, then when you're ready to make it crossplatform, you replace the windows api call with the new one. You should do this anyways even if you're using a window library in case you want to swap to a different one or add support for a platform that the library doesn't support (e.g. Android when you're using GLFW). Generally you want to avoid coupling your main engine code to the window library.
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
It depends on your deadline requirements. But overall, it's only useful for educational purpose. If you are not sure that some other libraries are stable and fast enough, it means that you have never used them and you have no clue how they work. If you want to support some unknown console hardware or very old hardware that may not suite library requitements - than YES, you are forced to write a hardware specific implementation. BUT, if your goal is to make an engine for Windows, than its just a huge waste of time. Because making a decent 3D engine by itself will require lots of architecture decisions and implementations.
For simpler games it might be okay, and C++ is more portable and used across the consoles. A 3D engine that would make the next Fortnite or something, I see what you mean.
@@astrahcat1212 For simpler games some people are not even creating game engines. Or if they create one, they really try to make it quite fast and definetely don't waste time on rewriting GLFW or SDL or anything else that's stable and fast enough. What's the point of not using simple and fast GLFW? Why writing 500 lines of code to setup a window with input events? What if you will add a support in future for Linux and you will need to play with X11 or other Linux window API and write ~300 lines of code to make trivial things - window with input events? That's not even considerable, that's always huge waste of time. In real world games, I was using internal company game engine, where they were using around 20-30 libraries and for such trivial things like windowing, input events - they were simply using SDL and that's it.
Don't use this if you solely wanna make games just use engines. This is cool and all but if you want to make actual games then you'll not be able to achieve everything you'd use along the way with game engines even if you did it'd just take tremendous amount of time. I also made 2d engines and they sucked so I just do premade engines now.
Playful remark about the title: "you don't need libraries, but use OpenGL, Open Graphics LIBRARY". It's in the name 😆
Yeah the name is misleading OpenGL is not really a library
@@tlgaming6725what is it and what is the difference to a library?
@@somename5632opengl despite its name is in fact something called graphics api. Set of functions that are running on the gpu. We can use opengl drivers on our graphic cards to render things onto a window for example
I really expected him to write to /dev/fb0 or something crazy like that
@@somename5632OpenGL is and API standard, which graphics card vendors implement. This is, so your graphics code can work on graphics cards manufactured from a wide range of vendors, rather than having to write different code for every different kind of card. The OS usually helps you by providing some kind of standard OpenGL header with function pointers to the functions implementation of the graphics card in the PC, so in that sense it is a little bit like a library, but in essence it is not.
Here's my current take on this subject: If you're building an engine specifically to build actual projects or to learn about a specific feature, then just use existing open source implementations for rest of the features you're not interested in or focused on and write a thin API around them for your application to use. These libraries can be replaced with your own implementation if required in the future, I've seen many companies do this like valve and roblox. As an example:
I'm interested in learning about entity component systems and I want to write a simple C based engine that utilizes such a system. In this case, I would simply use SDL to handle sound, input and windowing to quickly get started and possibly even a rendering library for visualization. I would then build the ECS system myself since that's what my engine is focused on. Later I can swap out the rendering library with my own renderer, but only if required.
The point of saying all this, not as a response to your video necessarily, is people shouldn't worry too much about using existing libraries. They can be swapped out whenever required, focus on what you want to focus on for now. Chances are existing libraries will fulfil your requirements.
I live all of these "you dont need xxx to create game" videos. Like literally, every single video tries to proof that you can roll your own engine and as proof they show empty scene with one colored cube at the end. No it is not "game engine". You don't have input system, multiple rendering pipelines, multiple platforms, audio mixer, netplay, entity managment, shaders, particle systems, physics, component systems, pbr materials, terrain system, level editing tools, animations, ui, scripting systems, lighting systems, ai, navigation, scene graph, (....) I can do it all the day.
Of course, I encourage everyone to try making simple 3d stuff by themeselves, its great fun and you can learn a lot with that in terms of low level programming.
But please stop with those "you dont need game engine" videos already..
Fun fact, author of video didn't actually mention any argument of "why you should not use any libraries for game engine". If you are making a clickbait title for video, you should at least try to argue why it is good/bad.
You have courage. I also made a game library for myself using several small libraries and it still demanded a ton of work and study.
I understand why it seems appealing, but now you depend on the Windows API which is even worse in the long run. It makes your game much less portable to other OS-es. Even if you don't want to depend on an existing game engine, you could use a cross-platform library like SDL which is low-level enough to give you great control, but still portable.
You abstract the game logic from the Windows API so it's portable. This is the main problem I had using Unity and Unreal is that it entangles you unless you think very carefully about your code being abstract.
SDL sounds reasonable.
SDL could do the job, but the WinAPI is pretty good. Not to mention Wine can be used on Unix systems
@@rytif I was thinking about Linux specifically, but there are also a great number of Mac fans out there. @victorthevictor1976 Banking on "Unix-like users will just use Wine" is not the right way of thinking. Wine should be considered as a last resort when there are no alternatives available. Games always have alternatives: other games. Though I think you can still go cross-platform later, if needed, just make sure to separate your system calls to distinct modules.
@@rytif IOS Android MACOS WEB Steam Deck(Linux, still better to have native support than using Proton), and Windows is slowly losing popularity. It's also potentially future proof for new platforms, but it's a maybe.
i think you predicted the future! good video!
Now make it work for x11 and macos... kidding! You're awesome!
Agreed. I feel like it was hidden from me for a long time that Windows already gives you everything you need to make a game. They have image loaders, they have 3d apis, they even have 3d audio.
I mean that's fair enough, but what if you want to make your game cross-platform? Then you'd have to deal with every platform's different APIs.
@@vesk4000You do anyway if you want to have a toolset that can port to consoles, but better thing to do is abstract the game logic from the renderer, so that you can just change the code in your functions according to the renderer. You can just start with using GDI if you wanted to, then later implement OpenGL, Vulkan or Direct3D.
or just use something simple that's cross platform and doesn't require windows... please,
@@MisterZig0 to provide a game for 2 people on linux, great advice for a beginner... dealing with problems on 3 different OS's
@@qqshutup7175I mean I'd rather have the extra feedback and it's not like SDL or similar are bad.
i made my own 2D game framework using OpenTK and i learned a lot about modern graphics rendering (textures, vertex specification, GLSL, matrices, etc).
i have never learned so much from a single project, but it was also the most painful 6 months of my life.
also wrote a 3D model loader for AutoDesk but i gave up on learning more about 3D after that (lighting, collision, camera).
what did you use for audio when you made your engine using OpenTK?
"you don't need libraries"
my brother in christ, windows.h
all jokes aside though this is very impressive
My brother in Christ, "opengl32.lib;kernel32.lib;user32.lib;gdi32.lib;shell32.lib;"
What does ".lib" stand for again?
That's not a library.
@@TU7OV I mean yeah it’s *technically* not a library but it is a header file you include that provides functions, typedefs and structs (exactly what libraries do except it’s for interfacing with the OS). I think that’s close enough for you to not be *that guy* on a comment with 10 likes.
The title is imprecise as what he meant is "libraries outside of OS functionality" which as you said is still awesomely impressive as the OS doesn't give you much at all in the way of writing a game. I wouldn't know how to do this myself without at least SDL2 and GLFW
Yeah, go all the way in and write your own OS.
Well, OpenGL is a library. It even has the word in its name.
OpenGL is not a library, is an API, it just have "graphics library" in the name because is an open version of IRIS GL, and they did keep the GL in the name, when IRIS GL became open source they named it OpenGL.
OpenGL is a crossplatform standard for graphics. Thats all it is. There is no "OpenGL library code" that is written by the OpenGL creators. They jus say "hey, this is how things should be", and then each vendor implements their part so that everyone can write graphics programs with a common interface. Thats why its an API. If you want, you could manually find a way to interface in different platforms with different graphics cards and use their specific machine languages for their architecture specific instructions. We could also make computers out of sand and stop buying them. The purpose of OpenGL is to prevent having to program a different program for both the main application and for the runtime compiled shaders for each and every single different GPU that exists in the world. If we lived in the simpler times when your OS did not take control over its resources like it does nowadays, and when graphics cards were not a thing, then we could all write our own software renderer and we would actually be doing all the legwork ourselves. But... since we have an operating system that takes control of our resources and doesnt allow us to directly write to memory wherever we want, we cant make our own software renderer that runs on the CPU, we'd have to rely on OS specific drawing commands at some point... and nowadays with all the graphics cards that exist, yeah, im sorry but we're FORCED to used APIs because we live in a world of standards where you cant even do things by hand anymore. Thats why all the people who write software renderers these days always make them export to image files rather than displaying them on the screen. But hey, if you want to write machine code for every single GPU out there, you're free to do it.
@@K3dev I'll give him OpenGL. But I better not see him use the "standard library" anywhere. 😛
@@K3dev he's using an implementation of OpenGL as a library
@@heliusuniverse7460 he is not choosing the implementation, that's why he needs to use wglgetprocaddress, because he is just using the API and Windows is getting the implementation from the gpu drivers, if you want to blame someone, blame the OS or the Gpu manufacturer for using the OpenGL implementation as a library and not as executing the opengl functions directly. If he was in mac he would be calling OS internal functions instead (using the same API)
very cool!
You also dont need condoms to have sex but they are useful
I agree using an existing close engine is fairly limiting.
I don't know if it is my eyes or my monitor but when you move object in your game I believe I can see interlacing between frames. Was it intentional or a side effect of something ? This looks great btw.
Thanks :) The interlacing is a side effect of the video. I'm going to look into that for the next one.
@@The_Simplest_Game Not sure which video editor you're using but usually there's a list of output resolutions when exporting and 1080i for instance is 1080 interlaced as opposed to 1080p which is not.
Sehr Interessant
The only reason I want to make a engine is to flex, and learn from it.
Are you going to make a tutorial series on doing that? I'm currently kinda stuck moving on from the basic tutorial (console program and stuff) to the more advanced stuff like making GUI and using libraries. I don't even know how to make an installer for my finished programs...
I’m probably not going to make a full on tutorial series about this, but I’m considering going into more detail in some of these aspects. I have written a small immediate mode gui system and want to show that in the future, but that still requires some more work.
@@The_Simplest_Game Interesting! Looking forward to that!
I recommend watching the Cherno, victor gordon, or ogldev while waiting. They have good c++ and OpenGL videos. It might be slow at first but there’s a lot to understand before making more complicated graphics things from scratch if that’s what you want to learn.
@@The_Simplest_Gamedefinitely interested in a tutorial series. I have been learning C++ Win32 API graphics programming only utilizing WinGDI so far, so I understood alotta the code, despite never having used openGL. what resources did you use to learn how to do all of this btw?
Writing your own tool is educational, leveraging existing tool is productive.
done the same, just finished rigging my puppet, entirely in c/c++ win32, no blender, took 12 weeks to design it myself.
but faster next time. and all my rotations are euler angles. :) and my entire game app is like 700kb haha.
That's really cool! Check your video export settings though, that interlacing is really annoying.
Thanks :) I'll make sure it's fixed in the next one.
right now I'm trying to load jpgs/pngs. its too bad .bmp is the only file you can load by default.
understanding libraries is a nightmare .
Just wondering if you were going to release it as open source? I'd love to have a look at what you've done as I'm trying to do the exact same thing right now.
I don't have plans for that at the moment, but almost all code should be visible in the video.
@@The_Simplest_Game would have been a lot easier if we could just copy from github instead having to copy everything line by line. this is just mean.
@@The_Simplest_Game If you are not gonna sell it, you should make it open source. Free software and open source developer mindset is a good thing not just for other but especially for you to grow and learn more.
super cool
I made a 2D Game Engine in DirectX 11/OpenGL and W32. When porting it to MacOS, I couldn't be bothered to learn objective c or metal so I just used SDL 😂😂😂
Is there a link to the source code? I would like to see how you initialize OpenGL context on windows
Isnt opengl a library too? I thought you were even going to write that from scratch haha
OpenGL is not a library, it's a specification. If you're using only OpenGL you need to write all the code that implements OpenGL yourself.
The actual libraries that do that for you are stuff like glut or glfw3, those are libraries that meet the OpenGL specifications.
@@insentia8424 You are wrong! glut and glfw are on top of openGL and are just extra tools for creating windows and handling inputs. OpenGL itself is implemented with Mesa 3D library on Unix like OSes, not sure about how Windows implements it.
Nice! Also, well done by not using something like SDL, but handling the OS stuff yourself. I started doing that after working in the industry and it's really cool. :)
what are the disadvantages of using SDL?
@@leeoiou7295 well, there are no inherent disadvantages to SDL, its just that not using something like SDL means that if you want to port your program to a different platform, you'll need to do all of the platform specific implementation by hand, meaning you will have more control and understand better how a certain platform works, as well as having to actually do things for yourself. For example, if you want to create a window in Windows, you do it one way, but if you want to do it in a Linux distro you have to do it in another way, which means that you'll have to create your own abstractions or ways to select what piece of platform specific code to use when compiling for different targets. Which is what SDL does under the hood for you.
@@AlFredo-sx2yynah thats bs. SDL is a great library that abstracts logic that you as a programmer dont need to know.
@@superduper6090 what? i never said that SLD is bad. I said that there is no disadvantage to SDL lmao. Read my comment carefully, cause what i explain is the reason why using SDL is GOOD.
@@superduper6090 I dont understand why people like you feel the need to pick a fight with people who are literally agreeing with you.
cool! also wanted to ask , how did you implement the field reset animation in pong? tried to recreate it, but got stuck
This is the main function in the fragment shader. Hope it helps :)
float widthScale = u_resolution.x / TargetResolution.x;
float heightScale = u_resolution.y / TargetResolution.y;
float scale = max(widthScale, heightScale);
vec2 resolution = u_resolution / scale;
vec2 uv = UV * resolution;
vec2 origin = u_origin * resolution;
vec2 middle = vec2(0.5) * resolution;
float distanceOrigin = distance(uv, origin);
float distanceMiddle = distance(uv, middle);
Color = u_time < 1.2
? distanceOrigin < u_time * 2500.0 ? OverlayColor : u_color
: distanceMiddle < (u_time - 1.2) * 2500.0 ? u_color : OverlayColor;
Do it without openGl
open gl is a library
This is cool! It would be nice to have access to a github with just the Win32 and OpenGL integration.
You should try vulkan! It's not *that* much harder but the granularity you get is awesome when trying to build for low powered hardware
"not much harder" 💀
Yeah not that much harder but the enormous amount of lines and concepts to master to get more than a simple triangle can be very daunting
I still have not delved into Vulkan. What is wrong with me?
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?
But C++ uses libraries by default...
He's talking about graphic libraries no?
He's talking about stuff like SDL
Libraries like GLFW implement Win32 in the backend and fill it up with extra glitter and sparkles to make it very easy to get going, whereas this guy is writing everything from scratch with no pre-made libraries.
Youre always gonna be dependent on someone...Operating Systems, Hardware Manufacturers, User Demand. No matter what you do in life youre always gonna be dependent on someone, because thats how a society works. So avoiding all and any dependencies is not gonna work. But Id still agree that carefully selecting your dependencies is the best course of action.
I agree to a point, but these engines really rope new game developers into becoming entangled and dependent, mainly on their animators. Animation though can be done with shaders, so you actually don't have to make use of Unity's tools, for example, you can just make a single Unity scene, single game object in that scene, single script as an entry point, then just have everything created procedurally, and create your own game object and scene format. Put all the code in a 'Src' folder, then, if it needs to be ported to Unreal engine later, what one could do is just use Chat GPT 3.5 turbo or something to convert it, touch it up, and then work on porting from there.
make your own os/computer. easy fix
@@screencancer4732😂😂u will rely on parts and if u dont you will rely on material, if you dont you will...
yes, but every person i'm dependent on doesn't know qi jiguang. or julius orion smith III. all must be removed.
people are stupid. people are stupid. i went to school for gifted kids decades ago, you know what? we are more intelligent. people suck. especially microsoft (rofl "microsoft")
If you really wanted to make a game without using any "libraries", youd have to make your own hardware entirely. (Depending on your definition of what is considered a library)
But yeah i dont really consider opengl to be a library, i consider low level abstractions not to be libraries in a sense, (how low level something must be to not be considered a library is my arbitrary opinion) relative to other libraries. Though it does the same thing most libraries do; load procedures that allow you to interface with hardware in an abstract way.
Not that it really matters, its just cool how the tools we use are the culmination of sometimes hundreds of years of research.
do you have like a discord server?
I once started coding a game engine but got really stuck on shaders.
well sure you could be a carpenter starting with no tools but you gotta be sure you want to
This is brilliant analogy, lol
What's the point of this video?
You don't give a link to a source code, and you're not gonna make a tutorial.
You have a nice voice!
If you really want to use no library, you have to write your own OS and build tool for that OS and your own driver for god knows how many devices you would like to support. Good luck with that.
I actually encourage starters to use 3rd party libraries, since libraries themselves are required to be learned as well.
But of course you should eventually learn how to code for specific OS too, though it's optional kinda.
not manufacturing your own pc from scratch by mining ore is just using a physical library
this doesn't make sense
Bro this directx kid wont quit yappin smh you don't need to make an os, just a driver for no library and you arent a "starter" for using things like opengl when coding an engine
Why do you include a cpp file?
B-but Open GL is a library :(
No, is just an API technically
@@samarthtandale9121 its called open graphics LIBRARY
@@samarthtandale9121 "technically" all libraries have APIs
DIY FTW!
How to open a window and draw something in it using only std library?
Use OS specific apis. In case of Windows - WinAPI.
And don't use STL at all. Or at least make a custom memory pools and allocators for STL. Just an advice.
@@cheerwizard21 thank you.
@@cheerwizard21 any advice on how to make a simple 2D RPG game engine for instance, without utilizing the STL? I can hack together a game with WinGDI pretty easily, and would like to eliminate any unneeded overhead -- not that my simple pixel projects are even that resource intensive, I just would like to learn.
@@MrValsung 1. As I mentioned, just make memory pools (you can learn about that, just google). And then google how to add a custom allocator structure to STL container. Inside this structure allocate/deallocate methods - just use allocation calls to your own memory pools.
2. If you want to completely eliminate STL, then check Molly Rocket (Casey Muratori) on that, he is doing everything from scratch and is not using STL as well.
3. You need to learn how to build string, vector, hash table, linked list or tree (optional just in case). Do also some research and learn memory managment really well, so you can utilize your preallocated heap memory, big/small chunks of memory, CPU caches (L1, L2, L3), branch prediction inside loops.
I personally always choose to customize STL memory allocations with memory pools, since I know STL pretty well and the only thing I really need to is to completely eliminate heap allocations from STL and replace it with getting memory chunks from preallocated heap in the beginning of program - which is thousands times faster than default STL :)
are you Sebastian Lague ?
Probably the same country, hence the accent
@@anon1963 sebastian is from denmark - he's from germany i think
@@RavuyI thought Sebastian was from Cape Town?
Not even using glfw is a bit excessive. Although its better for personal projects, it will give you headache in long run.
Glfw is so bloated and bad
Why you say you don't need libraries then use OpenGL?
Now use vulkan, or no opengl
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.
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
Ce mec est francais 10000000000000000%
I couldn't avoid to notice you're #including cpp files. Why? We normally include .h files only with declarations and let the implementations in .cpp files. That way you don't get duplicated symbol errors.
Amen. Including cpp files should be done only for inline functions.
but why write everything yourself? learning to use well written libraries will save you time and hopefully free you from solving problems thats already been solved.
learning what libraries are doing under the hood is extremely valuable
@@flamingowrangler...but he does have a point, it's great to put something like this on a resume, but the problem that crops up for me, is that we developers need to attend streams and be where the players are more and serve them if we're making games, rather than just serve our own self interests. That's a huuuge lesson I've learned over a long period of time. There's a tendency to stay in the comfort zone where the other artists, developers, etc... are, and it removes us from connecting with the people we're trying to make stuff for. What the players seem to be looking for, is running around a semi-open world with good character driven stories and beautiful visually appealing worlds they can explore around, at least from the streams I've watched and the players I've connected with... So just going where the players are for the games that you loved when you were growing up, and making a prototype for them, and doing it minimum viable product, you would tend to want to use whatever tool you're well versed in and is fastest and easiest.
@@astrahcat1212 who do you think has a higher chance of being hired, a guy with a portfolio where they made a game engine and a game in it, or a guy that made an assetflip in unity?
@@astrahcat1212Sure, but down the line you will want to write shaders to make your game more unique, improve performance, etc. and understanding how things work under the hood helps there. You may even reach a point where a game engine just doesn't support something that you want to do, at which point you can either try to add it to an open source engine, or make your own.
Also, it's fun.
@@widgitymaking your own engine just for one feature is completely deranged. You would just end up with slow, clunky garbage with weird api but at least it has that one fucking feature. Writing an engine is a commitment which takes years to turn it into something usable and at this point you aren’t a game dev, you are an engine dev. It is just as dumb as creating your own cpu when you can’t find one instruction that you need.
Let's be real. You do if you want to actually make something good.
Hello, I want to create MMO RPG. Will your engine be sufficient for this?
no
oh boi he runs windows lmao
wait until you need to port to embedded devices/android/linux. those lovely Macroshaft exclusive APIs are gonna be sweet to deal with.
With a little forethought it's really not that bad, add a layer of indirection so you call your own function that calls the windows api, then when you're ready to make it crossplatform, you replace the windows api call with the new one. You should do this anyways even if you're using a window library in case you want to swap to a different one or add support for a platform that the library doesn't support (e.g. Android when you're using GLFW). Generally you want to avoid coupling your main engine code to the window library.
why tho
Dude, a cube renderer is not a game.
Who asked
Open Graphic Lib...
am i the only one or does he talk like sebastian league?
XD
"you don't need libraries to write a game engine in c++"
>proceeds to use opengl (open graphics library)
🤦🤦🤦🤦🤦🤦🤦🤦🤦
You have to use a library at some point. It’s just not an external library
@@colleagueriley860 define external
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
you are using a graphics lib. Your title does not really make sense
Nerd.
.
ich sehe einen deutschen akzent, wenn ich ihn sehe!😂
You are not transparent either. Skip
It depends on your deadline requirements.
But overall, it's only useful for educational purpose.
If you are not sure that some other libraries are stable and fast enough, it means that you have never used them and you have no clue how they work.
If you want to support some unknown console hardware or very old hardware that may not suite library requitements - than YES, you are forced to write a hardware specific implementation.
BUT, if your goal is to make an engine for Windows, than its just a huge waste of time. Because making a decent 3D engine by itself will require lots of architecture decisions and implementations.
For simpler games it might be okay, and C++ is more portable and used across the consoles. A 3D engine that would make the next Fortnite or something, I see what you mean.
@@astrahcat1212 For simpler games some people are not even creating game engines. Or if they create one, they really try to make it quite fast and definetely don't waste time on rewriting GLFW or SDL or anything else that's stable and fast enough.
What's the point of not using simple and fast GLFW? Why writing 500 lines of code to setup a window with input events? What if you will add a support in future for Linux and you will need to play with X11 or other Linux window API and write ~300 lines of code to make trivial things - window with input events?
That's not even considerable, that's always huge waste of time. In real world games, I was using internal company game engine, where they were using around 20-30 libraries and for such trivial things like windowing, input events - they were simply using SDL and that's it.
Don't use this if you solely wanna make games just use engines.
This is cool and all but if you want to make actual games then you'll not be able to achieve everything you'd use along the way with game engines even if you did it'd just take tremendous amount of time.
I also made 2d engines and they sucked so I just do premade engines now.
Nope.
Complex game requires solid game engine
Complex games require optimized and specific engines.
don't be lazy bum tho
You don't need c++ at all
Good old C is better. Is that what you mean ?
Troll
@@evilwizardtherapist actually, yeah. XD
Assemble CPU machine code by hand.
Just open a hex editor and start typing the numbers😂