02b Section 01 Notes
02b Section 01 Notes
In this video
Were excited because we see your improvement.
The more you put in, the more you get out.
Follow all the videos through.
Most importantly - have fun!
In this video
Get Unity downloading now, its big.
Challenge 1: Do a whole section alone.
Challenge 2: Large challenge videos.
Challenge 3: Mini-challenges.
In summary
Section notes are for reference, no action needed.
Please do at least the mini-challenges.
Assets are near the start of each section.
Post feedback against specific lecture.
Consider HD video, and Closed Captions (CC)
Installing Unity
In this video
Checking the version you already have installed.
If 4.x installed,update to v.4.6.3 (not Unity 5 yet).
If 5.x installed, install Unity v.4.6.3 as well.
Finding Unity v.4.6.3 in Unitys download archive*
Installing and registering Unity.
* http://unity3d.com/get-unity/download/archive
In this video
How Unity and Mono (or your IDE) relate.
Create, delete and rename scripts in Unity.
Edit your scripts in Mono.
Save your changes to disc in Mono.
Unity will then read / run the script for you.
In this video
Take a look around the editor.
You can use Angry bots, or any other project.
Dont worry its just an overview.
Well show you everything slowly.
Moving around
Youll want a 3-button mouse*
Middle button click allows you to move.
Try zooming and scrolling around.
Grey shade shows what would be lost if changed.
* http://magicprefs.com to enable on Mac Magic Mouse
MonoDevelop 101
*Thanks to Thelmo.
Setting-up MonoDevelop
Go into MonoDevelop Preferences.
Text Editor > Behaviour > Indentation > Automatic
Take a look at the keyboard shortcuts.
In this video
How to tell if your spirit is saved.
How to delete scripts (do this in Unity).
What files Unity saves and how to move them.
Saving projects and scenes in Unity.
In this video
A discussion of C#, UnityScript and Boo.
Why we chose to teach this course in C#.
Note Boo is phased-out in Unity 5.
Quack!
Assume Nothing!
Most bugs are due to incorrect
assumptions
List you assumptions before and after a
method is called
Prove your assumptions (copious amounts
of print() are called for)
You can write the assumptions down in the
code as comments, or better yet as tests
Lets do science!
Use the scientific method for Debugging
1. Make an hypothesis
2. Develop a testable prediction
3. Test the prediction
4. Repeat until tests concur
with hypothesis
Further Resources
Eric Lipperts great How to debug small programs
tinyurl.com/howto-debug
John Regehrs Scientific debugging:
tinyurl.com/scientific-debugging
Good admin
Mark your question as [Help] and [Solved] at the
beginning of the title
Use a clear and descriptive title
Use full sentences with correct grammar and
punctuation
The Secret
The effort spent asking a better question
solves the problem 75% of the time!
Further Resources
Stack Overflows How to ask a good question:
http://stackoverflow.com/help/how-to-ask
Jon Skeets Writing the perfect question:
http://tinyurl.com/stack-hints
Eric S. Raymonds How To Ask Questions The Smart Way:
https://tinyurl.com/smart-questions
Useful Resources