ok... (DirectX)(WTL)(MFC)
-
Previous: Ok, im going to explain this vary carfully... with all the details and every thing "just to make sure im in the right place." My recent thread discused about rather i should use WTL, DirectX, or MFC. I ended up with me using DirectX. Now: The thing that i am going to program "in do time, after allot of study hours and practice" is program a 2D RPG "Two Dimensional Role Playing Game" Engine "The thing that i use to make the game." This Engine will be entirly in a windows format, every little thing. I am not programming the game, i am just programming the tool that will program the game. "Now that every one knows that..." Which device am i better off in using? WTL, Wich makes it easier to do windows stuff without the bulky MFC format. MFC "Which gives me a lot of extra things i dont need to deal with." Or DirectX, which doest do windows, yet does games? The game is going to be "As i have told you" A RPG that will be played entirely on the .net. Any info on which way i should go would be helpful, and any place to find the tutorials from beginning to end that would teach me what i need to do would also help. Thanks every one! ~SilverShalkin :rose: The gate is opening :rose: :rose: And light as warmth :rose: :rose: And full of knowledge :rose: :rose: Inrichest me :):rose:
-
Previous: Ok, im going to explain this vary carfully... with all the details and every thing "just to make sure im in the right place." My recent thread discused about rather i should use WTL, DirectX, or MFC. I ended up with me using DirectX. Now: The thing that i am going to program "in do time, after allot of study hours and practice" is program a 2D RPG "Two Dimensional Role Playing Game" Engine "The thing that i use to make the game." This Engine will be entirly in a windows format, every little thing. I am not programming the game, i am just programming the tool that will program the game. "Now that every one knows that..." Which device am i better off in using? WTL, Wich makes it easier to do windows stuff without the bulky MFC format. MFC "Which gives me a lot of extra things i dont need to deal with." Or DirectX, which doest do windows, yet does games? The game is going to be "As i have told you" A RPG that will be played entirely on the .net. Any info on which way i should go would be helpful, and any place to find the tutorials from beginning to end that would teach me what i need to do would also help. Thanks every one! ~SilverShalkin :rose: The gate is opening :rose: :rose: And light as warmth :rose: :rose: And full of knowledge :rose: :rose: Inrichest me :):rose:
SilverShalkin wrote: Which device am i better off in using? WTL, Wich makes it easier to do windows stuff without the bulky MFC format. MFC "Which gives me a lot of extra things i dont need to deal with." Or DirectX, which doest do windows, yet does games? Why do you persist in putting DirectX in the list of options when it is a completely different part of your game ? 1/ If you want fast 2D graphics and more than one sound at once, you WILL use Direct X. Simple as that. If you want to do it in 3D ( not as bad an idea as it sounds, you can fix the camera in a 2D style, which would give you a 3D type view without the 3D headaches, give you lighting, etc. ), then OpenGL might be a better option if you find another way to handle sound. 2/ If you want the game to run in a window, then the answer is probably MFC. You are clearly far out of your depth at this point, so using something that offers no documentation is going to be your own private hell. If you want the game to run full screen, as most games do, then the game should probably be Win32. If you're doing an engine, that is, a system that is called by other code to create the game, then still Win32, unless the engine has a GUI, in which case it's more of a games creation system than an engine. An engine to me is an SDK - it's something that gives me the bottom level code so I can write higher level code to achieve my goal, just like GDI stops me from having to find out the details of my graphics card and write each pixel as a byte in memory. 3/ There are no end to end tutorials, but I would *again* recommend you read www.flipcode.com if you're serious. It's full of people who are writing engines, or thought they could write an engine and gave up after a few months. www.gamedev.net is another one, it also hosts nehe.gamedev.net, the best set of OpenGL tutorials out there. Overall I suggest you go to some gaming sites, write some code in the different systems you're considering so you know what it is you're asking, and what each bit will do, and stop asking the same question over & over again. Christian The tragedy of cyberspace - that so much can travel so far, and yet mean so little. "I'm somewhat suspicious of STL though. My (test,experimental) program worked first time. Whats that all about??!?! - Jon Hulatt, 22/3/2002
-
SilverShalkin wrote: Which device am i better off in using? WTL, Wich makes it easier to do windows stuff without the bulky MFC format. MFC "Which gives me a lot of extra things i dont need to deal with." Or DirectX, which doest do windows, yet does games? Why do you persist in putting DirectX in the list of options when it is a completely different part of your game ? 1/ If you want fast 2D graphics and more than one sound at once, you WILL use Direct X. Simple as that. If you want to do it in 3D ( not as bad an idea as it sounds, you can fix the camera in a 2D style, which would give you a 3D type view without the 3D headaches, give you lighting, etc. ), then OpenGL might be a better option if you find another way to handle sound. 2/ If you want the game to run in a window, then the answer is probably MFC. You are clearly far out of your depth at this point, so using something that offers no documentation is going to be your own private hell. If you want the game to run full screen, as most games do, then the game should probably be Win32. If you're doing an engine, that is, a system that is called by other code to create the game, then still Win32, unless the engine has a GUI, in which case it's more of a games creation system than an engine. An engine to me is an SDK - it's something that gives me the bottom level code so I can write higher level code to achieve my goal, just like GDI stops me from having to find out the details of my graphics card and write each pixel as a byte in memory. 3/ There are no end to end tutorials, but I would *again* recommend you read www.flipcode.com if you're serious. It's full of people who are writing engines, or thought they could write an engine and gave up after a few months. www.gamedev.net is another one, it also hosts nehe.gamedev.net, the best set of OpenGL tutorials out there. Overall I suggest you go to some gaming sites, write some code in the different systems you're considering so you know what it is you're asking, and what each bit will do, and stop asking the same question over & over again. Christian The tragedy of cyberspace - that so much can travel so far, and yet mean so little. "I'm somewhat suspicious of STL though. My (test,experimental) program worked first time. Whats that all about??!?! - Jon Hulatt, 22/3/2002
Christian Graus wrote: and stop asking the same question over & over again. I knew that was comming :) Christian Graus wrote: If you want fast 2D graphics and more than one sound at once, you WILL use DirectX. I know that too. But will i use DirectX to build the engine? That was the question... "The engine to me is a map editor that puts your game together :)" I know that Direct Draw and Direct Sound and Music will make my game awesome, but, at the moment i am not make a game but the game engine. So,... Base question... Will i or will i not use DirectX to build my Engine? If not, then what should i use. "Engine, not game" But then, if i was to build my engine so that it would use DirectX, would i use DirectX with my engine? Oi,... Me confused, ill get it sooner or later... I also know about FlipCode but they are all in 3D stuff and stuff and they have no tutorials, there forum is half decent, yet no one responds to questions else you wait till the next day to get them. Ill try www.gamedev.net "i dont think ive bean there" Thanks for your time, its always apprecited :) ~SilverShalkin :rose:
-
Christian Graus wrote: and stop asking the same question over & over again. I knew that was comming :) Christian Graus wrote: If you want fast 2D graphics and more than one sound at once, you WILL use DirectX. I know that too. But will i use DirectX to build the engine? That was the question... "The engine to me is a map editor that puts your game together :)" I know that Direct Draw and Direct Sound and Music will make my game awesome, but, at the moment i am not make a game but the game engine. So,... Base question... Will i or will i not use DirectX to build my Engine? If not, then what should i use. "Engine, not game" But then, if i was to build my engine so that it would use DirectX, would i use DirectX with my engine? Oi,... Me confused, ill get it sooner or later... I also know about FlipCode but they are all in 3D stuff and stuff and they have no tutorials, there forum is half decent, yet no one responds to questions else you wait till the next day to get them. Ill try www.gamedev.net "i dont think ive bean there" Thanks for your time, its always apprecited :) ~SilverShalkin :rose:
SilverShalkin wrote: I know that too. But will i use DirectX to build the engine? That was the question... "The engine to me is a map editor that puts your game together " I know that Direct Draw and Direct Sound and Music will make my game awesome, but, at the moment i am not make a game but the game engine. You're writing an editor, not an engine. You won't need to use DirectX. You should use MFC for the reasons I stated. Christian The tragedy of cyberspace - that so much can travel so far, and yet mean so little. "I'm somewhat suspicious of STL though. My (test,experimental) program worked first time. Whats that all about??!?! - Jon Hulatt, 22/3/2002
-
SilverShalkin wrote: I know that too. But will i use DirectX to build the engine? That was the question... "The engine to me is a map editor that puts your game together " I know that Direct Draw and Direct Sound and Music will make my game awesome, but, at the moment i am not make a game but the game engine. You're writing an editor, not an engine. You won't need to use DirectX. You should use MFC for the reasons I stated. Christian The tragedy of cyberspace - that so much can travel so far, and yet mean so little. "I'm somewhat suspicious of STL though. My (test,experimental) program worked first time. Whats that all about??!?! - Jon Hulatt, 22/3/2002
Ok, thanks... I have a book and ill start studying. If i have any other questions on this little subject, i have 3 other forums to post it :) Thanks Again! ~SilverShalkin :rose:
-
Christian Graus wrote: and stop asking the same question over & over again. I knew that was comming :) Christian Graus wrote: If you want fast 2D graphics and more than one sound at once, you WILL use DirectX. I know that too. But will i use DirectX to build the engine? That was the question... "The engine to me is a map editor that puts your game together :)" I know that Direct Draw and Direct Sound and Music will make my game awesome, but, at the moment i am not make a game but the game engine. So,... Base question... Will i or will i not use DirectX to build my Engine? If not, then what should i use. "Engine, not game" But then, if i was to build my engine so that it would use DirectX, would i use DirectX with my engine? Oi,... Me confused, ill get it sooner or later... I also know about FlipCode but they are all in 3D stuff and stuff and they have no tutorials, there forum is half decent, yet no one responds to questions else you wait till the next day to get them. Ill try www.gamedev.net "i dont think ive bean there" Thanks for your time, its always apprecited :) ~SilverShalkin :rose:
SilverShalkin wrote: Will i or will i not use DirectX to build my Engine? If not, then what should i use. "Engine, not game" Will your 'Engine' need to display graphics, show animations or play sounds of any kind? If the answer is yes, then you will need to use DirectX. If your 'Engine' just needs to input data into a dialog box, then MFC will do the job fine. And just to confuse the issue a little more, it is possible to write a DirectX application using MFC. There are plenty of books out there that teach you how to do it. It's not easy and doesn't produce fast games but if you are just doing a map editor then it might be a way forward. Do a search on Amazon for books on writing games, they contain all the information you need. A google search might also help. Michael :-)