A little update. I have been trying to find the root cause for that, but for now I only was able to determine that some Field Notify Setters seem to trigger this issue. Interestingly enough is that those seem to work sometimes and other times not. E.g. my GenericEnumSelect has it’s SelectedOption value bound by several parent widgets, but only one is causing the issue.
My current workaround is creating the FieldNotify binding manually:
I already tried most of the usual stuff btw: recreating the asset with the issue, deleting cached data from both the engine and the project cache, trying to wrap the asset in another Widget, etc. and I am running out of ideas. It would be great if someone could tell me, whether this is the intended behaviour or if it is a bug in the MVVM system. As for now I’ll have to refrain from using it sadly due to the less than optimal developer experience.