Unsafe' is inaccessible due to its protection level in DataFlowGraph

I just tried to update to 2020.1 with a lot of updates packages along with that. I ran into a problem with DataFlowGraph 0.15.0-preview.5 (needed for Animation 0.5.1). I have 34 errors that try to access Unity.Burst.Unsafe, but it can’t get them because they are internal or just not in the namespace that DataFlowGraph thinks, here are two examples:

Library\PackageCache\com.unity.dataflowgraph@0.15.0-preview.5\Runtime\ComponentNode.cs(443,20): error CS0122: ‘Unsafe’ is inaccessible due to its protection level

Library\PackageCache\com.unity.dataflowgraph@0.15.0-preview.5\Runtime\RenderContext.cs(48,20): error CS0103: The name ‘Unsafe’ does not exist in the current context

I can’t find anything related to this issue anywhere? Am I missing something?

Have you tried re-open unity editor or hitting the clear button in the Console tab? Whenever I finish updating Burst Package, I see those notifications pop up and reopening the editor makes them all disappeared.

I have restarted Unity so many times :confused: The issues are not going away…

Hmm… Now it seems to have morphed into this instead:

Library\PackageCache\com.unity.animation@0.5.1-preview.3\Unity.Animation\Core\AnimationStream.cs(809,74): error CS0103: The name ‘Unsafe’ does not exist in the current context

All the issues are in Animation instead.

Anyone have similar issues?

Collections used to have the Unsafe dll now it doesn’t. DFG relies on that. It’s the fault of the animation package though for having incompatible dependencies.

Providing your own CompilerServices.Unsafe dll is how to resolve this for now.

4 Likes

And what is the easiest way to do that?

Another fix seems to be to revert to Hybrid Renderer 0.5.2-preview.4 and DOTS Editor 0.8.2-preview