After installing the latest Unity beta when re-assured that it fixed bugs regarding the input manager, I opened my project with the new version and received these two errors:
C:/Users/(username)/AppData/Local/Unity/cache/packages/packages.unity.com/com.unity.package-manager-ui@1.9.11/Editor/Sources/UI/Common/PopupField.cs(8,36): error CS0246: The type or namespace name `BaseTextElement' could not be found. Are you missing an an
C:/Users/(username)/AppData/Local/Unity/cache/packages/packages.unity.com/com.unity.package-manager-ui@1.9.11/Editor/Sources/UI/Common/PopupField.cs(118,33): error CS0115: `UnityEditor.PackageManager.UI.PopupField<T>.ExecuteDefaultAction(UnityEngine.Experimental.UIElements.EventBase)' is marked as an override but no suitable method found to override
These two errors actually got cut off in the editor, so this is what was given to me.
The obvious first question would be to ask what kind of UI element things have I been doing? Currently the canvas in my projectās only scene has three text elements, which makes sense given the error is that it canāt find āBaseTextElementā. What confuses me further is that the text elements are actually rendering properly in the game screen and show their default text values. I decided to reimport my assets using āReimport Allā and this didnāt fix the issue. Then, I deleted the com.unity.package-manager-ui@1.9.11 folder in the cache folder and re-opened my project with the same outcome.
Is there something Iām doing wrong or is it a known issue with this Unity 2018.3.0a6 Beta?
Is it possible you could try the beta using that link and let me know if you get the same problem? I just want to make sure if thereās anything Iām doing wrong on my end or if itās a thing for everyone who installs the beta.
I never personally found a solution. I basically just gave up on using Unity for any projects for a while. The only reason I even downloaded this beta was because it launched a new Input Manager that supposedly fixed XInput issues previously in Unity, and now the engine itself wasnāt working.
At this point, Iām basically just going to program my own engine in C++ and not care about multi-platform support for Mac or Linux until I learn Unreal Engine more. Unity has many other underlying issues that just donāt meet the needs of my games, and Iād only recommend it as an absolute last resort for beginners.
No, but I will try it when I get home from work today. Even if that fixes the error, I likely wonāt be using Unity for my project unless I absolutely have to.
I started by doing a clean install of Unity version 2018.3.0b3.
I then downloaded and started the 2D Game Kit from Unity Hub. I had 8 errors, of the form āerror CS0012: The type āAttributeā is defined in an assembly that is not referencedā.
I then tried @karl_jones tip and clicked on āHelp->Reset Packages to defaultsā. This caused the following log file to appear ā
Packages were changed.
Update Mode: resetToDefaultDependencies
The following packages were added:
com.unity.collab-proxy@1.2.9
The following packages were updated:
com.unity.analytics from version 2.0.16 to 3.0.9
com.unity.purchasing from version 2.0.3 to 2.0.1
com.unity.textmeshpro from version 1.2.4 to 1.3.0
com.unity.package-manager-ui from version 1.9.11 to 2.0.0-preview.7
The following packages were removed:
com.unity.cinemachine@2.2.0
com.unity.postprocessing@2.0.9-preview
At this point, I had 25 errors, all in CinemachinePostProcessing.cs. Hereās the first one ā
Assets\2DGamekit\Utilities\CinemachinePostProcessingV2\CinemachinePostProcessing.cs(13,29): error CS0234: The type or namespace name āPostProcessingā does not exist in the namespace āUnityEngine.Renderingā (are you missing an assembly reference?)
I have yet to find a Unity tutorial project with no errors.
2018.3 is still in beta, the content team do not support betas. Once release candidate is out then the projects will have updated versions.
If you want to use the 2D tool kit or a tutorial/sample then I suggest you use 2018.2.
I would strongly urge you not to learn Unity with a beta version.
If you must use 2018.3 then it may be possible to fix the issues you describe by manually updating the Cinemachine and PostProcessing packages through the package manager.
Stumble upon the same problem, but now with the release version of Unity 2018.3.0f2.
Tried Help/Reset packages to default, but itās doing nothing, literraly, nothing happens after pressing it.
Is there a way to manually update and/or reset package manager?
Thx for the tip.
Unfortunately didnāt work for me. But Iāve managed to revive the engine by creating new project and stealing Packages/manifest.json from there. Though I have to reinstall all additional packages used by my project, but at least I have a working engine right now.
I am not sure if it is related, but I am running into missing .cs files from a fresh install of Unity in a fresh project. The package reset idea did not help the missing files appear.
