Learn Unity for 2D Game Development 无水印pdf.pdf

发布时间：2022-05-29 发布人：admin 分类：说明书资料大小：11.10M 资料格式：pdf 举报版权申诉

u011433684-10002470-4744302542858950076.pdf-第1页.png

第1页 / 共306页

u011433684-10002470-4744302542858950076.pdf-第2页.png

第2页 / 共306页

u011433684-10002470-4744302542858950076.pdf-第3页.png

第3页 / 共306页

u011433684-10002470-4744302542858950076.pdf-第4页.png

第4页 / 共306页

u011433684-10002470-4744302542858950076.pdf-第5页.png

第5页 / 共306页

u011433684-10002470-4744302542858950076.pdf-第6页.png

第6页 / 共306页

u011433684-10002470-4744302542858950076.pdf-第7页.png

第7页 / 共306页

u011433684-10002470-4744302542858950076.pdf-第8页.png

第8页 / 共306页

Cover

Contents at a Glance

Contents

About the Author

About the Technical Reviewer

Acknowledgments

Chapter 1: Unity Basics for 2D Games

Unity Projects, Assets, and Scenes

Project Wizard and Project Panel

Assets and Project Files

Scenes

Navigating Scenes and Viewports

GameObjects, Transforms, and Components

Cameras

Meshes and Geometry

Scripting and the Unity API

MonoDevelop

Components

Performance, Profiling, and the Stats Panel

The Profiler

The Stats Panel

Editor Add-Ons

Unity Interface Configuration

Summary

Chapter 2: Materials and Textures

Using Materials and Textures

Getting Started with Materials

Mesh Renderers

Shaders

Working with Textures

Materials for 2D Games

Method 1: Use White Ambient Light

Method 2: Use Light-Immune Shaders

Creating Textures

Rule #1: Power-2 Dimensions

Rule #2: Retain Quality

Rule #3: Expand Alpha Channels for Transparency

Creating Alpha Textures in Adobe Photoshop

Step 1. Separate Foreground From Background

Step 2. Duplicate and Defringe

Step 3. Expand Edges

Step 4. Merging and Alpha Channels

Creating Alpha Textures in GIMP

Importing Textures into Unity

Importing an Alpha Texture into Unity

Step 1. Import Alpha Texture

Step 2. Create Alpha Compliant Material

Step 3. Create a Textured Quad

Summary

Chapter 3: Quick 2D Workflow

Getting Started at Making “2D Alien Invasion”

Adding the Player and Enemies to the Scene

Implementing Player Movement

Implementing Player Weapons with Prefabs

Creating an Ammo Prefab Object

Implementing the Ammo Trajectory

Creating the Prefab Ammo Object

Defining the Cannon Point

Coding the Firing of Ammo

Implementing Moving Enemies and Collision

The EnemyController.cs Script

Setting the BoxCollider as a Trigger Volume

Adding a RigidBody Component

Adding a Level Background

Moving Forward and Project Limitations

Summary

Chapter 4: Customizing the Editor with Editor Classes

Editor Classes

Getting Started with Batch Rename

BatchRename.cs

Creating a Folder for Editor Extensions

Adding Batch Rename to the Application Menu

The CreateWizard Function

Testing the Batch Rename Menu Option

Reading Object Selections in the Scene

Making Use of Selection in BatchRename.cs

Testing Object Selections in Scene

Adding User Input to the Batch Rename Window

Completing the Batch Rename Feature

Summary

Chapter 5: Procedural Geometry and Textured Quads

Getting Started with the CreateQuad Feature

Setting the Quad’s Anchor Point

Specifying the Asset Path

Generating the Quad Mesh

Step 1—Create Vertices

Step 2—Create Quad as an Asset

Step 3—Instantiate Quad in Scene

Testing the Quad Mesh Generator

Summary

Chapter 6: Generating Atlas Textures

Getting Started with Atlas Textures

Configuring Texture Inputs

Atlas Textures and UVs

Generating an Atlas – Step 1: Optimizing Texture Inputs

Generating an Atlas – Step 2: Atlas Generation

Generating an Atlas – Step 3: Saving the Atlas Prefab

Testing the Atlas Texture

Summary

Chapter 7: UVs and Animation

Creating a Dockable Editor

Starting an Editor GUI — Selecting an Atlas

UV Editor—Adding an Input for the Atlas Prefab

Continuing with the GUI—Selecting a Texture

UVs and Manual Mode

Editing Mesh UVs

Putting It All Together—Finishing the UV Editor

Flipbook Animation

Summary

Chapter 8: Cameras and Pixel Perfection

Perspective versus Orthographic Cameras

World Units and Pixels

Position Objects

Field of View

Camera Size

Pixel Positioning

Pixel Perfection

Other Useful Camera Tricks

Depth

Advanced Depth

