We're using multiple Noesis Views, some in screen space, and some with WorldSpaceUI set.

In the elements using the NoesisWorldUI component some XAML changes hot reload while others do not. Specifically, it looks like anything in the NoesisWorldUI view will hot reload, but anything in a DataTemplate within a ResourceDictionary referenced by that main view will NOT hot reload.

We're using un-keyed DataTemplates, and MergedDictionaries, so there are no StaticResource bindings to get in the way. We have also disabled and re-enabled the GameObjects holding the NoesisWorldUI, however the old XAML is still used until we exit playmode and re-enter it.

Is there any way to force a reload of these files/elements?

[edit] This actually looks like it happens in Noesis Studio as well, so unrelated to NoesisWorldUI and probably related to DataTemplates, ContentPresenters, or DataTemplates inside ResourceDictionaries presented in ContentPresenters.

Hi Jesse,

Effectively, this issue isn’t related to WorldSpace UI, it seems to be specific to how Templates are handled.

Do you think you could reproduce this with a single, simplified XAML file? That would help us narrow down the problem.

I filed a bug report: https://www.noesisengine.com/bugs/view.php?id=4449
And created a minimal repro: https://github.com/JesseOlmer/Noesis-Bug-HotReload

This issue partially manifests in Studio as well, though not as severely as in Unity. Details are in the github readme.

Thanks for the ticket and the awesome report!