Top Tweets for #Dataoriented

Thousands of pickups don’t need thousands of Actors. By building a coin pickup system with plain data arrays rather than one Actor per coin, we can add thousands of pickups to the world in microseconds, not milliseconds. The code remains simple to understand and maintain. We store each coin’s location, credit reward, and mesh instance ID in three synchronized arrays. A single Instanced Static Mesh Component represents the coins in the world. This layout, known as a Structure of Arrays, is one way to apply Data-Oriented Design to your gameplay systems. It lets us process thousands of pickups with less memory overhead and is more cache friendly than using Actors and Components, which is important for performance. During the lessons in the new UE5 C++ Course we go into detail on how and when to apply this in your own projects. Data-oriented Design is nothing new and Unreal Engine has a similar data-oriented system called Mass. But I often see developers learn this approach very late in the process as Unreal Engine is so heavily biased to OOP (object oriented programming). OOP is convenient, but not always the right approach. In the C++ course we explain and apply both.