4.0.0rc3

• [Unity] Auto mode in AssetDependencyAttribute to calculate paths automatically.
• [Unity] Implemented NoesisUnity.LoadComponent using AssetDependencyAttribute.
• [Unity] XamlImporter: less aggressive caching algorithm to allow movement of type assets.
• [Unreal] Set Studio View tessellation quality to High, and enable PPAA and LCD flags.
• Fixed: Mouse input get stuck when selecting a Combobox Search result.

4.0.0rc4

• Inspector: Added editable combobox for target selection.
• Fixed: LayoutScaler and RadialNeedle returning Infinity in MeasureOverride.
• Fixed: Win32Display not respecting NoResize mode in mouse capture callbacks.
• [Unreal] Samples added: CustomControl, Menu3D.
• [Unreal] Enabled gamepad (Enhanced Input Actions) on all Unreal samples.
• New Inspector document.

4.0.0rc5

• DragDropExtensions ported to C#.
• Potential out-of-bounds memory access in SVG::Parse.
• [Unity] Added Inventory sample.
• [Unreal] Make sure the AssetImportData hash is valid when importing XAMLs (#5170).
• [Unreal] "Add to Viewport" sets up the EnhancedInput mappings.

After the Upgrade to Noesis 4.0 we started seeing an assert on shutdown.
It seems to come from NS_SHUTDOWN_PACKAGE(Gui, Core), where it calls UI::Shutdown(), which in turn will try to free gTheme. It's the validation that creation/deletion happens on the same thread, and the first call to UI::GetTheme() tends to happen when we first create a view, which we do on the Noesis thread.
I have a temporary workaround to call UI::GetTheme() in NS_INIT_PACKAGE(Gui, Core). Not sure if this is your preferred solution, or if we are missing some initialization call in our integration backend?

Edit: Sorry, my proposed solution does not work. It instead causes the same asserts when creating views, presumably because it's trying to read the default style (now created on main thread).
Moving the call to GUI::Shutdown() to NoesisThread also causes the assert, but now coming from VisualTreeInspector::Shutdown();

After the Upgrade to Noesis 4.0 we started seeing an assert on shutdown.
It seems to come from NS_SHUTDOWN_PACKAGE(Gui, Core), where it calls UI::Shutdown(), which in turn will try to free gTheme. It's the validation that creation/deletion happens on the same thread,

That threading validation is just emitting warnings that can safely be ignored. I recommend building with NS_MULTITHREADING set to 0 until we provide a better solution for this. Could you please provide more information about the assertion?

Unity and Unreal guides updated to 4.0

4.0.0rc7

• Added Welcome screen to Unity and Unreal
• Fixed: Issue with disappearing nodes in Inspector
• [Unreal] Added new samples: Inventory, Menu3D, TicTacToe
• [Unity] Added new samples: Inventory, UserControl and Rive
• [Unity] Add info dialog about GlobalResources.xaml on studio project creation

The official 4.0.0 release is already out.

Closing this topic. Please continue the conversation in new topics.