procedural-mesh-generator VS EntityComponentSystemSamples

The generator is available here:https://github.com/sxm-sxpxxl/procedural-mesh-generator

Sure. This is the repo. It contains more than Physics

(In general - I'd recommend looking at https://github.com/Unity-Technologies/EntityComponentSystemSamples and use their manifest.json as a base for your project)

heres some samples and reads from unity https://github.com/Unity-Technologies/EntityComponentSystemSamples

Check out the links here. The official ressources contain videos, text tutorials and examples.

The manual is a good starting point. There is also the scripting API for specific syntax, the dots samples by unity and the megacity sample by unity for a full project.

The ECS samples have both. I am using the new input system and it works. The gist is to have a systembase for the callbacks that sets singleton components for the gathered input. Then each system (base or isystem) can query those as normal components. New input system

DOTS comprises a number of new features in Unity. Dive into this GitHub as it’s got a number of great resources to get started.

In Unity, the implementation was done by moving functions from the Entity to the Archetype, which then can be accessed via interfaces. Those interfaces can be inherited in classes. I have "running, waiting, scanning" behaviour classes that get applied to those Archetypes, so OOP is still there but different.

If you have the same problem that I had. I found the solution from Unity's ECS Samples here the link: https://github.com/Unity-Technologies/EntityComponentSystemSamples it's in Advanced/EntityPrefab long story short you should use DynamicBuffer with struct that includes EntityPrefabReference and then you must load it via adding RequestEntityPrefabLoaded component and only then when we have PrefabLoadResult component we can spawn it.