Compatibility with GameObjects
The following is intended for informational purposes only, and may not be incorporated into any contract. No purchasing decisions should be made based on the following materials. Unity is not committing to deliver any functionality, features or code. The development, timing and release of all products, functionality and features are at the sole discretion of Unity, and are subject to change.
If you have accepted to use functional cookies and logged in using your Unity ID at the top right of the page, then sharing feedback is as simple as clicking a card below, selecting a topic’s importance, adding your point of view, and submitting. If you prefer not to accept functional cookies or log in, you will be prompted to enter an email address and validate it, so we know how to reach out when the topic evolves. For more information read the Feedback and privacy terms.
ECS for Unity preserves the standard Unity authoring workflow of creating, previewing, inspecting, and debugging gameplay in your project. It also ensures that Entities is compatible with current GameObject-based systems.
Baking is what enables developers to author content using GameObjects and have that data converted to entities in a runtime optimized format. Incremental baking ensures conversion works effectively at scale in massive scenes, where changes to specific components only bake what is needed for those modifications.
Additionally, developers will be able to switch data modes from authoring to runtime view both in the hierarchy and in the inspector windows of the Editor. As such, they can better understand how baking works, and seamlessly navigate the hybrid environment. As a bonus, this new workflow will, for the first time, enable artists and level designers the ability to author in Play mode without losing their changes when exiting Play mode.