MeshInstance render system interaction

It's apparent a lot of work went into this. Kind of surprising there is just a one liner comment.

Is it even possible to update position/rotation/scale?

Also curious why so many of these systems don't use injection? Kind of begs the question what's so wrong with injection that Unity doesn't use it for their own stuff so often. I'm guessing it's also why most of these systems don't show in the entity debugger correctly?

 

Could you please be more specific about what is means? Are these obsolete? Will they be removed?

 

IJobProcessComponentData would be perfect if it could somehow pass an entityarray as well. Also some versions with 4+ generics.

I could use it for 90% of my systems if those were implemented. It could reduce so much code.

 

And DynamicBuffer. They all should share some common interface for this purpose I would say.

 

Would be nice if there was a nice and tidy documentation page explaining the recommended way to implement these kind of performant ECS systems. The source code examples differ quite a bit and it's not easy to decipher what is currently the "best" way, especially if you are still learning ECS design patterns.

Also I think that a documentation page is easier to keep up to date than the plethora of code examples from the ECS samples repository.

 

From what I know, lambda will give you performance penalty. Or your solution is try to map lambda to the generated code so the final compiled code is based on generated code instead of lambda?

 

@Joachim_Ante - I was already wondering if some kind of lambda -> codegen would be in the works, since it seems like the obvious solution to a lot of problems and enables things like functional composition.

Are there any good examples of using the ArchetypeChunk API? I know there's code in TransformSystem with the new preview packages but it's extremely verbose, I've used it a little in unit tests, but I'm wondering if there's anything comprehensive that's short and to-the-point.

 

Maybe this could help.

 

I like the query approach I think it's a much more natural and direct approach. If you look at generic ECS systems, the system is basically this awkward abstraction that tightly couples queries and the rest of the logic flow. Once you decouple those, IMO it almost immediately leads to better abstractions for querying/updating data.

 

Perfect, thanks! I haven't had time to check the docs at work today.

 

To my first question, I figured out CustomLocalToWorld does what I needed. Naming seems rather awkward atm, not a very intuitive system so without some documentation it's not actually obvious I'm even doing the right thing.

 

I do like the new ArchetypeChunk api. It takes a bit of time to understand the new structure but overall it is more transparent compared to the injection system.

Is there a way to access classic parts like game objects or transforms with this api? Or is it still necessary to use injection for these interactions?

 

Can you add IJobProcessComponentDataWithTransform? I develop 2d game with sprites, so i have to use hybrid ecs. A lot of my systems use Transform component, like this:

Code (CSharp):

1. struct MarkForRemoveJob : IJobParallelForTransform
2.  {
3.         [ReadOnly]
4.         public float ViewLeftBorder;
5.         [ReadOnly]
6.         public ComponentDataArray<DeleteOffset> DeleteBound;
7.         public ComponentDataArray<ItemState> State;
8.  
9.  
10.         public void Execute(int index, TransformAccess transform)
11.         {
12.             bool outOfView = transform.position.x + DeleteBound[index].ItemWidth < ViewLeftBorder;
13.             if (outOfView) State[index] = new ItemState { State = ItemState.RequiredRemove };
14.         }
15.  }

So, jobs with transform component will be perfect for me:

Code (CSharp):

1. struct MarkForRemoveTransformJob : IJobProcessComponentData<TransformAccess, DeleteOffset, ItemState>
2.  {
3.         public void Execute([ReadOnly] ref TransformAccess transform, [ReadOnly] ref DeleteOffset deleteOffset, [WriteOnly] ref ItemState state) {.....}
4.  }

But i cant use TransformAccess as generic parameter in IJobProcessComponentData.