Assign Objects to Layers

Clearing the Depth Buffer

Summary

Chapter 9: Input for 2D Games

Detecting Mouse Clicks on Objects Automatically

Detecting Mouse Clicks on Objects Manually

Coding a Mouse Cursor

Working with Keyboard Input

Virtual Axes and Buttons—Input Abstraction

Mobile Input—Android, iOS, and Windows Phone

Detecting Touch Events on Mobiles

Mapping Touches to Mouse Input

Conditional Code Compilation

Summary

Chapter 10: Getting Started with a 2D Game

Game Design—Card Matching

Getting Started with the Game

Importing Assets

Generating an Atlas Texture

Generating Card and Cursor Quads

Assigning Materials and UVs

Camera and Resolution

Configuring the Scene—Setting Up the Cards

Setting Card Properties

Positioning and Arranging the Cards

Positioning and Arranging the Cards—Starting

Positioning and Arranging the Cards—Completing

The Game Manager

Shuffling the Cards

Handling User Input

Turn Management

Summary

Chapter 11: Completing the 2D Card Game

Networking in Unity — Getting Started

Establishing a Server

Establishing a Client

Testing Networked Functionality

Network Views

Making an Authoritative Server

Using RPCs

RPCs from Client to Server

Summary

Chapter 12: Optimization

Optimization—What Is It?

Tip #1—Minimize Vertex Count

Tip #2—Minimize Materials

Tip #3—Minimize UV Seams

Tip #4—Recycle Texture Space by Overlapping UVs

Tip #5—Use Per-Platform Texture Settings

Tip #6—Cache Components and Objects

Tip #7—Avoid Using Update

Tip #8—Minimize Colliders

Tip #9—Avoid OnGUI and the GUI class

Tip #10—Use Object Pooling

Tip #11—Use Static Batching

Tip #12—Utilize Skyboxes

Tip #13—Avoid Dynamic Lights and Shadows

Tip #14—Bake It; Don’t Simulate It

Summary

Chapter 13: Wrapping Things Up

GUIs and Resolution

Tiles and Tile-sets

Atlas Textures

Fonts

Unity Alternatives

Engines

Libraries and APIs

Asset Creation

Image Editing Software

Vector Graphic Software

2D Animation Software

Summary

Index

For your convenience Apress has placed some of the front matter material after the index. Please use the Bookmarks and Contents at a Glance links to access them. www.it-ebooks.info

Contents at a Glance About the Author ��xiii About the Technical Reviewer �� xv Acknowledgments �� xvii Introduction �� xix ■ Chapter 1: Unity Basics for 2D Games ��1 ■ Chapter 2: Materials and Textures ��27 ■ Chapter 3: Quick 2D Workflow ��57 ■ Chapter 4: Customizing the Editor with Editor Classes ��85 ■ Chapter 5: Procedural Geometry and Textured Quads ��101 ■ Chapter 6: Generating Atlas Textures ��121 ■ Chapter 7: UVs and Animation ��139 ■ Chapter 8: Cameras and Pixel Perfection ��163 ■ Chapter 9: Input for 2D Games ��189 ■ Chapter 10: Getting Started with a 2D Game ��213 www.it-ebooks.info iii

Contents at a Glance iv ■ Chapter 11: Completing the 2D Card Game ��241 ■ Chapter 12: Optimization ��259 ■ Chapter 13: Wrapping Things Up ��273 Index ��281 www.it-ebooks.info

Introduction If you log on to any online or mobile marketplace for games and browse the titles offered today, it’s likely that the majority of games you see will be 2D and not 3D. If you think back over the relatively short history of video games, or if you listen to industry veterans talking about their inspirations and favorite games, it’s likely that the titles most mentioned are in the 2D style. Frequently listed titles in these video game reminiscences include: Pacman, Sonic the Hedgehog, Super Mario Brothers, Tetris, Lemmings, Arkanoid, Bejewelled, Angry Birds, Plants vs Zombies, Minesweeper, Civilization, Donkey Kong, and Sim City. Despite the manifold differences between all these landmark games both new and old, they all share the common ingredient of 2D-ness; of having their graphics presented in a very specific way that doesn’t rely on three-dimensional space. In short, the 2D style represents some of the most well-known titles in video games history, and it is also a style that is alive and well today. 2D games are not simply stuck in history. They are not a thing of the past; a phenomena that has been and is no longer relevant to the demands of contemporary gamers. Rather, these games represent a significant and lucrative segment of the video game market. Often has been the occasion when this or that learned person has predicted the demise of 2D games, and yet despite all such predictions 2D games have not gone away. This resilience and strength is due primarily to their general popularity, charm, and stylistic simplicity. 2D imparts a classical and timeless feel to games that is technically difficult to replicate by alternative means. For this reason, gamers keep coming back to the 2D style and find within it new ways of enjoying games and experiencing richness. 2D games today play an especially prominent role in two large market areas, and for different reasons. These markets are the casual game market and the so-called “indie games market.” In the casual games market, including games such as Mystery Case Files and Bejewelled, the 2D style is deployed to add an accessible “pick up and play” feel that does not require the user to learn any complex control systems or to concern themselves with moving a camera in 3D space. The Indie Games market, including games such as Retro City Rampage and Super Meat Boy, have used the 2D style to create a retro or old school feel that is popular to a general audience. Whatever your reasons for wanting to make 2D games, 2D games offer a positive and promising future for game developers willing to embrace them with both hands and a with a can-do frame of mind. 2D provides a means of creating games that differ from the norm and from the mainstream, and for creating very distinctive flavors that all have a special kind of classical vibe. This book can help you get started with confidence on that road to making successful 2D games. There are many routes leading to that destination. Some are longer than others, and some are smoother than others. xix www.it-ebooks.info

