![\"\"](\"https:\/\/courses.ideate.cmu.edu\/53-353\/m2023\/wp-content\/uploads\/2022\/06\/image-5.png\")
When we launch this, our editor will look mostly the same, with a few small, but significant differences. First, you will notice that our Scene window is set to “2D” mode, with our camera facing the XY plane.<\/p>\n\n\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/53-353\/m2023\/wp-content\/uploads\/2022\/06\/image-6.png\")
<\/figure><\/div>\n\n\nYou will also notice that our scene only include a camera – by default there is no directional light, because we will be using sprite rendering<\/strong> in this project instead. Also, our Main Camera<\/strong> is a little different – our Projection<\/strong> is set to Orthographic<\/strong>, and there is no Skybox<\/strong>. (There can be a skybox, but none is included by default, so the Clear Flags<\/strong> option falls back to the Solid Color<\/strong> designation.<\/p>\n\n\n While the 2D \/ Orthographic camera can<\/em> be used to render 3D content – remember, we did this with our Pong game – the primary method of drawing objects on the screen for 2D content is to use Sprites<\/strong>.<\/p>\n\n\n\n \u201cSprite\u201d is a term that has been used in the video game industry almost since it\u2019s inception. In the beginning, it referred to an image of a specific size and type that could be drawn directly to the the screen without having to be processed by the CPU, and was used to improve the performance of a game. These days, the term refers to any bitmap (or image) that is used primarily as a 2D object in a game.<\/p>\n\n\n\n For now, we will use Unity’s built-in sprites which are simple shapes that we can use to explore layers and physics. <\/p>\n\n\n\n Sprite rendering works differently than 3D rendering – there are no polygons to receive and reflect light, and so the images used for sprites are simply presented (and rendered) as-is. The Sprite Renderer<\/strong> has different properties than the Mesh Renderer<\/strong> that we have previously used, including two very important ones – the Sorting Layer<\/strong> and the Order in Layer<\/strong>, and Unity’s rendering engine uses these values to determine which object to draw on top of another.<\/p>\n\n\n The Sorting Layer<\/strong> is given top priority in rendering. The higher the Sorting Layer’s index (as defined in the Tags & Layers<\/strong> panel that we’ve used before), the closer to the camera this layer will render, regardless of other attributes like distance (unless the sprite is behind the camera, and thus outside of the view frustrum). These are especially useful as we set up rules for our tilemaps, so that we can generate proper layers without having to worry about actual z-depths.<\/p>\n\n\n\n The next level of sorting priority when drawing is the Order in Layer<\/strong> setting. Overlapping objects that are contained within the same layer will use this numeric value to determine which should draw on top of the other – the higher number sprite drawing over top of the lower numbered sprite. (These numbers can also be negative, and these values can be changed programmatically if need be).<\/p>\n\n\n\n In the event that overlapping sprites do not have different layers or layer orders, then there are a few other comparisons such as distance from camera (as determined by the pivot point). But if you have overlapping sprites, it’s best to use these systems.<\/p>\n\n\n\n Unity’s 2D physics system relies on a different physics library than the 3D system, and so the sprites that we create will use a separate set of components when operating in the 2D physics world. There is a Rigidbody2D<\/strong> type component that performs the same task as the 3D Rigidbody, but only operates on the XY plane with the only possible rotation happening on the Z axis, towards the camera).<\/p>\n\n\n There are also a set of 2D Colliders<\/strong> which work with this system, including a BoxCollider2D<\/strong>, a CircleCollider2D<\/strong> and a CapsuleCollider2D<\/strong>. It is important to note that collision detection also relies upon its own method, OnCollisionEnter2D(Collision2D collision)<\/strong>.<\/p>\n\n\n\n As a demo today, we built a simple environment using multiple square sprites (stretched to form rectangles), plus a few sprites with the Rigidbody controller attached. We used the Rigidbody2D.MovePosition( ) <\/strong>function to move our sprite towards a location that we defined as the current position + a directional offset (using the Input.GetAxis( )<\/strong> for horizontal and vertical dimensions).<\/p>\n\n\n\n![\"\"](\"https:\/\/courses.ideate.cmu.edu\/53-353\/f2020\/wp-content\/uploads\/2020\/11\/image-3.png\")
<\/figure><\/div>\n\n\nPart 2: Sorting Layers<\/h3>\n\n\n\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/53-353\/m2023\/wp-content\/uploads\/2023\/06\/image.png\")
<\/figure><\/div>\n\n\nPart 3: 2D Physics & a Top-Down Controller<\/h3>\n\n\n\n
![\"\"](\"https:\/\/courses.ideate.cmu.edu\/53-353\/m2023\/wp-content\/uploads\/2023\/06\/image-1.png\")
<\/figure><\/div>\n\n\n
\n\n\n\nTopDownCharacterController.cs<\/pre>\n\n\n\n
using System.Collections;\nusing System.Collections.Generic;\nusing UnityEngine;\n\npublic class TopDownCharacterController : MonoBehaviour\n{\n public float speed = 1.0f;\n\n private Rigidbody2D rb;\n private Vector2 direction;\n\n\n \/\/ Start is called before the first frame update\n void Start()\n {\n rb = GetComponent<Rigidbody2D>(); \/\/ get the rigidbody for this object\n direction = new Vector2();\n }\n\n \/\/ Update is called once per frame\n void Update()\n {\n \/\/ get the movement inputs\n direction.x = Input.GetAxisRaw(\"Horizontal\");\n direction.y = Input.GetAxisRaw(\"Vertical\");\n\n }\n\n private void FixedUpdate()\n {\n if (rb)\n {\n \/\/ move the controller\n rb.MovePosition(rb.position + (direction.normalized * speed * Time.fixedDeltaTime));\n } else\n {\n Debug.Log(\"Missing a Rigidbody 2D component\");\n }\n }\n}\n<\/pre>\n","protected":false},"excerpt":{"rendered":"