demonkoryu

UML is good as a visualization tool as long as you don't try to apply the full "Rational Unified Process" which basically involves drawing the entire project beforehand using fancy UML diagrams, and then, when coding, realizing that all the pretty pictures were just a castle in the sky.

I think games that don't have godmode readily available (i.e. require some kind of trainer or cheat code) are the best compromise for the largest part of the gaming population, fun-wise, because with god-mode available, there is no challenge. There's constantly a rational voice in your head that tells you to just skip that hard part of the game so you can get on, instantly eliminating sense of accomplishment and motivation if you decide to use it. It's just a distraction, really, not much better than a WIN button.

 

The people who want god-mode can find a cheat or trainer easily enough if they want. The rest of us probably doesn't even want to be aware of the possibility to chicken out so readily.

You can embed a JRE in your program distribution, that way, end-users won't need to have Java installed.

Forget about your GPU(s). To restate what has been already said above, you need enough RAM and a fast hard disk (preferably SSD) so that you can compile/build and switch between IDE and game without having to wait for swap, and 4+ CPU cores to have your game, your IDE and your build tools smoothly running in parallel. For GPU, a mid-spec GPU is enough, since it already covers most high-end features (except that it is a little slower) and keeps you attentive to your target audience's hardware. If you're going to work on media such as 3D graphics, movies and so on, you'd profit from beefy GPU; although since you'll be programming, that's a moot point.

Another option is the Drupal CMS. It's easy enough to get going quickly. It can also be expanded later into any imaginable type of website (not only blog/community style like Wordpress).

Look into memory mapped files.

* Pro JavaScript

* Secrets of the JavaScript Ninja

Both by John Resig, but that's coincidence. The former begins with the only proper introduction to JS that I've ever read.

I taught everything myself the whole about C++ in about a week and have working on AAA titles about 1-2 months later then. That's ridiculous!

If you have completed a game with each engine, you wouldn't be asking this.

I want to know the language i need to learn

Most languages will do, if you know what you're doing.

and also the graphic thing. I need to know the sections i need to learn in the specific language and also in the graphics library. I need a clear answer for this.

You will need a good grasp on everything that's important. What that is, only experience can tell you.

The game which is created by my game engine should work in pc, mac, ps3, xbox.

Your engine doesn't create games, you create games. ;)
Try Unity, that's a popular cross-platform engine.

And guys i did not post anything because i am not started yet. I need some guide in it. For now i am learning so it would be more easier for me to learn if i know what to learn

Learn to make a game, using an existing engine. Then you can make a "game engine", because you know how to use one.

The problem with planning ahead is that only experience can give enough information to plan a software design properly. So, in a domain where you have good experience (i.e. many completed programs), you might plan ahead and be mostly right.

Myself, I find that minimal planning and then refactoring as I progress gives me the best results. Refactoring is especially valuable in retrospective to crystallize the real meaning of your code; in contrast to the mess that code can be when you just got it running for the first time. ;)

And read Pitfalls of Object Oriented Programming, while you're at it.

• Focus on results, i.e. finished programs. You'll ever only know why something is considered "good C++" if you did it wrongly in the first time.
• Again. Code to make stuff happen, and choose the simplest working way. ("Simplest" does in no way mean "sloppy".)
• As you work your way through real programming problems, you'll see when you need to learn more complex C++ stuff. Google for solutions and try to apply them to your work. (Some things look shiny (macros, template metaprogramming) but make your program worse if not properly used)
• http://yosefk.com/c++fqa/
• http://www.parashift.com/c++-faq-lite/

About 5 years ago, Tim Sweeney (creator of the Unreal Engine) was making a lot of noise about Haskell/Erlang (can't remember which) being the next big language for game development, but AFAIK, they're still sticking with procedural C++/UnrealScript.

A search for his name + Haskell or Erlang might turn up some of these presentations.

You mean this? He talked about Haskell's advantages but said that the syntax is not accessible enough for new programmers. It was essentially a call for a new, practical and easily accessible functional PL.

You need periods and capital letters much more urgently than pictures.