The UI Profiler & Frame Debugger

Loading...

From the course by Unity

Rapid Gameplay Prototyping

2 оценки

Unity

Rapid Gameplay Prototyping

2 оценки

Course 1 of 5 in the Specialization Unity Expert Gameplay Programmer Certification Preparation

Welcome to Rapid Gameplay Prototyping, the first course in Unity's Gameplay Programming Specialization! This course is exam preparation for Unity's Expert Gameplay Programmer Certification Exam. This course will challenge you with a series of realistic programming problems in Unity video-game projects, inspired by one or more of the topics covered in the Expert Gameplay Programmer Exam. Throughout this course, you will work on a 2D “infinite platformer” game project. This will help you practice prototyping core game play mechanics, including scripting GameObjects and their components, coordinating UI systems, and implementing UI scripting. You will also identify conflicts and implement solutions during the prototype stage. This is an advanced-level course, intended for industry game developers or very experienced Unity enthusiasts who are looking to “level-up” their gameplay programming and implementation strategies. To succeed in this courses, you should have at least 2-3 years of experience developing games with Unity. You should be familiar with the full-game lifecycle (working from early concept to launch), creating and working with Prefabs, understanding game asset and animation pipelines, and have some experience with Unity Services. You should also have advanced programming skills, particularly in the C# language.

From the lesson

UI Scripting

Your UI is ready to provide feedback, and for that it needs data and methods of translating that data into visuals that user can quickly absorb. From simple meters for health or time, to complex maps showing player progress or proximity, these elements need to run smoothly and accurately. If your game must be localized into multiple languages, you’ll have to plan and execute for that, too. This week you’ll delve into the scripting side of UI. You’ll hook up last week’s UI to your gameplay, and add new features derived from scene data. All this has to perform well, which will require a look at the UI Profiler to determine how to optimize per platform. For elements that require localization, you’ll use a script to determine which assets need to be replaced. When you’re done, your UI will give you real-time feedback on your gameplay.

The UI Profiler & Frame Debugger4:36

UI Optimizations1:56

Meet the Instructors

Unity Technologies
Dustin Carroll
Senior Technical Artist & Adjunct Instructor
Computing & Digital Media

An important part of getting any UI to work well is

to debug it and make sure that it's working optimally.

Thankfully, there's a bunch of tools Unity offers to help you along with this.

The first of these can be found under the Profiler.

If you go to Window, Profiler,

this brings up the Profiler.

Now, if you don't see the UI element right away, it might be at the bottom,

or if they're not there,

you can always add them by doing Add Profile and bring it up UI and UI Details.

I don't need any of the rest of this right now so I'm just going to get rid of these.

In fact, I want a nice view of my UI Profiler so I'm going to drag

my Inspector over here and put my Profiler over there.

Now, when I play the game,

we'll get some information coming in through here.

UI details is going to be fairly empty right now. That's fine.

I'm just going to go ahead and select one of these frames.

In fact, I'll select one of these larger ones here,

and then here, you get all the details as to how things are actually being batched.

You'll notice that under our canvas,

there are three different batches.

Now, if we scroll over here to the right or we just make these a little smaller,

we can see that each successive batch

gives a reason for why it did not batch with the previous.

In this instance, we just have different materials.

If you're able to reduce the number of materials that your UI is using,

you'll make your UI operate just that much better.

We have a fairly simple UI going here,

and there is a few different reasons that batching could be broken.

First of which is a non co-planar UI element,

meaning that a UI element that is not in the same rotation as the canvas.

This means that the game has to figure out how to

draw it in a 3D rather than 2D perspective.

The other reason is an injection of a new canvas group.

It's generally a good idea to avoid canvas groups where you can,

they tend to have a bit more overhead to them.

I've gone ahead and added a button to

our canvas just to show off something in the UI details that is useful.

You'll notice it's not a lot happening down here.

If I go ahead and click on that button though,

we get something called a marker.

That marker tells me exactly what was

clicked and what the button on click was called.

The other tool we have at our disposal is a frame debugger.

Now, this can apply to the game at large,

not just UI, but UI is an element of it.

If you go to Window, Frame Debugger,

just going to put that right there, if you enable it,

you're going to start gaining information as to how your game

is actually drawing everything that you see.

Now, under camera.render, we're going to get basically the entire game being constructed.

And there is another path for our render camera,

so that's not for free.

At the very bottom here,

we've got the UGUI rendering

and what this does is it will show you step-by-step how these things were drawn.

Notice that the very first draw call is for our radar background.

The rest, it comes in at the next draw call for our text,

and then the next three draw calls are for our button.

So, the buttons can have a bit more overhead than the regular item.

It depends on how you are rendering them,

the text is part of our button as well.

The button here is taking up three draw calls.

It's a little bit more expensive but we do have a different piece

of text on top of the button so this is to be expected.

Furthermore, on the right here,

you can see some of our shader properties giving us

an idea of what the shader is doing to make this thing work.

If you're running into render issues related to your UI,

go ahead and have a look at your Profiler with

the UI elements enabled or the Frame Debugger.

They'll probably give you a good idea as to what's breaking

your batches or what's causing a lot of extra draw calls.

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

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

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

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

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

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