FryCaptain Posted November 18, 2021 Report Posted November 18, 2021 So, I've just got the demo 10.5X up and running in Unity 2020.1 using North Net Working. Yea! I've purchased Gaia Pro, World Streamer 2, And I'm looking to upgrade the nav mesh because I want to do the modular building and have the path finding be dynamic. But, before I do all that. Should I keep this install on 2020.1 or use a different version of Unity? I get a bunch of errors when opening a project in this version about Unity's UI and CSS. I tried a couple of fixes but they didn't work. It doesn't seem to affect anything in the game. But it is annoying. Also, the video tutorials are kinda old. Can I use the URP or HRP? Or, still just Post Processing 2. Thanks your your input. Quote
Martin (Dragonsan) Posted November 18, 2021 Report Posted November 18, 2021 1 hour ago, FryCaptain said: So, I've just got the demo 10.5X up and running in Unity 2020.1 using North Net Working. Yea! I've purchased Gaia Pro, World Streamer 2, And I'm looking to upgrade the nav mesh because I want to do the modular building and have the path finding be dynamic. But, before I do all that. Should I keep this install on 2020.1 or use a different version of Unity? I get a bunch of errors when opening a project in this version about Unity's UI and CSS. I tried a couple of fixes but they didn't work. It doesn't seem to affect anything in the game. But it is annoying. Can you show me the errors you are having, because Atavism doesn't use CSS/USS? 1 hour ago, FryCaptain said: Also, the video tutorials are kinda old. Can I use the URP or HRP? Or, still just Post Processing 2. Atavism supports URP and HDRP, but shaders that are in the demo package are only for the standard rendering pipeline, so you would have to migrate them or use the core version and implement your assets on top. Quote
FryCaptain Posted November 21, 2021 Author Report Posted November 21, 2021 NullReferenceException: Object reference not set to an instance of an object UnityEditor.UIElements.UIElementsEditorUtility..cctor () (at <20b79eb59c0f467d8b1106b2110bc953>:0) Rethrow as TypeInitializationException: The type initializer for 'UnityEditor.UIElements.UIElementsEditorUtility' threw an exception. UnityEditor.UIElements.UIElementsEntryPoint.CreateRoot () (at <20b79eb59c0f467d8b1106b2110bc953>:0) UnityEditor.UIElements.UIElementsEntryPoint.GetRootVisualElement (UnityEditor.EditorWindow window) (at <20b79eb59c0f467d8b1106b2110bc953>:0) UnityEditor.UIElements.DefaultEditorWindowBackend.OnRegisterWindow () (at <20b79eb59c0f467d8b1106b2110bc953>:0) UnityEditor.UIElements.DefaultEditorWindowBackend.OnCreate (UnityEditor.IWindowModel model) (at <20b79eb59c0f467d8b1106b2110bc953>:0) UnityEditor.GUIView.set_windowBackend (UnityEditor.IWindowBackend value) (at <20b79eb59c0f467d8b1106b2110bc953>:0) UnityEditor.GUIView.OnEnable () (at <20b79eb59c0f467d8b1106b2110bc953>:0) UnityEditor.HostView.OnEnable () (at <20b79eb59c0f467d8b1106b2110bc953>:0) It seems I get a different error message every time I open 2020.1. I was getting something similar to the above about a CSS issue and the UI. If I close then open Unity again I get no errors...? I should probably post this on the Unity form. I'm pretty sure this isn't an issue with Atavism. Quote
Martin (Dragonsan) Posted November 21, 2021 Report Posted November 21, 2021 It doesn't seem like an Atavism related, because we are not using any UI Elements, at least not yet. Is it possible that any other package is using this or maybe it's just a Unity bug? Have you tried to update your Unity Editor? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.