• Content count

  • Joined

  • Last visited

Community Reputation

428 Neutral

About djtesh

  • Rank
  1. You need to replace the collision handling to use physics solvers instead of "stop all movement". Most collision detection code is just that - detection.   Here's what certain engines do:   Physics is handled on a separate thread / module. In order to obtain desirable results, movement solving is done over several iterations PER frame.   Since you're building using C++, I'd recommend looking into the free Chipmunk Physics C++ library. Alternatively you can write quasi-physics by following your own rules as mentioned.   I'm rusty in physics but you should be able to calculate angle of incidence (into the wall or another tank) based on movement vector of both objects. Since the wall is static it will work itself out. When two objects collide, a third party (collision handler with body A and body B) will decide the results. If both objects were tanks, you'll be happy that both can conserve momentum and "bounce" or "slide" correctly based on the same application of physics.   If you want to step it up - and your tanks are not all the same size, you can take weight and momentum into account.
  2. Great artwork!   If you really are just looking for a way to stitch your concept art into a static point and click adventure game, you might be able to get away without a programmer. Can you tell us if this is going to be a 2D game or 3D? Will the camera move?   Basically if it is really 2D, you can try an adventure builder or GameMaker. These tools will come ready to handle "triggers", touch zones - so you can react to player input and stitch together screens or levels.   If you want to do anything special like pick up items, show an inventory, have dialogue or character or camera movement, then it is likely you will need a programmer. These are staples of most adventure games, so you should decide now before you get too invested into a game engine or set of tools. Enlisting a programmer is easier if you are serious about your project and can show progress like this. If you decide to go this route, I might suggest using Unity, put together your levels, and then use their forums / marketplace to team up with someone who will help you get your game finished.   If you want REALLY high fidelity and you understand 3D modeling, animation and shaders at a AAA level, you could also try using the Unreal Engine. It is $19/month to use it commercially. You can make complete games using their system called Blueprint without any programming. (See their Flappy Bird and related demos).   Come back with some details and I can help you further.   Best of Luck!
  3. The way you are doing this right now, you are creating the pixels in System Memory (RAM). In most modern computers, the graphics card loads the textures into its own memory. Thus, you'll have to copy your buffer from one memory to another every frame in order to get your desired effect, which is very inefficient, but good enough for a one-off use.   A better approach, then, is to not create the array in System Memory but to do things directly on the graphics device. There are two approaches that I know of for this:   1. Use shaders. Use the vertex shader to draw a rectangle the size of the screen. Use the pixel shader to draw your random colors.   OR   2. Use OpenCL. OpenCL runs C / C++ programs on the GPU. You can integrate OpenCL into your graphics pipeline as well. There are tutorials out there for this - I'm not too familiar with how to do this myself.
  4. Although your question is not very specific, here are 3 popular methods that won't let you down:   1. JSON, with a parsing library available in most languages. JSON is easier to read and edit, smaller than XML and works with RESTful APIs and internet technologies all over the world now.   2. XML. XML is also easily consumed and parsed in most languages. It is older and somewhat clunkier, but it is still being used in many commercial game engines as a general data format.   3. Design a database using SQLite. This is a file based database format that can be easily consumed in C++ and most other languages. If you know SQL and relational database concepts, this is a powerful way to store and query your game data.   My opinion is that writing custom text file parsers is a waste of time compared to these options, unless you have to do something so extraordinary with it that it makes it impossible to use all of these methods.
  5. As far as I remember, the Visual Studio Installer project can be configured to include the installation of other components like the runtime library as part of the install. It won't embed the whole thing but rather download and install the latest from Microsoft's servers during the install process.   Look it up. If not, there's Inno setup. It is a powerful, script driven system that definitely handles pre-requisite installs.
  6. Hello there,   I have worked in both AAA and indie environments and different sizes of games. Just wanted to leave some random information here for you to consider:   Since Terraria renders and maintains thousands of terrain tiles per frame, performance will be an issue, and Python may or may not be fast enough to handle the computational aspect of it. For this particular case, I'd recommend something using C# or C++. If you don't know either language, you'll likely find C# to be much easier yet more capable (out of the box) than pure C++. C++ takes many years to master because the language leaves you to consider things that have been neatly "solved" for you in C#.   If you go with C#, you might want to consider MonoGame or XNA to help jumpstart your rendering and game systems. You could also use Unity Free. Building a game engine from scratch will take a lot more effort - and architectural level understanding of how game engines work. A lot of reading and experimentation..   MonoGame / XNA allows you to piece together your game and works more like a swiss-army-knife styled utility library. Unity is a full fledged engine that takes over all of the heavy lifting, allowing you to simply focus on gameplay prototyping.   And this is where the important question comes up. Do you want to make an awesome game now - or do you want to become a badass programmer? What is your ultimate goal with this project?   If your focus is to learn more, go with MonoGame / XNA or even write your own engine. However, if you want to make your game quickly and focus on bringing it to market sooner, then you may want to choose Unity instead.   C++ is used in high end AAA studios in several engines that are almost a decade old (or even older). The reason C++ is used is for raw power. Most of these engines use a scripting language like Python / Lua in order to allow designers and other scripters to flesh out the gameplay - things like missions, switches, triggers for sounds and particles, loading levels, spawning items and such. The really low level graphics, particles, physics and other subroutines are tucked away and maintained in C++ by "well paid" "badass" programmers who hardly work on the game. Their job is to manage and ensure optimum memory usage on consoles / PC, multi-threading, performance optimization, shader optimization and balancing tasks between the CPU and GPU - much closer to hardware level of concern - hardly anything to do with a particular game. Such a complex setup works well for larger studios as they can separate the concerns of each department in different layers.   When people say "real game developers use C++", they aren't giving you the full picture. Most indie developers should not need this level of sophistication. Building games of Mario / Galaga level of complexity on the studio setup is actually a huge waste of time and talent. It makes sense for games like Call of Duty - something that pushes the limits of visuals and technology with hundreds of people on the team. I've known many people who wanted to make a full-fledged FPS or RPG on their own - and these projects go on for years with very little progress. So don't let someone else dictate what programming language or tool you "must" use in order to be "cool".   Just some thoughts.
  7. I need help with some maths

    Seems like you are not normalizing correctly.   You want to move "r" units from "p" in a direction that points towards "t". Directions are always normalized (unit vectors), so that they make sense when moving any amount of units along them (even fractions).   Check that and try again.
  8. Unity Unity or C++?

    I agree with Nypyren's reply.   Also wanted to add that award winning games and studios are also using Unity for complete games. Think Monument Valley and Hearthstone.   Time is a resource. The quicker you can prototype your game ideas, the more likely you are to spend the time to polish them. C++ is great for truly learning how programming works at a deeper level, but you should decide what is more important - your programming ability or the product / game.
  9. Newbie Game Dever

    Welcome and good luck ahead!
  10. I think there are two basic approaches you can use consistently to achieve this.   Approach 1. If you are ok with using extern variables, then you can simply declare them in the header file and define their value once in some cpp file. These are usually better for debugging than defines.   Approach 2. If you must have your macros/defines as preprocessor directives, you can create two sets of header files. A set of "Private" header files that are only used during your library compilation but not available to external SDK users. This is tricky and requires more work but it works.
  11. Consider from the player's perspective, given your own game's design. What's the most beneficial thing to show and what's redundant? Also, which combination leads to the most "fun"? Sometimes, the absence of information can heighten the tension.   Think for a little while and I'm sure you'll get arrive at the answer. If you still aren't sure, let some people play it both ways and tell you.   There's no universal truth to such UI and game design.
  12. unity monthly subscription question?

    Sorry but the Unity3D subscription membership is for a minimum of 12 months.
  13. Can't solve problems without googling?

    Hello!   This is a very interesting conversation to have! I've been programming for over 10 years. I really enjoy it and the feeling of wanting to improve persists! Here are some things I've found:   #1) Most regular professional jobs are results oreinted. They really do not care if you've written the best search algorithm or the most optimized string parsing routine. You can get into trouble as you are bombarded with deadlines, and tasks cannot be consistently challenging. Here, it is very common to be an OK programmer and do well with a bit of politics. To do the really good stuff, you'll have to turn to #2. If you have a burning desire to do cutting edge things, steer your career away from jobs that don't need it.   #2) A lot of great programming achievements were started as pet projects / hobby projects. These are the projects that someone really cared about intensely, and found the time and energy to devote to something exceptional. Never stop making stuff on your own.   #3) There are a few exceptionally rare companies that try to build the very best libraries themselves, and then release them to the world. For example, Twitter with Bootstrap, Google with AngularJS and their plethora of tools and Apple with their various frameworks that they provide to App developers. You can make decent money if you find yourself at one of these coveted companies. Microsoft and Facebook have really really smart people too, and there may be many companies that could have exceptional teams. Finding these hidden gems can be difficult.   #4) Finish stuff. Today you have so many avenues to see if people care about what you made. App Stores, GitHub just to name a few. Let people play with or use the things you make. The art of finishing is lost on many (including myself for so many years). It is hard to learn the really valuable stuff that a real life use will teach if you can't finish your projects. Start small if you have to. Find passionate teammates before attempting massive stuff.   #5) If you have the time, take great open source projects and make them better. The world will thank you for it. I will thank you for it!   If you are not a naturally great problem solver - or if you don't know, the best path is to join a place with REALLY smart people. You'll see their tricks, their way of thinking and you will learn quickly.   Ok I'll stop here for now. Let's see what others have to say.   Best Regards, Mitesh
  14. I recommend Unity3D for what you want to do, as it can do PC, Mobile and Web with the same game scripts so you won't have to rewrite after that.   Polish, test and release your games. Then, sell it for Windows 8 & Surface RT, Windows Mobile, and Android. When you make some money from them (by selling them in the respective App Stores), invest in a Mac Mini and iPod Touch (cheapest entry into the Apple world) and you've got a full studio for all the platforms you want to hit. One of the best ways to score Apple gear for less is to look at the Apple Store online in the "Refurbished & Clearance" link. You'll save 20% or more.   Wish you the very best. Writing and selling multi-platform games can be very fulfilling :)