maelstrom | High performance Matrix Home Server in rust | Math library

The problem is that you are are confusing INotifyPropertyChanged with INotifyCollectionChanged.

A multi-binding is only updated if one of the properties in one of the bindings issues an INotifyPropertyChanged.PropertyChanged event. In other words, if the entire collection underlying Textures or GameObjects was completely replaced with a brand new instance of ObservableCollection

But that's not what happens when you add/remove items to/from an ObservableCollection. In that case, the property that returns that collection object does not change at all; The very same ObservableCollection object remains. But the collection itself raises the INotifyCollectionChanged.CollectionChanged event.

The only way that WPF can react to this is if some object is monitoring that specific ObservableCollection object for INotifyCollectionChanged. And that cannot possibly happen when you use it in a MultiBinding because the ObservableCollection gets lost in the conversion. The MultiBinding returns one single value and whatever that value is, it's not any object that implements INotifyCollectionChanged.

You might want instead to look into the CompositeCollection class. That might be a better approach