Question Are there any problems making multiple IInputComponentData per entity (Player)?

Hello everyone,

As what I learned from DOTS best practice, the recommended approach is to have many small components with fewer properties rather than a few large components with many properties.

By breaking down data into smaller components, I can ensure that the ECS only processes the necessary data for each system, reducing memory overhead and improving overall efficiency also I can consider what to be replicated or not.

Does IInputComponentData same as any other components (i.e. IComponentData) that I can the bove approach apply on?


So, which is better when using IInputComponentData:

Code (CSharp):

1. [GhostComponent(PrefabType = GhostPrefabType.AllPredicted, OwnerSendType = SendToOwnerType.SendToNonOwner)]
2. public struct PlayerMovementInputs : IInputComponentData
3. {
4.     public int Horizontal;
5.     public int Vertical;
6. }
7.  
8. public struct PlayerCameraInputs : IInputComponentData
9. {
10.     public float Pitch;
11.     public float Yaw;
12. }
13.  
14. public struct PlayerAttackInputs : IInputComponentData
15. {
16.     public InputEvent SkillAttack;
17. }

OR......

Code (CSharp):

1. [GhostComponent(PrefabType = GhostPrefabType.AllPredicted, OwnerSendType = SendToOwnerType.SendToNonOwner)]
2. public struct PlayerInputs : IInputComponentData
3. {
4.     public int Horizontal;
5.     public int Vertical;
6.     public InputEvent SkillAttack;
7.     public float Pitch;
8.     public float Yaw;
9. }
10.  

Thanks in advance.

 

Thank you for your valuable response.

 

Is that the IComponentData u mention not just applies to IInputComponentData but also ghost IComponentData that has [GhostField] tag and also regular IComponentData without [GhostField] tag? If yes, so that's why now Entities transform system now combined position, rotation and scale together into one single LocalTransform component?