Member Avatar for vandenzergen

Hello everyone, I really want to know what should I do first in making games using c++. We all know that c++ is the most widely used programming language in making games. But, there is still things which are not clear to me as of now.

I'm still a newbie and I know that c++ is not the only programming language that you will use in making games, there are still another software that you might use to make that dream possible.

Please, everyone I really wanted to know... please, I know all of you are far more knowledgeable than myself. I know you've got answers in there...:?:

  • 5 Contributors
  • 8 Replies
  • 126 Views
  • 4 Weeks Discussion Span
  • Latest Post Latest Post by vandenzergen

Dani AI

Generated

Thread starter already has the right foundation (loops, conditionals, functions). Replies from , , and pointed toward two sound principles: keep strengthening programming fundamentals, and avoid rebuilding everything from scratch. The paragraphs below turn those principles into a practical, modern checklist and a small roadmap that fills gaps not covered in the replies.

Important technical areas to add next: modern C++ idioms (RAII, smart pointers, move semantics, the standard library), build/toolchain familiarity (compilers, CMake, linker flags), version control, and basic debugging/profiling workflows (memory sanitizers, debuggers, profilers). Game-specific fundamentals include a deterministic game loop (fixed timestep and delta-time handling), basic linear algebra (vectors, matrices, transforms), resource/asset management, simple collision detection and spatial partitioning, and separation of concerns between input, update, and render.

A practical progression that avoids scope creep: keep projects tiny and iterative. Set up source control and a minimal project skeleton, then implement a bare main loop that handles input, updates state, and renders placeholders. Replace placeholders in small steps: sprite or mesh rendering, asset loading, audio, simple AI, collision and physics, then profiling and polish. Frequent small commits, small testable chunks of game logic, and profiling before ambitious optimizations prevent common pitfalls.

Tool selection should match goals: lightweight libraries are excellent for learning internals; higher-level engines speed up prototyping; full-featured engines suit larger teams or commercial goals. Study a few small open-source engines to learn architecture, keep milestones realistic (multiplayer, advanced physics and networking are separate specialties), and focus early effort on shipping playable prototypes. This approach builds transferable skills and avoids the frustration of unfinished large projects.

Recommended Answers

All 8 Replies

Member Avatar for Lerner

You start with a dream and go from there. Some people prefer to jump off the high dive into deep water and learn how to swim or die trying. Others take the more sensible route and start from the beginning before getting in over their heads. I'd suggest the latter route. If you aren't familiar with programming at all learn how to handle the console with loops, the common containers and algorithms, etc. Then you can branch out to graphics using whichever graphics program you want: OpenGL, DirectX, whatever. If you have the knowledge base behind the graphics programs then you don't have to learn the background information at the same time you learn the graphics algorithms, etc.

Member Avatar for MosaicFuneral

What's the question???

Do you even know how to program in C++? That would be the first step towards doing anything.

Member Avatar for vandenzergen

I've studied c++ basics, like looping, conditioning, making functions and function calling and other things(basics) and I've solve a couple of mind twisting problems and I've gladly made it and have arranged my logic towards programming but there are still things lacking inside, many things lacked.

I also wondered how to make a front end programs, whacha call that? middle end? is it? Because I think that's also a part of creating games... If you could just help me... but anyway, I really thank you all for replying...

Member Avatar for MosaicFuneral

Well if you know basics, then you could try out SDKs like SDL, Allegro, whatever, or try looking for game engines that have things like renders, scene loaders, event handling and such already made so you can spend more time on your games actual development.

Member Avatar for vandenzergen

I thank you... thanks for the valuable information... I hope we could share more information in the future... constantly...

Member Avatar for minas1

Try darkGDK, it's free and very easy to use. Google it.

Member Avatar for jbennet

Yeah, dont dive right in with 3d games. Space invaders / asteroids is a very challenging product but a good one to get started with. You any good at maths?

Member Avatar for vandenzergen

Thanks everyone...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.