• Advertisement
Sign in to follow this  

Unity What do you need to learn before using a game engine?

This topic is 1650 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hey guys, I'm new here :)

So I was thinking about game programming and using a game engine. And everyone's been saying that you should first do some game programming and graphics programming before you actually use a game engine, so you know how things work on the programming side of things.

 

So my question is:
Basically, what is everything you need to learn in game programming before using a game engine (like Unity)?

I personally have been learning C# and XNA and I'm pretty new at it, and C# is used in Unity as a scripting language, and I always intended on transferring to Unity after learning everything I needed to know. So I really need to know everything I need to learn before going to Unity. Meanwhile I'll be learning that in XNA or SharpDX.

Feel free to post about general knowledge you need to have before using a game engine that's not language specific.

Cheers!

Share this post


Link to post
Share on other sites
Advertisement

I think knowing your languages well is the big thing. Game programming is just regular programming with some domain specific stuff mixed in.  

 

Otherwise I'd just say jump in with and go though. Learning stuff on your own isn't really like learning something in a class... there are no predefined "prerequisites", so you'll basically just be learning your prerequisites along the way. The main thing is just plowing through frustration.  

 

Personally I'd recommend against Unity if you're just starting out though. Don't get me wrong, I really really like Unity (I'm using it right now), but IMO it's more of an expert's tool than a beginners. YMMV though, try it out at least. 

Share this post


Link to post
Share on other sites

Well, I meant more in the line of, a list of topics that you need to have learned, before getting into a game engine. smile.gif
I know it's kind of a bad idea to get into a game engine, without any previous knowledge of some required topics that you absolutely have to know, otherwise you'd be lost.

And as a beginner and newbie in game programming, I really feel that finding the answers for a list of topics you have to know and a good list of tutorials and resources, has been daunting so far. But I'm finally getting around to it. smile.gif


Cheers!

Share this post


Link to post
Share on other sites

It depends...

 

Game engine is quite huge term. Your engine can allow just creating some 2D sprites, using some basic sounds, using basic movement mechanisms and scripted AI. Or your engine can allow for large open-world, dynamic AI (even learning through neural networks), advanced physics (cloth, fluid, soft bodies), perfect 3D sound tech.

 

But all in all I'd say that solid Linear algebra knowledge is one of the must-knows. Also basic data structures as you will use them everywhere. Maybe also some automata, from there I think you could create some basic and later more advanced games.

Share this post


Link to post
Share on other sites

Thanks, my main direction in school was math, so I've got that pretty much covered. However I really need a list of subjects for game programming and graphic programming that I need to learn. Maybe with a list accompanied with tutorials and resources too. :)

 

As you're telling me all the stuff that I know, but I don't know where to start.

Cheers!

Share this post


Link to post
Share on other sites

Thanks, my main direction in school was math, so I've got that pretty much covered. However I really need a list of subjects for game programming and graphic programming that I need to learn. Maybe with a list accompanied with tutorials and resources too. smile.png

 

As you're telling me all the stuff that I know, but I don't know where to start.

Cheers!

 

Here are tips I have learned when I finished coding Pong and did tons of work adding features to a simple arcade shooter game. Both games share similarites.

 

I assume you know how to program.

 

1) Figure out or just look and download an open source game code. Even a simple game code will teach you a lot. There are plenty to learn from their code. What you want to get out of it is understanding how they set up the game and build off from there!

2) Prior knowledge for figuring out where each game object should be: Understand how the coordinates of a graphics window or graphics canvas is laid out.

3) How to load a image and draw that image on a graphics context

4) how to clear and flip a buffer. understand why you would need this.

5) requesting focus to which object. think about how you would switch from a main menu to another menu and then start up the gameplay

5) How to set up the code to perform keyboard and mouse events. In Java, they are event listeners.

6) Understand what a game loop is. Any game needs this to keep the game running.

7) Basic AI involves the state of an object. Is the direction of the monster up or down. If it is up what should the monster do?

8) Some basic physics on kinematics and vector is needed. i.e how to calculate position in physics.

 

This is just a small set, there are plenty of things you will have questions with. But this should be a nice starting point for you.

 

It is important to figure out how to basic stuff like gameplay logic: basic AI and collision

 

Good luck.

Edited by warnexus

Share this post


Link to post
Share on other sites

I think the most useful game engine you create will use what you learn while developing your own games. Your best shot at getting something that fits in well with your games and has code you can really reuse is to refactor your engine out of your own projects. So, you need to learn about your own software.

Share this post


Link to post
Share on other sites

So just wanted to put an update on this thread, if any beginners are reading. smile.png

I've set up a step by step guide, for how to progress through game programming with C# and XNA.

 

EDIT: If you don't know C# but are looking to start. There are a lot of resources you can find. I personally find RB Whitaker stuff to be excellent for beginners.

http://rbwhitaker.wikidot.com/c-sharp-tutorials

 

