Since starting tinkering with DOTS Physics I'm used to ticking off JobsDebugger checkbox every time I start Unity. Recently after updating to 2020.1 decided to give it a try, but among some legit and actually useful safety errors it keeps producing stuff like this: InvalidOperationException: The previously scheduled job SolverarallelApplyGravityAndCopyInputVelocitiesJob writes to the Unity.Collections.NativeArray`1[Unity.Physics.MotionVelocity] ParallelApplyGravityAndCopyInputVelocitiesJob.MotionVelocities. You are trying to schedule a new job ExportPhysicsWorld:ExportDynamicBodiesJob, which reads from the same Unity.Collections.NativeArray`1[Unity.Physics.MotionVelocity] (via ExportDynamicBodiesJob.JobData.MotionVelocities). To guarantee safety, you must include SolverarallelApplyGravityAndCopyInputVelocitiesJob as a dependency of the newly scheduled job. I'm not doing anything fancy, no custom StepPhysicsWorld etc., just regular physics bodies interacting. So this error must be totally on Unity Physics side. Or am I misunderstanding something?