Explore
For Enterprise
Join for Free
Log In

Гуманитарные науки и искусства
Бизнес
Компьютерные науки
Наука о данных
Информационные технологии
здоровье
Математика и логика
Личное развитие
Естественные и технические науки
Социальные науки
Изучение языков
Степени
Сертификаты

Полный обзор Coursera

Обзор
Поиск
Для организаций
Войти
Присоединиться бесплатно

Debugging a Unity Script in MonoDevelop

Loading...

Introduction to C# Programming and Unity

Система университетов штата Колорадо

4.8 (оценок: 442) | Зарегистрировано учащихся: 16K

Курс 1 из 5 — C# Programming for Unity Game Development Специализация

This course is all about starting to learn how to develop video games using the C# programming language and the Unity game engine on Windows or Mac. Why use C# and Unity instead of some other language and game engine? Well, C# is a really good language for learning how to program and then programming professionally. Also, the Unity game engine is very popular with indie game developers; Unity games were downloaded 16,000,000,000 times in 2016! Finally, C# is one of the programming languages you can use in the Unity environment. This course doesn't assume you have any previous programming experience. Don't worry if you've never written code before; we'll start at the very beginning and work our way up to building small games by the end of the course. Throughout the course you'll learn core programming concepts that apply to lots of programming languages, including C#, and you'll also learn how to apply those concepts when you develop games. Computer programming is really fun in general, and programming games is even better! Caution: Beginning (assuming no prior programming knowledge) is not the same as easy (not hard to do). Learning to program IS hard to do, especially since this course is essentially the first half of a freshman-level college course. Meeting the course challenges while you master the material will be rewarding to you, but doing that will require hard work and maybe even a few expletives along the way. Module 1: Write your first C# console application and Unity script and learn how we store data in our programs Module 2: Learn how we use classes and objects to implement our code Module 3: Learn the basics of Unity 2D games and discover how we make decisions in our code Module 4: Get and use player input in your Unity games Module 5: Complete final peer review and take "Final Exam" “Unity” is a trademark or registered trademark of Unity Technologies or its affiliates in the U.S. and elsewhere. This course is an independent work and is not sponsored by, authorized by, or affiliated with Unity Technologies or its affiliates

Просмотреть программу курса

Получаемые навыки

