new subscence and conversion workflow ?

I've seen some previous demo's of pure and hybrid ECS , and now there is that new conversion workflow and I'm really confused about it all .

if I understand then the conversion workflow will turn gameobjects into entity's - which is useful for the components that are not pure ECS yet like the graphics and physics - but what happens to any logic in custom script that is attached to a game object ?

obviously the conversion workflow does not write my systems for me

I've seen demo's were people would convert an object to entity and then also add components to it along with systems.

but if I'm starting a new project how should I go about it ?
first convert the game object with its graphic and physics components and then add all my custom components and systems ecs way ?

 

You write authoring MonoBehaviours that implement IConvertGameObjectToEntity and attach your custom IComponentData. The samples have really simple examples of how to do this.

 

links to the subscene samples are dead

 

Authoring Sample: https://github.com/starikcetin/Learning-Unity-ECS-2/tree/master/01 - Converting GameObjects to Entities/Assets/01.C - Authoring

SubScene Sample: https://github.com/starikcetin/Learning-Unity-ECS-2/tree/master/01 - Converting GameObjects to Entities/Assets/01.D - Sub Scene

 

https://github.com/Unity-Technologi...master/ECSSamples/Assets/HelloCube/1. ForEach
This is as simple as it gets and shows you how to add a custom rotation speed component.