To begin with XNA, the first thing you should do is follow this tutorial. It will set the fundamentals of 2D game programming for you. smile.png Try to add features to the game, and to modify it. You should then search for more resources until you feel comfortable with 2D game programming.
http://xbox.create.msdn.com/en-US/education/tutorial/2dgame/getting_started

 

XNA adventures from SixOfEleven is also a great place to learn 2D game programming. He has a series of XNA tutorials for making a whole RPG!
http://xnagpa.net/xna4tutorials.php

 

After learning 2D game programming, and when you think you're ready to move on to 3D. Here are some essential things you should read.
http://blogs.msdn.com/b/davrous/archive/2013/06/13/tutorial-series-learning-how-to-write-a-3d-soft-engine-from-scratch-in-c-typescript-or-javascript.aspx
In the prerequisites section, there are great links which will explain how 3D space works, and how 3D programming is done, and if you want you can follow along with the tutorials.

 

Next, you should definitely check out RB Whitaker's site. It will help you build up your 2D programming knowledge, you'll learn how to make a particle engine, and how to expand the content pipeline!, and it has great tutorials about implementing a 3D model and animating it. And it also has great tutorials for HLSL, when you think you're ready for them.
http://rbwhitaker.wikidot.com/xna-tutorials

 

What I'm currently doing, is learning 3D graphics programming on BBeck's site. Which set's the fundamentals of 3D game programming. These tutorials for me, are like the first 2D tutorials I did, and is making me greatly understand how 3D games work.
http://virtuallyprogramming.com
Check out the fundamentals section, and after that head straight to the Tutorials section, do the Holodeck tutorial and experiment with it as you did with your 2D games. You'll learn A LOT from these tutorials, and you'll start understanding how the 3D system works. Afterwards continue with the rest of the tutorials. smile.png

 

That's how far I am, and I'm learning more every day, until I feel confident and ready to use Unity as a game engine.

 

Have fun in your game development adventures!

Edited by traxix

Share this post


Link to post
Share on other sites

Honestly the best way to learn is to -do-.

 

Tutorials are deceptive, people read a lot of tutorials and think they suddenly can make a massive game but that's not really how it works, I've read thousands of tutorials probably and quite a few books and the knowledge they give isn't nearly as useful as trying it yourself.

 

Tutorials are useful, yes, but going from pong to half life in a week will leave you probably unable to even make pong by yourself without copying someone's code. The hard part of coding isn't copying code, code is just text. The important thing is to learn how to decode the problem at hand and how to create a way to solve it.

 

That's the difference between you and the guy writing the tutorial. In most cases he did all the work for you and you just followed along, you weren't forced to create your own solution and teach yourself how to figure out the problem.

 

My advice would be to read how to use something as a tool, then follow it up with practice. Just read a tutorial on making pong with SDL? Well now go make your own version, make it better. Or make a similar difficulty game that is different. These are the things that stick game dev as a process in your head.

 

Personally I think writing my own improved version of Pong that I polished to what I would consider a not embarassing level taught me more about making a game than many hours reading books did. Imagine how good you'll be making a couple dozen games like that!

Share this post


Link to post
Share on other sites

Yeah, I totally know what you're saying, I forgot to mention in my post that you should practice after following tutorials.

