The many hours you spend writing code, debugging, profiling, and iterating should go as smoothly as possible. We’re working hard to shave off the time spent switching between the Editor, your IDE, and Game view or Play mode.
What’s ready for you today
So, how are we doing this? To start with, we have been optimizing our asset import since the release of 2021 LTS, and we’ve made it 3–4 times faster, while project import times are 8.7% faster compared to 2020 LTS.
We’ve improved IL2CPP build times by 20% since the last LTS release, and by 40% since 2019.4. Our investment in our suite of Profiler tools helps you identify performance bottlenecks more efficiently and in greater detail. Our Memory Profiler, which will soon be production-ready, adds detailed profiling for both user and engine code, as well as faster location of memory use.
Looking ahead to 2023 and 2024, we’ll move both the Editor and runtime to Microsoft’s CoreCLR, thereby providing you with the best possible .NET experience and enabling all the latest C# 10.0 features. This will also bring a high-performance just-in-time (JIT) compiler, server-ready garbage collector, more robust debugging, and access to the ubiquitous tooling for testing, profiling, and diagnostics from the .NET ecosystem.
We’ll be sharing a blog post on performance in the weeks if you want to know more, or you can check out our Editor roadmap page for details about where things are going.
We’re making multiple investments in sharing more real-world best practices in partnership with Unity Professional Services, a team that helps some of the biggest studios using Unity with in-depth analysis of their project’s code and assets to identify areas for optimization. Here are three e-books packed with advanced, actionable tips to help keep your game development as efficient as possible:
Source: Unity Technologies Blog