Working with sorting layers
by Chris Dickinson, John P. Doran, Greg Lukosek
Unity 5: Learning C# by Developing Games
- Unity 5: Learning C# by Developing Games
- Table of Contents
- Unity 5: Learning C# by Developing Games
- Unity 5: Learning C# by Developing Games
- Credits
- Preface
- 1. Module 1
- 1. Discovering Your Hidden Scripting Skills and Getting Your Environment Ready
- Prerequisite knowledge to use this book
- Dealing with scriptphobia
- Downloading Unity
- Teaching behavior to GameObjects
- C# documentation – where to find it? Do I need it at all?
- Working with C# script files
- Creating a C# script file
- Introducing the MonoDevelop code editor
- Instance? What is it?
- Summary
- 2. Introducing the Building Blocks for Unity Scripts
- 3. Getting into the Details of Variables
- Writing C# statements properly
- Understanding component properties in Unity's Inspector
- Changing a property's value in the Inspector panel
- Private variables
- Naming your variables properly
- Beginning variable names with lowercase
- Using multiword variable names
- Declaring a variable and its type
- Assigning values while declaring a variable
- Where you declare a variable is important
- Variable scope – determining where a variable can be used
- Summary
- 4. Getting into the Details of Methods
- 5. Lists, Arrays, and Dictionaries
- 6. Loops
- 7. Object, a Container with Variables and Methods
- 8. Let's Make a Game! – From Idea to Development
- 9. Starting Your First Game
- 10. Writing GameManager
- 11. The Game Level
- 12. The User Interface
- 13. Collectables — What Next?
- 1. Discovering Your Hidden Scripting Skills and Getting Your Environment Ready
- 2. Module 2
- 01. 2D Twin-stick Shooter
- Project overview
- Setting up the project
- Creating our scene
- Implementing player movement
- Shooting behavior
- Creating enemies
- Adding GameController to spawn enemy waves
- Particle systems for enemy explosion
- Adding in sound effects/music
- Adding in points, score, and wave numbers
- Publishing the game
- Summary
- Challenges
- 2. Creating GUIs
- 3. GUIs Part 2 – Clicker Game
- 4. Mobile Endless Game – Procedural Content
- Project overview
- Prerequisites
- Project setup
- Adding the background
- Adding a simple animated character
- Making a repeating background
- Working with sorting layers
- Creating our player behaviour
- Creating obstacles
- Spawning obstacles at runtime
- Game start and end behaviours
- Keeping score
- Summary
- Challenges
- 5. Shooting Gallery – Working with Animations and Tweens
- 6. Side-scrolling Platformer
- 7. First Person Shooter Part 1 – Creating Exterior Environments
- 8. First-person Shooter Part 2 – Creating Interior Environments
- 9. First Person Shooter Part 3 – Implementing Gameplay and AI
- 10. Building an In-Game Level Editor
- 11. Finishing Touches
- 01. 2D Twin-stick Shooter
- 3. Module 3
- 1. Detecting Performance Issues
- 2. Scripting Strategies
- Cache Component references
- Obtaining Components using the fastest method
- Removing empty callback declarations
- Avoiding the Find() and SendMessage() methods at runtime
- Disabling unused scripts and objects
- Consider using distance-squared over distance
- Avoid retrieving string properties from GameObjects
- Update, Coroutines, and InvokeRepeating
- Consider caching Transform changes
- Faster GameObject null reference checks
- Summary
- 3. The Benefits of Batching
- 4. Kickstart Your Art
- Audio
- Loading audio files
- Encoding formats and quality levels
- Audio performance enhancements
- Minimize active Audio Source count
- Minimize Audio Clip references
- Enable Force to Mono for 3D sounds
- Resample to lower frequencies
- Consider all encoding formats
- Beware of streaming
- Apply Filter effects through Mixer groups to reduce duplication
- Use "WWW.audioClip" responsibly
- Consider Audio Module files for background music
- Texture files
- Mesh and animation files
- Summary
- Audio
- 5. Faster Physics
- Physics Engine internals
- Physics performance optimizations
- Scene setup
- Use Static Colliders appropriately
- Optimize the Collision Matrix
- Prefer discrete collision detection
- Modify the FixedUpdate frequency
- Adjust the Maximum Allowed Timestep
- Minimize cast and bounding-volume checks
- Avoid complex Mesh Colliders
- Avoid complex physics components
- Let physics objects sleep
- Modify Solver Iteration Count
- Optimizing ragdolls
- Know when to use physics
- Consider upgrading to Unity 5
- Summary
- 6. Dynamic Graphics
- Profiling rendering issues
- Front end bottlenecks
- Back end bottlenecks
- Fill rate
- Overdraw
- Occlusion Culling
- Shader optimization
- Consider using Shaders intended for mobile platforms
- Use small data types
- Avoid changing precision while swizzling
- Use GPU-optimized helper functions
- Disable unnecessary features
- Remove unnecessary input data
- Only expose necessary variables
- Reduce mathematical complexity
- Reduce texture lookups
- Avoid conditional statements
- Reduce data dependencies
- Surface Shaders
- Use Shader-based LOD
- Memory bandwidth
- VRAM limits
- Fill rate
- Lighting and Shadowing
- Optimizing graphics for mobile
- Summary
- 7. Masterful Memory Management
- 8. Tactical Tips and Tricks
- A. Bibliography
- Index
Next, I want to ensure that the sprites that we added will actually be in the correct order from any of the other sprites that we add to the level. This is because when we place objects on the same Z position, we are telling the graphics card that we don't care what order the images are drawn to the screen (also known as z-fighting). In this case we do and even if it "looks right" in the editor right now, if you ever load or restart the scene it may not look correct so rather than wait for the problem I suggest we fix it now. I could change the Z position of the object, but rather that, we can make use of the sorting layers property instead:
- Select one of the background objects from the Hierarchy tab and then from the Inspector tab, go to the Sprite Renderer component and click on the Sorting Layer dropdown. Then, select Add Sorting Layer… click on the + icon two times and name the newly created layers
BackgroundandForeground. From there, bring theBackgroundlayer up (by dragging the = symbol on the left up) so that it's drawn first:
Now, the background will be drawn first, then the
Defaultobject (acting as our middleground), then the foreground. - Of course, this isn't doing anything just yet, so select the two background objects again and then under the Sprite Renderer component change the Sorting Layer to
Background. - Afterwards, change the two
groundGrasssprites to use theForegroundSorting Layer. We'll keep thePlaneobject at the default so it'll stay as is.
At this point, the Sorting Layers are working correctly! If you want to see what happens when we change the order, go to the Add Sorting Layer… menu again (or click on Layers | Edit Layers from the top-right toolbar) and then drag and equals sign buttons in a different order. Note that if I bought Background all the way down, the following will happen:
All of the other sprites would disappear because they'd be drawn first and then the background on top of them. Of course, change it back afterwards.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.