Video Game Development, C Sharp (C#) (Programming Language), Unity (User Interface), Game Programming

Рецензии

4.8 (оценок: 442)

5 stars
369 ratings
4 stars
57 ratings
3 stars
9 ratings
2 stars
3 ratings
1 star
4 ratings

MR

Apr 09, 2018

Fantastic course!\n\nDr. T creates the best learning curve by balancing perfectly the level of difficulty in their courses. Worth it even for intermediate C#/Unity programmers.

EJ

Apr 08, 2019

This is a great course for those who want to learn C# for Unity. Dr. T is very effective in his instructions plus the program exercises will make you learn C# in no time. :-)

Из урока

Unity 2D Basics and Selection

In this module, you'll learn some of the basic ideas behind using Unity to develop 2D games. You'll also learn how we can make decisions in our code.

Lesson Introduction0:48

The Unity Editor3:53

Sprites and Game Objects7:31

Unity's Component System3:57

Scripts as Components3:59

Debugging a Unity Script in MonoDevelop5:54

Debugging a Unity Script in Visual Studio2:52

2D Physics11:34

Colliders and Physics Materials, Part 16:49

Colliders and Physics Materials, Part 28:38

Преподаватели

Dr. Tim "Dr. T" Chamillard
Associate Professor

Текст видео

In this lecture we'll talk about debugging a Unity script using MonoDevelop.

So sad to say, sometimes your games will have bugs in them.

And the only way to fix those bugs is to debug, get rid of the bugs.

And so, that's what we're going to talk about today.

Before we actually go through the mechanics of doing that,

let's talk a little bit about how debugging works.

So here's how it works.

We find an error in our code,

a bug, somehow it's not behaving the way it's supposed to behave.

Before we go messing around in the debugger and

sort of watching how our program executes and so on,

we should form a hypothesis about what could cause this error.

Because especially once we have lots of code, sort of mucking about,

executing one instruction at a time is going to take a long time.

So you should form some idea

about what might be going wrong before you go try to find it.

So formulating a hypothesis.

Now I'll freely confess that sometimes as a programmer I don't do that.

I go sort of wander around in the debugger, but that's a stalling tactic.

It's getting me working on formulating that hypothesis in the background

while I do something else.

I mean, I suppose could go read a book or go for a run or something,

but it's doing something while I'm trying to form a hypothesis.

Once you form a hypothesis, you go and gather evidence.

And we actually can't prove hypotheses to be correct, but

let's not get technical about those kinds of hypotheses.

Once you sort of figure out what you think is going wrong,

then you use the debugger to try to discover if that is in fact the case.

And then, you sort of walk through the code,

and you look at values of variables and so on to see if your hypothesis was correct.

And you might discover it was and then you can fix the bug.

Or you might discover it wasn't, but that's okay too because you find

a different place where the problem is actually occurring.

So let's actually go to Unity and

MonoDevelop now to see how that debugging process works.

To debug our script, we need to open up both our project in Unity and

our script in MonoDevelop.

And in fact our first step is to do something in MonoDevelop,

so let's go there first.

So I've added a little extra temporary debugging code so

we can see how the debugger works in a little more detail.

One of the important tools we have when we debug is something called a breakpoint.

So if I click here, to the left of line 16, I get a little red circle and

that line gets highlighted.

And what that means is I have set a breakpoint at that line.

And what that means is when I run the code,

when it reaches this point, it will stop, it will break execution.

And then I can sort of look around at stuff here in the environment.

So we'll do that in a moment.

The way we start debugging, here in MonoDevelop,

is we go to that top menu bar and we select Run > Attach to Process.

And in this pop-up, there should only be one Unity Editor process.

If you see multiple Unity Editor processes,

you have multiple instances of Unity running.

So you should shut them all down and start over,

otherwise it's hard to pick the right one.

So just double-click it, so now we can go to the editor and start up the game.

We start the game as usual by clicking the start button.

And it takes a little longer to get started when the debugger is running.

And you'll see that it is highlighted, MonoDevelop down here in my taskbar, so

I'll click that and it has stopped here on this line.

And you can tell it is stopped here on this line because that little red circle

has an arrow in it, and the line is all marked with yellow.

Now one of the interesting things we can do with the debugger is we can look at

the values of variables as we go along.

So I'm going to actually step over or execute this line of code.

And then we'll take a look at the value of the position variable,

which right now is 000, whoops, I hovered over the variable.

To step over you can come up here and click Run > Step Over.

Or you can remember that it's F10 and just press F10, but I stepped over it.

The value of position here is still 000.

You can also look at position down here in the Locals pane.

Sometimes you might have Watch selected, like that.

You can click Locals to look at the variables.

And position is 000 down there as well.

I'm going to step over one more line of code,

which changes the x component of that vector 3 to 1.

So I'll F10 to step over that line of code and

you can see that position has changed to 1.0, 0.0, 0.0.

And then when we're all done, we can just say Run > Stop and then we're all done.

And we always need to go back to our Unity game and even though we stopped

debugging in MonoDevelop, we have not stopped running our Unity game.

So you just click the button again to stop running the game.

And that's how you can debug a Unity script in MonoDevelop.

To recap, today we talked a little bit about the process of debugging.

And we also talked about how specifically we fire up the debugger

using Unity and MonoDevelop.

Ознакомьтесь с нашим каталогом

Присоединяйтесь бесплатно и получайте персонализированные рекомендации, обновления и предложения.

Coursera делает лучшее в мире образование доступным каждому, предлагая онлайн-курсы от ведущих университетов и организаций.

© Coursera Inc., 2019 Все права защищены.

Загрузить из App Store

Загрузить в Google Play

Coursera
О проекте
Руководство
Карьера
Каталог
Сертификаты
Сертификаты MasterTrack™
Степени
Для организаций
Для правительственных организаций

Сообщество
Learners
Partners
Developers
Beta Testers
Translators

На связи
Блог
Facebook
LinkedIn
Twitter
Instagram
YouTube
Технический блог

Еще
Условия
Конфиденциальность
Помощь
Доступность
Пресса
Контакты
Справочник
Филиалы