But yeah, copying code won't get you anywhere, after doing a tutorial, one should always try to make something from scratch.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By GytisDev
      Hello,
      without going into any details I am looking for any articles or blogs or advice about city building and RTS games in general. I tried to search for these on my own, but would like to see your input also. I want to make a very simple version of a game like Banished or Kingdoms and Castles,  where I would be able to place like two types of buildings, make farms and cut trees for resources while controlling a single worker. I have some problem understanding how these games works in the back-end: how various data can be stored about the map and objects, how grids works, implementing work system (like a little cube (human) walks to a tree and cuts it) and so on. I am also pretty confident in my programming capabilities for such a game. Sorry if I make any mistakes, English is not my native language.
      Thank you in advance.
    • By Ovicior
      Hey,
      So I'm currently working on a rogue-like top-down game that features melee combat. Getting basic weapon stats like power, weight, and range is not a problem. I am, however, having a problem with coming up with a flexible and dynamic system to allow me to quickly create unique effects for the weapons. I want to essentially create a sort of API that is called when appropriate and gives whatever information is necessary (For example, I could opt to use methods called OnPlayerHit() or IfPlayerBleeding() to implement behavior for each weapon). The issue is, I've never actually made a system as flexible as this.
      My current idea is to make a base abstract weapon class, and then have calls to all the methods when appropriate in there (OnPlayerHit() would be called whenever the player's health is subtracted from, for example). This would involve creating a sub-class for every weapon type and overriding each method to make sure the behavior works appropriately. This does not feel very efficient or clean at all. I was thinking of using interfaces to allow for the implementation of whatever "event" is needed (such as having an interface for OnPlayerAttack(), which would force the creation of a method that is called whenever the player attacks something).
       
      Here's a couple unique weapon ideas I have:
      Explosion sword: Create explosion in attack direction.
      Cold sword: Chance to freeze enemies when they are hit.
      Electric sword: On attack, electricity chains damage to nearby enemies.
       
      I'm basically trying to create a sort of API that'll allow me to easily inherit from a base weapon class and add additional behaviors somehow. One thing to know is that I'm on Unity, and swapping the weapon object's weapon component whenever the weapon changes is not at all a good idea. I need some way to contain all this varying data in one Unity component that can contain a Weapon field to hold all this data. Any ideas?
       
      I'm currently considering having a WeaponController class that can contain a Weapon class, which calls all the methods I use to create unique effects in the weapon (Such as OnPlayerAttack()) when appropriate.
    • By Vu Chi Thien
      Hi fellow game devs,
      First, I would like to apologize for the wall of text.
      As you may notice I have been digging in vehicle simulation for some times now through my clutch question posts. And thanks to the generous help of you guys, especially @CombatWombat I have finished my clutch model (Really CombatWombat you deserve much more than a post upvote, I would buy you a drink if I could ha ha). 
      Now the final piece in my vehicle physic model is the differential. For now I have an open-differential model working quite well by just outputting torque 50-50 to left and right wheel. Now I would like to implement a Limited Slip Differential. I have very limited knowledge about LSD, and what I know about LSD is through readings on racer.nl documentation, watching Youtube videos, and playing around with games like Assetto Corsa and Project Cars. So this is what I understand so far:
      - The LSD acts like an open-diff when there is no torque from engine applied to the input shaft of the diff. However, in clutch-type LSD there is still an amount of binding between the left and right wheel due to preload spring.
      - When there is torque to the input shaft (on power and off power in 2 ways LSD), in ramp LSD, the ramp will push the clutch patch together, creating binding force. The amount of binding force depends on the amount of clutch patch and ramp angle, so the diff will not completely locked up and there is still difference in wheel speed between left and right wheel, but when the locking force is enough the diff will lock.
      - There also something I'm not sure is the amount of torque ratio based on road resistance torque (rolling resistance I guess)., but since I cannot extract rolling resistance from the tire model I'm using (Unity wheelCollider), I think I would not use this approach. Instead I'm going to use the speed difference in left and right wheel, similar to torsen diff. Below is my rough model with the clutch type LSD:
      speedDiff = leftWheelSpeed - rightWheelSpeed; //torque to differential input shaft. //first treat the diff as an open diff with equal torque to both wheels inputTorque = gearBoxTorque * 0.5f; //then modify torque to each wheel based on wheel speed difference //the difference in torque depends on speed difference, throttleInput (on/off power) //amount of locking force wanted at different amount of speed difference, //and preload force //torque to left wheel leftWheelTorque = inputTorque - (speedDiff * preLoadForce + lockingForce * throttleInput); //torque to right wheel rightWheelTorque = inputTorque + (speedDiff * preLoadForce + lockingForce * throttleInput); I'm putting throttle input in because from what I've read the amount of locking also depends on the amount of throttle input (harder throttle -> higher  torque input -> stronger locking). The model is nowhere near good, so please jump in and correct me.
      Also I have a few questions:
      - In torsen/geared LSD, is it correct that the diff actually never lock but only split torque based on bias ratio, which also based on speed difference between wheels? And does the bias only happen when the speed difference reaches the ratio (say 2:1 or 3:1) and below that it will act like an open diff, which basically like an open diff with an if statement to switch state?
      - Is it correct that the amount of locking force in clutch LSD depends on amount of input torque? If so, what is the threshold of the input torque to "activate" the diff (start splitting torque)? How can I get the amount of torque bias ratio (in wheelTorque = inputTorque * biasRatio) based on the speed difference or rolling resistance at wheel?
      - Is the speed at the input shaft of the diff always equals to the average speed of 2 wheels ie (left + right) / 2?
      Please help me out with this. I haven't found any topic about this yet on gamedev, and this is my final piece of the puzzle. Thank you guys very very much.
    • By Estra
      Memory Trees is a PC game and Life+Farming simulation game. Harvest Moon and Rune Factory , the game will be quite big. I believe that this will take a long time to finish
      Looking for
      Programmer
      1 experience using Unity/C++
      2 have a portfolio of Programmer
      3 like RPG game ( Rune rune factory / zelda series / FF series )
      4 Have responsibility + Time Management
      and friendly easy working with others Programmer willing to use Skype for communication with team please E-mail me if you're interested
      Split %: Revenue share. We can discuss. Fully Funded servers and contents
      and friendly easy working with others willing to use Skype for communication with team please E-mail me if you're interested
      we can talk more detail in Estherfanworld@gmail.com Don't comment here
      Thank you so much for reading
      More about our game
      Memory Trees : forget me not

      Thank you so much for reading
      Ps.Please make sure that you have unity skill and Have responsibility + Time Management,
      because If not it will waste time not one but both of us
       

  • Advertisement