![]() Unity is vast, like Photoshop, and just like people use Photoshop for a vast array of things like photo editing, sketching, and wireframing, there's a million ways to use Unity. There's no such thing as outright "learning Unity". ![]() These are things you want to discover ahead of time during a game jam instead of while working on your dream project. For example, you'll base all of your enemy AI around Unity's NavMesh system, only to realize that there's a limitation of the NavMesh system that means you need to rewrite all of your enemies to use something else (like an A* pathing asset from the asset store). If you start a large game project before you learn how to use Unity properly, you'll do silly things that are hard to fix by the time you discover they're silly. The reason it's better to do game jams or lots of little throw-away projects is that decisions you make early on in the game making process will matter greatly later on. So, don't come into it thinking "I need to make my dream game, I'm going to start today and just add on to it as I learn". Each tutorial you watch should be important to you, and the best way to make sure it's important is to constantly be trying stuff on your own as you're watching them, either with hundreds of small personal projects or with game jams.Īlso, I really don't recommend having the "one big game project" that some people do when they're starting out. Otherwise, you're just watching tutorials and forgetting half of what you've learned each time. That's the learning strategy you want to employ: Try a thing on your own, do it badly, watch the relevant tutorial. So instead of watching a bunch of random tips about how to fix these issues before you've encountered them (and forgetting everything you've learned), you end up going out and watching specific tutorials that explain how to avoid the situations you've run into in the past. For instance, once you've worked with thousands of objects in your scene, you'll start to notice performance problems and trouble finding anything in the Hierarchy window. After game jam, return to your online Unity tutorials and see how much of a difference it made.Įssentially, when you've done things under pressure, you've gained an interest in learning all the various Unity things.Do things in bad ways during the game jam, leading to a crappy game.Panic because you're running out of time during the game jam and Google how to do everything.Reddit Logo created by /u/big-ish from /r/redditlogos! Long series.ĬSS created by Sean O'Dowd, Maintained and updated by Louis Hong /u/loolo78 Favors theory over implementation but leaves source in video description. Normally part of a series.Īlmost entirely shader tutorials. Lots of graphics/shader programming tutorials in addition to "normal" C# tutorials. ![]() ![]() Using Version Control with Unit圓d (Mercurial) Related SubredditsĬoncise tutorials. Unity Game Engine Syllabus (Getting Started Guide)ĥ0 Tips and Best Practices for Unity (2016 Edition) ![]() Lots of professionals hang out there.įreeNode IRC Chatroom Helpful Unit圓D Links Use the chat room if you're new to Unity or have a quick question. Please refer to our Wiki before posting! And be sure to flair your post appropriately. Remember to check out /r/unity2D for any 2D specific questions and conversation! A User Showcase of the Unity Game Engine. ![]()
0 Comments
Leave a Reply. |