14-09-2020, 12:44 PM
(This post was last modified: 14-09-2020, 12:54 PM by josemendez.)
Could reproduce the issue by enabling the jobs debugger. With it disabled, things run normally, so the workaround for now is to just disable the debugger (which should be done anyway for normal performance).
This error is not present in Unity 2019. With the debugger enabled, no errors are shown in the console and the simulation runs normally using Burst. So it's either a bug in our job scheduling scheme that 2019's job debugger does not catch, or a bug in 2020's job debugger. Will investigate further.
This error is not present in Unity 2019. With the debugger enabled, no errors are shown in the console and the simulation runs normally using Burst. So it's either a bug in our job scheduling scheme that 2019's job debugger does not catch, or a bug in 2020's job debugger. Will investigate further.