Introduction xx Some involve the use of many tools and some involve the use of only a few. This book and the method presented here involve the use of the Unity Engine, and the pathway I discuss is intended to be a smooth and reliable one that will have relevance for most 2D games conceivable. What Is This Book About? This book is first and foremost a practical guide to making 2D games using the Unity Engine. That statement however, while informative, requires further clarification. First, the book is practical. This means most of the chapters are hands-on and project-based, as opposed to theoretical and abstract. They require you to be seated at the computer with the tools installed, and to follow along with me, step by step, as I do things. Practical does not mean however that I offer no explanations or detailed discussions about what is happening, and nor does it mean I simply expect you to repeat what I do verbatim in parrot-fashion. I do explore deeper theories, concepts, and ideas. But these are all presented around practical and real-world projects, which are the main focus, so that you can see how these ideas relate to game development in the field. The benefit of this is that you get to learn the theory and practice at the same time. You don’t only understand what it is happening and why, but you can apply that understanding to your own games. Second, this book is about 2D (two-dimensional) games. It is not about 3D or 2.5D games, or even about 4D games! But what does that really amount to in practice? What does it really mean to say 2D? After all, if every game is ultimately shown to the gamer on a flat, plane-like surface called a monitor, then isn’t every game really 2D? Surely, the only truly 3D game is one shown as a holographic image or in some kind of virtual reality helmet as seen in cyberpunk movies? Well; that is true in the strictest sense possible. But 2D is used here in this book, and generally in the games industry, in only a conventional and relative sense. It refers to any video game whose graphics and gameplay mechanics do not use 3D space. It refers to games whose worlds exist on a mathematical plane with an X axis and a Y axis, but not a Z axis. In a 2D game, characters typically move up and down and left and right, but they do not move closer to and further from the camera. In a 2D game, the gamer cannot rotate the camera freely; they cannot look around in all dimensions to see objects and things from different angles and perspectives, as they can in a first person shooter game. What makes a game 2D is largely about the limitations and restrictions it places on gamers and developers: the third dimension of space (depth) is off limits so to speak. There are, as we shall see, exceptions and caveats to this general rule, but the basic idea holds that 2D games are called 2D because objects in those games live on a 2D plane. Third, this book explains how to make 2D games using the Unity Engine specifically, as opposed to other viable tools such as GameMaker Studio or Construct 2 or Stencyl, among others. The latest version of Unity at the time of writing this book is version 4, but what is written here will most likely hold true for many later versions to come. The Unity Engine is sometimes informally named Unity 3D, and the “3D” part of the title reflects the main focus of the Unity Engine and the types of games it is typically used to make. Unity is primarily geared toward 3D games. It offers light-mapping tools, real-time lighting, particle systems, 3D coordinate spaces and more—all these are concepts associated with 3D and 3D games. For this reason, developing 2D games in Unity poses some challenges and hurdles that are not to be found when developing 2D games in many of the competing tools. This is because Unity was not designed primarily with 2D games in mind. But despite this, Unity is an attractive tool for 2D game development because it offers deployment to many popular gaming platforms and also the ability for developers to integrate many of its 3D features into their 2D games to make them look and feel even better. www.it-ebooks.info

