Quote:Transforms will also be evolving to reduce the considerable time spent to read/write/sync Transform data between GameObjects and Entities. Unified Transform will merge ECS and GameObjects Transforms so we no longer have to copy data between two different representations. [...] You will also be able to manipulate the Transform of a GameObject directly via ECS APIs, fully Burst-able.
My take of this is that the GO Transform will just be propety backed by a ECS transform. You can interact with it directly from GO without going through hoops of managing Entity reference and belonging World yourself - and it will be faster. But, it may still cause sync points, because systems will still mutate it - and if you don't want to end up with race condition, and still keep scheduled jobs from systems, there's not much of a choice.
Quote:How/when are you moving things relative to Obi's update? Could you give a bit more information about what you're doing and how?
As stated before; I use ECS with a presentation gameObject.
This means that I don't use PhysX, but the Unity Physics (ECS) for the physics world.
ObiSolver is set up on the presentation gameObject of the Player. In the child hierarchy I have Obi Bones, but will later have cloth as well.
ObiSolver is set up with Asynchronous mode, Burst (CPU), Interpolateion.None. I've tried different options here but none seem to improve the issues.
The game loop looks like this;
Frame
Fixed Update
- ObiSolver FixedUpdate (Only Completes)
Simulation Update
- Prediction tick
---- Fixed Step (store state to interpolate)
- Interpolate Position From Physics (Both platform and player interpolates here in sync with eachother)
- Update GameObject transforms from entities
Late Update
- ObiSolver Updates
Rendering
So the Obi Solver is moved by a physics simulation that is interpolated.
I think either driving the update manually;
- Being able to call the contents of LateUpdate with my own FixedDeltaTime and Steps from the ECS Fixed Steps, this means I can set the transform temporary to "fixedState platform localPosition" before manually calling the previous mentioned function
Cons;
- It needs the same physics fidelity rate as the simulation
- Inertia is only from local platform position, no custom % inertia from platform
Or
- Have an override/callback for InertialFrame to set custom Velocity and Acceleration (ignoring Transform translation).
I think the angular velocity form VelocityAtPoint is a bit more problematic to solve here since I don't think I can override the Transform to e.g. latest fixed state platform "localPosition" as I think it would be jittery? But not sure.
Thank you for your time.