Ich habe mich eine Nacht lang damit beschäftigt, den Heiligen Gral der Unity Entwicklung - den Unity Gral - zu suchen, und ihn gefunden.
Was ich als Unity Gral bezeichne, ist die Verwendung von Visual Studio Solutions, Asset-Management und einem Unity Projekt, ohne zusehr die Vorteile der Versions Kontrolle auszuhebeln. Vorteil des Unity Gral ist die einfache Nutzung des Repositories für Artists, als auch für Entwickler und Game Designer/Entwickler.

I found myself trying to write code for navigating in hierarchy like manner in Unitys Inspector (RuleSet -> Entity -> Component -> More To Come) today. First thought I had: Just put a reference field into every single scriptable object and your done ... well no.

I had the pleasure of creating loads of garbage while trying to decouple things with just a single, simple thing: Events. As Jackson Dunstan has shown C#-Events are heavily allocating memory and thats a unwanted pitfall in game programming. Creating 4000 objects on the fly with event allocation an...

Some times you write classes, inherit from them and create properties to cast things from base class to your known types.

Based on these two threads on Unity Forums and my research on my final project I just tried to get my async scripts memory footprint down to nearly zero (3 Byte per Frame?) which is impossible with Unitys Coroutines because they are generating 17 Byte per Frame with just a single yield return n...