Namespace not visible after installation of a package

Hi All,

I’m trying to add a package to an existing project. The package in question is the awesome UnityAtoms package GitHub - unity-atoms/unity-atoms: ⚛️ Tiny modular pieces utilizing the power of Scriptable Objects which I’ve used in plenty of other projects. The package appears to install correctly (from git) and that is confirmed as I see the Tools → Unity Atoms menu plus I’m able to add assets via Create → Unity Atoms so I know the package has installed and is working. What I’m a bit confused about those Is that I can’t see add ‘using UnityAtoms;’ and access the namespace from any scripts plus the namespace doesn’t show in the Assembly Browser (on Mac) or the Object Viewer (on PC).

Very odd… works with the same version of Unity in a fresh project so I’m wondering what could possibly be blocking the namespace from visual studio… I thought perhaps script execution order but couldn’t even add the namespace there… it came up but wouldn’t add which is odd. This issue is the same on both PC and Mac for me with the same project.

Last resort I guess is to recreate the project but thats quiet a big job so I was hoping someone could give me some pointers on what else to check. Thank you in advance :slight_smile:

1 Like

Show your syntax. Because other namespaces from packages are named like ‘Unity.Mathematics’, ‘Unity.Entities’, etc, I believe this is spelling error and you need to add dot in your usings: Unity.Atoms

HI,

Thank you for the reply but it’s definitely ‘using UnityAtoms;’ in this case… it’s a third party made package (and a very very good one too :-)) rather than a Unity one.

Thank you

I’ve checkd their repo on github, yes, it is without dot - UnityAtoms. So I guess maybe you have some AssembyDefinition files in your project and need to reference in explicitly? Because all plugins and packages are referenced by default player assembly automatically. Also you will be unable to use this from Plugins and Editor folders I guess.