Related --

Should dictionaries be able to open theme resources via the following syntax? This worked previously, and may be related to the above error.

<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation">
    <ResourceDictionary.MergedDictionaries>
        <ResourceDictionary Source="/Packages/com.noesis.noesisgui/Theme/NoesisTheme.DarkBlue.xaml"/>
        <ResourceDictionary Source="/Packages/com.noesis.noesisgui/Theme/NoesisTheme.Styles.xaml"/>
...

I downgraded to 3.2.12 and I continued to see missing package errors -- this time with themes. I deleted \library\Noesis and that fixed the downgrade. So now the question is -- did the upgrade to 4.0 RC1 fail because of existing files in \library\Noesis?

Just to understand this a bit more. In a new package, with a clean installation, is this happening?

Here are the steps.

• Using the package manager, I uninstalled Noesis 3.2.12 from an existing Unity project, Stellar Conquest.
• I added the package for 4.0 RC1 using the package manager "Install From Disk" option. I received the errors shown above, and errors related to #5177.
• I uninstalled Noesis 4.0 RC1 from the package manager.
• I installed Noesis 3.2.12 from the package manager.
• I received new missing package errors for Noesis Themes.
• I closed Unity and reopened it. No change.
• I deleted \library\Noesis and that fixed package import errors in Noesis 3.2.12 and I'm back up and running under 3.2.12.

Does Noesis need to delete files in \library\Noesis when version changes occur?

Issues:

• The /Packages/... syntax is still supported
• The patch in 0005167 fixes the issue of incompatibilities between 3.2 and 4.0. With the new patch, you should be able to move between 3.2 and 4.0 without problems (you will have to delete /Library once after applying the patch).

If this error persists

Can't open Packages/com.noesis.noesisgui/Runtime/API/Shaders/CrossFade.noesisbrush

I am going to need the callstack of that message.

Thanks for helping!

OK, I'll retry with the updated source and reply back.

I uninstalled 3.2.12.
Closed Unity.
Deleted \Library\Noesis.
Installed 4.0.

NoesisGUI v4.0.0-rc1 successfully installed
UnityEngine.Debug:Log (object)
NoesisUpdater:CheckVersion () (at E:/Source/StellarConquest/StellarConquest.Utilities/Noesis/4.0 RC1/Editor/NoesisUpdater.cs:46)
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()

I now have 15 Noesis errors instead of 999:

Assets/User Interface/Screens/Game/Overlay/Spedometer/SpedometerControl.xaml(15,9): Xaml not found 'Assets/User Interface/Controls/Radial Range Control/RadialRangeControl.xaml'
UnityEngine.Debug:LogError (object,UnityEngine.Object)
NoesisPostprocessor/<>c__DisplayClass4_0:<Update>b__1 (string) (at E:/Source/StellarConquest/StellarConquest.Utilities/Noesis/4.0 RC1/Editor/NoesisPostprocessor.cs:120)
Noesis.GUI:LoadComponent (object,string) (at E:/Source/StellarConquest/StellarConquest.Utilities/Noesis/4.0 RC1/Runtime/API/Core/NoesisGUI.cs:373)
StellarConquest.Presentation.Unity.UI.RadialRangeControl:InitializeComponent () (at Assets/User Interface/Controls/Radial Range Control/RadialRangeControl.cs:208)
StellarConquest.Presentation.Unity.UI.RadialRangeControl:.ctor () (at Assets/User Interface/Controls/Radial Range Control/RadialRangeControl.cs:203)
(wrapper dynamic-method) object:lambda_method (System.Runtime.CompilerServices.Closure)
Noesis.Extend:CreateInstance (intptr,intptr) (at E:/Source/StellarConquest/StellarConquest.Utilities/Noesis/4.0 RC1/Runtime/API/Core/Extend.cs:6249)
Noesis.GUI:LoadComponent (object,string) (at E:/Source/StellarConquest/StellarConquest.Utilities/Noesis/4.0 RC1/Runtime/API/Core/NoesisGUI.cs:373)
StellarConquest.Presentation.Unity.UI.SpedometerControl:InitializeComponent () (at Assets/User Interface/Screens/Game/Overlay/Spedometer/SpedometerControl.cs:48)
StellarConquest.Presentation.Unity.UI.SpedometerControl:.ctor () (at Assets/User Interface/Screens/Game/Overlay/Spedometer/

I'll apply the patch and try dependencies.

I am definitely able to get further with the upgrade! I can see other users being impacted by stale data in \library\noesis -- the errors thrown are definitely confusing.

I started working through the dependencies. If I am understanding the scope of the change, it is a significant body of work.

I have to roll back the upgrade to complete other work. I'll try again when I have a large block of time to address the dependencies requirement.

OK to close issue.

Closing this, let's continue in the other one.