Making a game engine...
Making a game engine...
Don't flame me. Don't tell me to learn c++ first. Don't tell me I can't do it. Don't tell me I won't be able to do it. Don't tell me it's impossible.
NOTHING is impossible, just difficult. And if it was easy, why would I do it.
I WANT to learn it this way. This is the best way for me to learn about basic c++...
Anyways, enough with the antiflamers. I've learned about loops, if statements, structures, header files, file input/output (kinda... haven't used it yet but I know how to sorta...)
I somewhat understand classes, but to fully understand all these basics, I need to see them in proper use. I need to see how they can be used, how they can be pushed, how they can be combined. And seeing as I am planning on following solo game design (epic fail, I know... But it's my life choice... Lawyer/gameprogrammer), it would be best to see how they can be used in game programming. And seeing as the best place to start game programming is the engine itself. I'd like to either be taught how to make one, or see the code for one.
I plan on using directx and c++.
Are there any books that I can read, or websites that I can read that will teach me how to create a game engine using c++ and directx? Or are there any open source 2d game engines that were created using directx?
If you're going to be telling me to learn c++ first before going into advanced stuff. Get the **** off. It isn't teaching me shiet. It's all common sense and logic in the basic stuff, in the advanced I can LEARN.
NOTHING is impossible, just difficult. And if it was easy, why would I do it.
I WANT to learn it this way. This is the best way for me to learn about basic c++...
Anyways, enough with the antiflamers. I've learned about loops, if statements, structures, header files, file input/output (kinda... haven't used it yet but I know how to sorta...)
I somewhat understand classes, but to fully understand all these basics, I need to see them in proper use. I need to see how they can be used, how they can be pushed, how they can be combined. And seeing as I am planning on following solo game design (epic fail, I know... But it's my life choice... Lawyer/gameprogrammer), it would be best to see how they can be used in game programming. And seeing as the best place to start game programming is the engine itself. I'd like to either be taught how to make one, or see the code for one.
I plan on using directx and c++.
Are there any books that I can read, or websites that I can read that will teach me how to create a game engine using c++ and directx? Or are there any open source 2d game engines that were created using directx?
If you're going to be telling me to learn c++ first before going into advanced stuff. Get the **** off. It isn't teaching me shiet. It's all common sense and logic in the basic stuff, in the advanced I can LEARN.
Basically. You build things from the ground up. And just saying. It's almost mandatory that you learn STL to make a game engine. Sorry
I recommend you finish your book or whatever you're learning from. Making the engine will be a lot easier, and you'll know more efficient, easier ways of doing things.
And when people have little experience, and try to tackle as something as big as a game engine, which can take years to make, it's just asking for failure. Start simpler, and go from there. Make a pong clone or something. I know, it seems boring and not fun, but if you can actually finish it 100% you'll be another skill level higher. You can't just start making huge projects, which take professionals years to make.
And I'm not flaming you or anything. I'm just being real.
I recommend you finish your book or whatever you're learning from. Making the engine will be a lot easier, and you'll know more efficient, easier ways of doing things.
And when people have little experience, and try to tackle as something as big as a game engine, which can take years to make, it's just asking for failure. Start simpler, and go from there. Make a pong clone or something. I know, it seems boring and not fun, but if you can actually finish it 100% you'll be another skill level higher. You can't just start making huge projects, which take professionals years to make.
And I'm not flaming you or anything. I'm just being real.
Originally Posted by ɑrtemis
Basically. You build things from the ground up. And just saying. It's almost mandatory that you learn STL to make a game engine. Sorry
I recommend you finish your book or whatever you're learning from. Making the engine will be a lot easier, and you'll know more efficient, easier ways of doing things.
I recommend you finish your book or whatever you're learning from. Making the engine will be a lot easier, and you'll know more efficient, easier ways of doing things.
Then I'll learn STL if I get confused.
not reading a book. I use cplusplus.com/tutorials and look at the code given to me... I then try and change the code to see what I can do with it. If I experience errors, or problems then I go back and I read up on it. If I still don't understand I re-read it, if I still don't understand I give up for a day and come back the next day and re-read it with a clear mind. If then I still don't understand, I re-read everything that could possibly help me on that website, if then I still can't get it I ask for help.
Originally Posted by VvITylerIvV
Then I'll learn STL if I get confused.
not reading a book. I use cplusplus.com/tutorials and look at the code given to me... I then try and change the code to see what I can do with it. If I experience errors, or problems then I go back and I read up on it. If I still don't understand I re-read it, if I still don't understand I give up for a day and come back the next day and re-read it with a clear mind. If then I still don't understand, I re-read everything that could possibly help me on that website, if then I still can't get it I ask for help.
not reading a book. I use cplusplus.com/tutorials and look at the code given to me... I then try and change the code to see what I can do with it. If I experience errors, or problems then I go back and I read up on it. If I still don't understand I re-read it, if I still don't understand I give up for a day and come back the next day and re-read it with a clear mind. If then I still don't understand, I re-read everything that could possibly help me on that website, if then I still can't get it I ask for help.
Please understand game engines take years to make by professionals.
Originally Posted by ɑrtemis
You don't understand you need a complete knowledge of C++ to do these things. Games revolve around objected oriented programming and polymorphism.
Please understand game engines take years to make by professionals.
Originally Posted by VvITylerIvV
I understand that... I never said I wanted to finish making one. I said I want to learn how to make one so I can learn the more basic things. Please understand that.
I'm just being real.
A kid can't just play a violin concerto(in this case an engine). He starts with smaller things and masters them(smaller projects), and moves up until he has the skills, technique, and knowledge to play the violin concerto(in this case engine)
It's not going to go how you planned it out. You're going to have to learn DirectX API first, before actually incorporating in your project. After you've grasped Direct3D, then you can start..
making a game engine... honestly... nop, it might be really rude.. but you won't even make 1% of it...
You should really train your basic c++ skills... concepts.. etc.. Then do what everyone is saying... Learn D3D.. etc.. This takes time.
You can try a simple game.. but a engine...
~ Fixed by hell ~
You should really train your basic c++ skills... concepts.. etc.. Then do what everyone is saying... Learn D3D.. etc.. This takes time.
You can try a simple game.. but a engine...
~ Fixed by hell ~
Originally Posted by 'Bruno
making a game engine... honestly... nop, it might be really rude.. but you won't even make 10% of it...
You should really train your basic c++ skills... concepts.. etc.. Then do what everyone is saying... Learn D3D.. etc.. This takes time.
You can try a simple game.. but a engine...
You should really train your basic c++ skills... concepts.. etc.. Then do what everyone is saying... Learn D3D.. etc.. This takes time.
You can try a simple game.. but a engine...
Originally Posted by ɑrtemis
If you want to learn more basic things start smaller.
I'm just being real.
A kid can't just play a violin concerto(in this case an engine). He starts with smaller things and masters them(smaller projects), and moves up until he has the skills, technique, and knowledge to play the violin concerto(in this case engine)
Originally Posted by 'Bruno
making a game engine... honestly... nop, it might be really rude.. but you won't even make 10% of it...
You should really train your basic c++ skills... concepts.. etc.. Then do what everyone is saying... Learn D3D.. etc.. This takes time.
You can try a simple game.. but a engine...
You should really train your basic c++ skills... concepts.. etc.. Then do what everyone is saying... Learn D3D.. etc.. This takes time.
You can try a simple game.. but a engine...
Originally Posted by ɑrtemis
Exactly what i tried to say. If you start big you're set for failure.
Not gonna happen.
Originally Posted by Hell_Demon
Not gonna happen.
Originally Posted by Void
Game engine is kind of a big project for anyone who's on their own.. Think smaller..
I KNOW IT'S A BIG PROJECT. THATS WHY I WANTED THIS PROJECT.
Originally Posted by VvITylerIvV
Not with that attitude. Posting here and not answering my question is the same as telling a dead man to die -- it's useless.
I KNOW IT'S A BIG PROJECT. THATS WHY I WANTED THIS PROJECT.
I KNOW IT'S A BIG PROJECT. THATS WHY I WANTED THIS PROJECT.
Game engine is kind of a big project for anyone who's on their own.. Think smaller..
Dude. I'm just being fucking real.
