Book Image

Game Development with Unity for .NET Developers

By : Jiadong Chen
Book Image

Game Development with Unity for .NET Developers

By: Jiadong Chen

Overview of this book

Understand what makes Unity the world’s most widely used real-time 3D development platform and explore its powerful features for creating 3D and 2D games, as well as the Unity game engine and the Microsoft Game Dev, including the Microsoft Azure Cloud and Microsoft Azure PlayFab services, to create games. You will start by getting acquainted with the Unity editor and the basic concepts of Unity script programming with C#. You'll then learn how to use C# code to work with Unity's built-in modules, such as UI, animation, physics, video, and audio, and understand how to develop a game with Unity and C#. As you progress through the chapters, you'll cover advanced topics such as the math involved in computer graphics and how to create a custom render pipeline in Unity with the new Scriptable Render Pipeline, all while optimizing performance in Unity. Along the way, you'll be introduced to Microsoft Game Dev, Azure services, and Azure PlayFab, and using the Unity3D PlayFab SDK to access the PlayFab API. By the end of this Unity book, you'll have become familiar with the Unity engine and be ready to develop your own games while also addressing the performance issues that you could encounter in the development process.
Table of Contents (16 chapters)
1
Part 1: Basic Unity Concepts
4
Part 2: Using C# Scripts to Work with Unity's Built-In Modules
9
Part 3: Advanced Scripting in Unity

The Model-View-ViewModel (MVVM) pattern and the UI

A common challenge in Unity development is to find elegant ways to decouple components from each other, especially when developing the UI because it involves UI logic and UI rendering. Model–View–ViewModel (MVVM) is a software architectural pattern that helps developers separate the ViewModel, which is the UI logic, from the View, which is the UI graphics. In this section, we will explore how to implement an MVVM pattern in Unity.

Figure 3.40 – MVVM

As its name suggests, MVVM consists of three parts:

  • Model: This refers to the data access layer, which can be Database, or PlayerPrefs, which stores player preferences in Unity, and so on.
  • View: This represents the Unity UI. It needs to be a Unity component that inherits from MonoBehaviour and is attached to the UI object. Its main role is to manage UI elements and trigger UI events, but it does not implement any concrete UI...