0.50 beware of strict namespace restriction.

Unity Engine
, ,
1

This code won’t compile on DOTS 0.50:

using Unity.Entities;
namespace MyNamespace.System
{
    public partial class BrokenSystem : SystemBase
    {
        protected override void OnUpdate()
        {
            Entities.ForEach((MyComponent c) => {}).Run();
        }
    }
    public struct MyComponent : IComponentData { }
}

Beware that in a big project this can be quite a nightmare. It means that if you have something like Views.Interaction and Player.Interaction, with a foreach referring both, codegen will break.

The only workaround I found was to give unique names to my namespaces and never use System in any part of the namespace.

Case 1411801

2

Hmm I have about 100 different variations of BovineLabs.X.Systems or Data etc namespaces and have no issue compiling.

My differences are

  • Plural though, I have no System namespace.
  • Also my using are within the namespace if that makes a difference
3

Plural will work because it doesn’t clash with System. And the second might be a viable long term workaround if this behaviour is by design. Still, that’s how Rider and VS functions (putting usings at top of the file, outside namespace).

The bug can be reproduced in an empty project by simply doing a ForEach inside a namespace containing System. That could be My.System.Something or Something.System, as long as System is somewhere, it will break codegen.

4

I had this issue as well with the namespace EnvironmentRenderingSystem, but weirdly completely removing the entities package from the project and reinstalling it fixed the problem…