Recently I keep getting this error and force me to move out some components as another entity which is quite annoying. Will mega chunk feature coming soon so I no longer need to fix this error anymore?
ArgumentException: System.InvalidOperationException: Entity archetype component data is too large. Previous archetype size per instance {archetype->InstanceSizeWithOverhead} bytes. Attempting to add component size {componentInstanceSize} bytes. Maximum chunk size {chunkDataSize}.
So you have an entity that has so much component data that it can’t fit one entity in a chunk ?
Ya.
And you use all these components together in the same job ? or have combination of job that basically make all component relevant to each others ?
If not, splitting it in multiple entity based on the set of component that are used in conjonction in job is probably a more performant approach even though it’s like you said more annoying to manage.
If you’re using buffers you can use [InternalBufferCapacity(0)] to keep all of the entry items outside the archetype’s chunk.
Eventually some games will evolve into things so big that although there is no one job that uses enough components to fill a chunk, there could be enough jobs that uses different parts of the same entity that fills a whole archetype.
Excuse my terrible paint drawing but it should explain what I mean much easier than I can put into words.
Another solution is to use another entity to hold some of the components then have a reference of it in the main entity. You can easily find the referenced entity using ComponentDataFromEntity.
