If you’re working on a game (or other real-time simulation) that requires the most efficient CPU usage possible, then Unity’s Data Oriented Technology Stack (DOTS) is a great way to get the performance you need. However, to use DOTS successfully, you can’t simply grab the API documentation and dive straight in. Before you begin creating a project with DOTS you must understand the following: The fundamental concepts of data-oriented design Data-oriented design in Unity The best practice advice in this guide Data-oriented design (DOD) is a big change from the object-oriented programming (OOP) that many developers have spent their whole careers working with. This means that the learning curve for DOTS might be steep, and there are a lot of pitfalls that might stop you from getting the performance benefits you hope for. This Best Practice Guide contains advice to help avoid those pitfalls. Sections 1 and 2 of this guide explain the fundamental knowledge you need to understand before starting to build DOTS applications, and the biggest obstacles to achieving good performance. Later sections contain techniques that you can use to squeeze even more performance out of the technology, but you must have a fundamental understanding of the basics to get good use out of them. NOTE: This guide is not intended to be a comprehensive tutorial to all aspects of building a DOTS-based application. The primary focus of this guide is to help you obtain the best possible runtime performance in code written using the DOTS packages, with a particular focus on the Entity Component System. As such, there are many topics which fall outside the scope of this guide and are not covered in detail or mentioned at all. Here is an incomplete list of topics which aren’t covered here: In-depth discussion of features which were primarily used in older, experimental versions of the Entities package, such as SystemBase and Entities.ForEach() How to use the Baking system to author and convert entity data How to create and use BlobAssets to represent memory-ready, read-only data Some newer convenience features such as Aspects . Aspects can help to simplify complex entity queries but come with an additional runtime performance cost. This feature is under active development and may be featured in future versions of this guide. Packages which supplement ECS but which are not a core part of DOTS, such as Entities Graphics , Unity Physics , Havok Physics for Unity , and Netcode For Entities

This course contains three tutorials that introduce the basics of the Entities package, the C# Job System, and other core parts of Unity's Data-Oriented Technology Stack (DOTS), which facilitates writing high-performance C# code.

A primer on Vector maths - as well as information on the Dot and Cross products. This tutorial is included in the Beginner Scripting project. Previous: Update and FixedUpdate Next: Enabling and Disabling Components

Learn about some basic conventions and syntax of writing code - dot operators, semi-colons, indentation and commenting. This tutorial is included in the Beginner Scripting project. Previous: Variables and Functions Next: If Statements

Hearing about DOTS hype? Wondering if it's for you? Be part of the Data-oriented design Bootcamp and find out. We know finding the time for professional development and keeping up with training is hard, but we’re going to challenge you to dedicate 4 hours over the course of the week alongside your fellow professional developers around the world. As a community, you’ll learn ways to improve your game’s performance, resulting in better framerates, more objects in the scene, and more performance benefits using DOTS. To enlist in the Data-oriented design Bootcamp, register here.

Learn how to create static variables, methods, and classes.

In this tutorial, you’ll learn about two advanced physics solutions available for projects that use Unity’s Entity Component System (ECS) framework: Havok Physics for Unity and Unity Physics. Important: This tutorial only applies to Unity 2022.2 Tech Stream and beyond, which will be reflected in the tutorial version in early 2023.

Namespaces are a fundamental aspect of scripting. By the end of this tutorial, you’ll be able to: Explain the purpose of namespaces. Import a namespace. Declare a type as part of a namespace. Declare nested namespaces.

In this tutorial, you will learn how to write a Shader that generates rim lighting using the surface normals of an object.

In this workflow, we will create new geometry with the Quad Draw Tool by placing vertices and drawing polygons directly on the reference mesh. We will use hotkeys to access enhanced functions of the Quad Draw Tool. In the process, we will demonstrate best practices for modeling and retopologizing that will help you with creating an object model.