Cross Platform Menu Controller Support

Loading...

來自 Michigan State University 的課程

现代平台上的游戏开发

594 個評分

Michigan State University

现代平台上的游戏开发

594 個評分

課程 4（共 5 門，Specialization Game Design and Development）

The device or "platform" that a game is developed for and played on has a massive impact on the game development process. In this hands-on course you will explore how to develop a game for a variety of modern platforms, including Web, Windows, Mac OS X, iOS, and Android. While building a complete game, you will learn intermediate and advanced game development techniques in the Unity game engine. By the end of the course, you will understand how to develop, refine, package, and prepare your game for distribution on a variety of game platforms. Particular attention will be given to developing a 2D platformer game that supports multiple forms of input (keyboard/mouse, controller, and touch), works across multiple forms of output (screen size, screen resolution, sound), and performs well on a variety of computing devices.

從本節課中

Building Out the Game

Hi! This week we will finish our example game, bringing in some visual polish and UI, adding a game manager, and making sure our game controls work across multiple platforms. We will continue to introduce additional design and programming concepts along the way. And, at the end of this week, you will start the process of modifying the game and transforming it into your own creation! How exciting! As always, if you are having troubles with a concept, quiz, or technical issue with Unity or the project, you should post on the Discussion Forum to ask for help. Remember to be a good Coursera community member and help others out when you can. Go! Go! Go!

Out-of-Game Scenes7:08

The Main Menu6:50

Cross Platform Menu Controller Support3:42

Supporting Mobile Cross Platform Input11:34

與講師見面

Brian Winn
Associate Professor
Media and Information

[MUSIC]

Unity UI buttons such as our main menu are set up by default

to work with the keyboard, mouse, and touch input.

And they also work with game controllers, which is great,

because we don't want our players to have to put down their controller and

use the keyboard and mouse on the main menu scene if they're using a controller.

However, you may need to modify the input manager to support your game controller

across multiple platforms.

In this lecture we'll resolve that issue.

Our objectives will be to explore the EventSystem and modify the Input Manager.

So within the main menu scene here, notice the event system.

So of course this game object gets created whenever you create UI in your scene.

You should always keep it.

It's got a number of scripts attached here that

really provide the input mechanisms for our UI.

So one of the things to note is the stand alone input module.

So you can see there's a number of axes and buttons to find here.

So the horizontal and vertical axes is how we move through our menu, using horizontal

and vertical proper mappings back to whatever controls we're using.

You can see the Submit button.

That's how we actually select a menu item is Map to Submit.

And then there is also a touch input module

that basically provides the functionality for touch input.

Now the issue with controllers is that the Submit button isn't actually mapped

properly depending in your controller and depending on your platform.

So let me actually bring up the input manager.

So under Edit > Project > Input, of course we have our Input Manager here.

And let's look at Submit.

So Submit's actually in this list multiple times.

So the first time you can see Submit is tied to positive button returns.

So that's Return key on your keyboard and Button 0 is the alternate.

And the second Submit is tied to the Enter button on the keyboard.

Or the Space button on the keyboard.

So there's multiple ways to actually submit things on the keyboard.

And for Controller, Button 0 is the only mapping.

Now as you recall back earlier when we set up jumping, and

we looked at the button mappings for the XBox 360 controller,

the Unity 3D Wiki page, if I scroll down here.

Remember, Button 0 is tied to the a button on Windows and Linux but not on Mac.

It's, you know, Button 16 on the Mac.

So, what we could do is we could modify the Input Manager to include Button 16 as

another way to submit.

So, back in Unity all of these slots are unfortunately full, so

we've got the positive button and alternate positive in two spots.

We've got a variety of things.

We could take out one as an option and replace it, but

I wanna leave everything that's here because maybe people wanna use Return or

the Enter button on the keypad or something like that.

So what I would actually do is create a new axes, so here, when it says 18,

I'm gonna add a new one.

I'm gonna type 19.

And what it essentially does is it duplicates the last one

to the bottom here.

So I have two Cancels now, let me actually change this now to be a Submit.

And I'm gonna set the positive button to joy stick button 16,

and for alternate positive I'm just gonna remove that.

So, now that I have that set up, if I go ahead and test here on my Mac, and

with my controller, I can basically scroll down or scroll up using the directions.

And if I hit a, which is button 16, it should actually fire that off.

So I can do everything with the controller.

I don't have to take my hands off the controller and use the mouse or

use the keyboard to navigate my menus.

探索我們的目錄

免費加入並獲得個性化推薦、更新和優惠。

Coursera 致力於普及全世界最好的教育，它與全球一流大學和機構合作提供在線課程。

© 2018 Coursera Inc. 保留所有權利。

通過 App Store 下載

通過 Google Play 獲取