All language subtitles for 3. Optimising the settings

So that's now converted.

It's changed over to Android, and you can see that because obviously you get a little unity icon on

the Android element there.

And now just changing over to Android like that, if you already have, let's say, a project that you

built specifically for PC or console and you just change over to Android, although it will technically

now export and apk file, it doesn't mean it's optimized for Android.

It's not as easy as that.

You do have to do a lot of optimization for it to work effectively on either an Android mobile or an

iOS mobile.

If you think of phones, almost like building for a computer about 10 years ago.

All right.

You'll get an idea of the ability that mobile phones can vary in terms of how powerful they are.

Some of them can be extremely powerful, almost as powerful as a modern day PC.

Some of them can be not very powerful.

So depending on what you're aiming for, I would say try and make an app that kind of really works on

an older phone.

And you can guarantee it's going to work on pretty much all of the mobile devices.

OK, so I'm going to be showing you various optimization tricks and to actually get the mobile games

working perfectly on all mobile devices.

Now, every now and then, you might see like a little yellow message at the bottom.

Just click clear.

These are basically just they're either warnings or advice.

That's coming up.

OK, nothing to worry about.

All right.

So one of the first things, if we move over to our game top and just check your game, make sure you've

got a simulator option.

If you're working on an older version of unity, and this is not there.

This is really going to prohibit you from following this course correctly.

OK, so I would definitely recommend updating your version of unity.

The simulator allows you to actually simulate all sorts of different mobile devices directly inside

the unity.

She's great.

OK, so we got a ton of different devices that we can actually simulate on.

So you can get different devices.

We can even rotate these.

So we're looking at the landscape this way, and this is going to be so useful for us.

OK, so I'll choose something like Samsung Galaxy J7 to begin with.

I'm just going to go back to game.

One of the first things that we need to do is change a free aspect to a set resolution.

So I'm going to go with 12, 80 by 720 landscape.

The reason why I'm doing that and the higher the resolution, the more processor power is going to take.

And on the mobile device processor power is is the kind of thing that's going to control your frames

per second.

If you overload the processor, that's just going to limit your frames per second.

Now, if you think about it in the mobile device, it just doesn't have any kind of fans.

It doesn't have kind of the airflow that you get in the PC.

So it's going to get extremely hot.

And when he gets up, he's going to start to try and cool itself down.

And it does that by limiting or bottlenecking your performance.

So you're going to get lower frames per second by keeping our resolution relatively low.

We're not overloading the processor or the CPU.

Then if we go to edit and project settings, if we come down to quality, this is going to show us levels

of quality.

Well, on the mobile device, we really don't need the quality to be ultra OK.

We can actually get away with either high or medium.

And since the game, I'm going to be making is relatively cartoony.

OK.

I definitely don't need to go for Ultra.

So I can actually click on Medium.

I'm just going to uncheck all of these boxes below medium.

OK, now, because I'm an Android, it's basically going to work medium level quality that's going to

change all of these elements that you can see below here.

So that is optimized for a medium quality that's going to increase your frames per second.

Notice that there's no anti-aliasing.

So if you do notice a lot of jagged edges on your screen, probably just change this to something like

two times multi sampling and everything else is good shadows.

I'm going to keep shadows on at the moment simply for light making.

And then I'm going to come back to this later and switch this off.

And we're not going to be using any real time light in a mobile device.

All right.

Which is going to be so much more effective for the processor.

But we'll get into that a little bit later.

Now, the V Sync.

I want to change this from every vblank to don't sync at all.

So what the V Sync does, he basically waits until your processor is fully processed.

The latest frame, and this creates a bit of a delay.

So the processor has to do all of the work and then pass the command through to the graphics processor

to actually render the scene.

And if you switch off async, the processor only has to process part of the frame and then it passes

the commands to to the graphics processor.

And that begins to actually draw the frame even before the process is finished processing.

So it makes your frame rates a lot faster.

However, one of the issues with switching off, we think if you are very, very fast movement in any

kind of a device, it can lead to screen tearing.

This is where you have one frame rendered at the top in a second frame, render below, and then maybe

a third frame rendered at the bottom of the screen.

And you can see these visible tags between each frame.

I doubt we're going to see that on mobile.

It's not going to be moving that fast.

OK.

However, voicing the ability to switch it off only works on Android devices.

Don't have this option on iOS.

So the iOS phones should technically be slightly faster and slightly better anyway.

So they shouldn't have a problem with V Sync.

But for Mobile, for Android, I would definitely recommend switching this off.

OK.

So what we want to do now is come to the player section and we're going to come to the resolution and

presentation and make sure that you're on the Android tab.

And where we have our

default orientation instead of auto rotation, I definitely want it to be a landscape.

I think it's just landscape, right.

That means the game will only work in landscape mode.

So if you flip your mobile phone over, it's not just suddenly going to try and make it fit a portrait

mode.

It can only work in landscape mode.

Kate, native aspect ratio.

And yeah, let's keep that.

Basically, it will try to match the aspect ratio of the phone and everything else is good.

Yeah, OK, that's fine.

Then we're going to come down to the other settings I call space, we're going to keep on Gummo.

OK, scummers technically faster than the linear color space.

You do have an option between the two and gamma is much more effective for mobile phones.

Not all mobile phone support, linear cooler space anyway.

All phone support, gamma call space.

We do have a couple of graphics APIs running, so it's fine.

We'll keep those multithreaded rendering is good.

Now for scripting, when we come down here, we can see that our script backend is set to Muno now for

Android mobile devices.

We can actually change over to this aisle to see.

This is it takes longer to actually build your device, build your app, but it's going to run so much

faster on the mobile device.

This is because it automatically converts it into binary code.

So it's auto converted when it actually reaches the mobile phone with the mono.

It's it's actually passing it over in a certain language that the mobile device then that's to actually

convert as you're playing.

So it makes it a little bit slower.

And what this option looks like, it's only available in the Android devices and not in the Mac and

minimum API level at the moment.

I'm going all the way back to API level 19.

But if you want to limit the phone, let's say you only want the target like new with mobile phones.

You can obviously go with whichever version you want, but that's going to limit your audience.

Who can actually play them.

This is important.

For example, you know, you've got a game where it's very, very demanding.

You know, the older phones just aren't going to be able to support that.

So then you'll limit it to a certain operating system.

OK, but I know that this should work on almost every phone target API level is basically just going

to find the highest installed.

All right.

So it's not it's not going to limit your phone in any way.

And active impaneling, we're going to use the input manager old as opposed to new input system.

OK, but if you do have to if you do want to use the new input system, well, I would recommend is

choose in both in that case.

And yeah, everything else is good, so that's the kind of settings that we need and to set up ready

for our mobile devices.