a bunch of errors at import 3d game kit to unity newest version, 6000.27
Assets\3DGamekit\Scripts\Game\Helpers\CameraSettings.cs(4,7): error CS0246: The type or namespace name ‘Cinemachine’ could not be found (are you missing a using directive or an assembly reference?)
like so Cinemachine related. Cinemachine packages are all installed already, but errors.
General rule of thumb: If in doubt “no”, if it is not specified assume the content is not to be used in commercial projects, this protects you from any possible issues later down the line.
I have had to read through a great many licenses to verify the conditions, Unity engine does release some assets but a lot are there for “Educational-Usage” meaning not comercial, but usable on a grand scale. If you can find the assets in the asset store and the store does state ‘Can be used for commercial projects’ etc. then go ahead, other than that, its safer in a legal sense to find assets with “For Commercial Use” flagged
Similarly to leegod, who started this thread, I’m getting several errors after importing 3D Game Kit to Unity (v6000.0.26f1).
In my case, the different errors are related to NavMeshLink. For example:
Library\PackageCache\com.unity.ai.navigation\Runtime\NavMeshLink.deprecated.cs(23,20): error CS0103: The name ‘bidirectional’ does not exist in the current context
All errors refer to different names (‘autoUpdate’, ‘bidirectional’, ‘costModifier’ and ‘UpdateLink’) not existing in current context. All these refer to the same script (NavMeshLink.deprecated.cs).
I did import and actualize every setting the wizard told me to. What should I do in order to get rid of the errors?
unity projects need to be open with the supported unity versions that they were created/verified to work with.
on the asset store page you can check what versions are supported in this case 2020 and 2022 using the built-in render. hdrp and urp are not supported.
why you get errors.
the unity editor and the packages are distinct things, think of the packages like a plugged in module that expand the editor.
each new unity version may change how some internal editor stuff works and because of that some packages features will not work anymore. so as a result if a newer editor version is released older packages versions will not find the editor features they rely on and they will break.
for this navigation issue maybe you can fix it by following the steps here
but I suggest just use the indented version for that project if you just want to learn. no need to bother yourself with these advanced stuff out of the box when trying to learn.
when you will want to work on your game is easy to switch to newer unity versions, they will not be completely different.
Likewise, thank you. I had not been able to solve the issue by myself, and had been looking for other learning projects. Your response is informative and useful.