Use the job system with Entities
The Entities package uses the C# Job System extensively. Whenever possible, you should use jobs in your system code.
For main thread access, you can use C# foreach
over the Query
objects in SystemAPI. For convenient job scheduling, you can use IJobEntity. In niche situations, or when you want manual control, you can use IJobChunk
's Schedule()
and ScheduleParallel()
methods, to transform data outside the main thread.
When you schedule jobs, ECS keeps track of which systems read and write which components. Later systems' Dependency
property will include the job handles of earlier systems' scheduled jobs, in cases where the set of components read and written overlap.
For more information about systems, see System concepts.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.