Introduction xxi In short, then this book details not only how to make 2D games, but how to make them in Unity while overcoming the hurdles we will face by trying to use a 3D engine to make 2D games. Further, it also explores how to optimize our games and assets so they can perform better on mobile devices. Not better in the sense of performing faster on mobiles than on desktop counterparts, but better in the sense of our games performing faster than they might do if we did not take certain precautions. In addition, this book also covers, as it inevitably must, a whole range of ideas, tips, techniques, and workflows that are useful life-skills generally and which are transferrable not only to non-2D games, but to practically any project-based work, whether game development or not. Who Is This Book For? Every technical book is apparently written with a target audience in mind. That is, it is written for a specific type of reader. Essentially, this means that when writing this book I, the author, must make certain assumptions about you, the reader. These assumptions are not about whether you might be male or female, or tall or short, or American or French, or like cheese or ice cream. Rather, the assumptions are about all the book-relevant topics that I think you will know about already, before even starting to read this title. The point of this is to help the reader get the best possible book they were hoping for. It is to ensure I write a book about only the subject-matter you are truly interested in, and also that I present it in a language that is both accessible and concise. Making assumptions and judgments about others is not something I like doing as a general rule, but it’s something I must do here for the book to be possible. I’ll write these assumptions in the form of five character profiles, as given here; though they don’t represent real people. Three describe typical readers of this book. They’re characters I’ve created to illustrate the skills and knowledge I think a reader of this book should have already. And the final two characters are people I think may not be suited to this book. I do recommend however that these profiles are not taken too seriously. If you happen not to match any of the profiles, or if you match to the latter two, then it certainly does not mean that you will inevitably not benefit from this book. These profiles are intended only as a guide and it is no part of my purpose to dissuade any person from reading this book who is keen to learn and succeed. Game development is infinitely knowable stuff, and nobody that has ever lived was born a game developer; everybody had to begin somewhere. This book is probably for you if you match any of the following profiles: nn —Rosalind is a second-year university student of game development. Rosalind She has worked both in a team and alone making sample games in Unity. She knows the basics of the engine for 3D games. She can import meshes, arrange them in scenes, and create basic script files. She is looking to take her knowledge to the next level by creating 2D games with Unity. nn Arnold —Arnold is an independent game developer who has been working with the tools Unity, GIMP, and Blender for several years now. He’s created a range of games for PC, Mac, and Mobiles, but all of them have been 3D games. He’s tried creating 2D games by taking advice here and there, and following tutorials here and there, piecing together as much information as he can. But his 2D games never seem quite right: his textures look wrong and he doesn’t feel in control of the process. He’s looking for guidance about a solid workflow. www.it-ebooks.info

Introduction xxii nn —Roger has been making 2D games for a long time in tools such as Roger GameMaker Studio, Construct2, Stencyl, SDL, GameSalad, and others. He’s looking to switch from these tools to the Unity engine for his next project. He’s hasn’t used Unity specifically before, but he is familiar with using other 3D engines and is familiar with the basic concepts of 3D, including meshes, vertices, edges, faces, and UV mapping. He is now keen to get started at continuing with this 2D game business in Unity. This book may not be for you if you match any of the following profiles: nn Caitlin —Caitlin has no experience with game development, though she wants to get started because she thinks it’ll be an easy career move. She has never even run Unity. She heard about it from a friend. She believes the best place to start is by learning how to use it for making 2D games. nn Pierre —Pierre is an experienced artist, game designer, and level designer but he really dislikes coding. He has recently decided to start up his own games company but wants to make 2D games in a visual way without having to code. If you want to learn the basics of Unity before proceeding with this title, then I recommend any of the Note following resources: Beginning 3D Game Development with Unity 4 by Sue Blackman, Unity 4 Fundamentals by Alan Thorn, or the Complete Beginner’s Guide to Unity for Game Development by Alan Thorn (Online Video Course). In addition, if you’d rather avoid coding altogether (like Pierre in the preceding list), there are still development options for you in Unity. Specifically, you can use the Unity add-on PlayMaker (http://www.hutonggames.com/), which is a Visual Scripting tool. That being said, this book will make extensive use of traditional code-based scripting. Why Is This Book Necessary? If you’re not already convinced about the value of this book, I anticipate this may be for one of two reasons. First, some might think this book unnecessary because there’re so many engines and libraries already available and dedicated to 2D games that it’s not really valuable to show how a 3D engine like Unity can be made to do the same thing. Why not just use the other engines instead and leave it there? There are two main lines of response to this that I want to present: one negative and one positive. The negative response is about existing users of Unity who do not want to switch away if possible: many game developers may have already invested in the Unity engine for making their 3D games, and while they have considered the possibility of purchasing alternative tools for 2D development, they would rather find a more cost-effective method for re-using the familiar Unity tools to create their 2D games as well. This book will demonstrate in each chapter how the familiar Unity tools can be used in new ways for a 2D workflow. The positive response is about non-Unity users looking around for new 2D development tools. Here, there are positive reasons to recommend Unity as a 2D game creator in its own right. Not only are 2D games possible in Unity, as this book will show, but Unity offers us the ability to mix and integrate its existing and powerful 3D functionality into the 2D games we create, such as mesh effects, particle effects, and 3D audio. These can www.it-ebooks.info

分享到：

赞收藏

资料库

Learn Unity for 2D Game Development 无水印pdf.pdf

相关推荐

开发技术

热门标签

最新资料