Hey all, first of all, I’m running 5.6.7f1 (old I know, but Pro license).
I’m new to using the NavMesh feature, so I’ve never had this issue before and wanted to know what’s going on, thought someone here may know.
I’m using the NavMeshComponents 5.6 tree from GitHub for NavMesh generation as it seems to work better than the builtin editor one, and some of the components seem to be required for it to work properly.
Everything works fine in the editor (better than I expected to be honest, kudos to whoever at UT built it), but as soon as I try to build to an executable, I get a CS0234 error that TestTools doesn’t exist in UnityEngine, and CS0246 that NUnit doesn’t exist, despite this working fine in the editor, and never throwing any other errors, these errors are called several times.
These namespaces are in use in the code (commenting out the “using” lines causes other errors) so they clearly do exist, despite not being F12-able in VS, so I’m unsure of what this is or what to do. There doesn’t seem to be much on Google about it.
Is this something others have experienced and know how to deal with?
Did you just clone it? If so, even if you get the clone from the 5.6 branch, you’re probably on master. Make sure you’re on the 5.6 branch.
If you are on 5.6, then perhaps the commit you are on has a bug and they left unsupported testing cruft in the build, or perhaps they mis-merged or mis-cherry-picked something.
See if you can go back a bit in history in the commits and use something earlier, or else just rip all the testing / NUnit crap out of the code you have.
UPDATE: yeah, looks like they left Test crap in… I would just nuke the Tests directory
I grabbed specifically the 5.6 branch, The later versions contain code that can’t be used in below 2017.
Works fine without the dir now, thanks.
Weird they left that in though.