I'm more confused than anything at this stage, I have no idea what caused it to throw errors in the first place. The only reasonable explanation I can find (apart from a bug here, that's what I am trying to figure out) is that first time you tried you didn't use the namespace in the XAML. That coul...

Sure, this is how my XAML was set up... <UserControl x:Class="UI.PlayerHud" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/200...

It would appear that was the problem, the namespaces were set up correctly but weren't respected in the conversion process I guess?
Changing the name of my type fixed the issue though, thanks!

I've been trying to come up with a working solution for piping converters, I've been through everything and decided to just fall back to a generic approach for specific converters. public class BooleanConverter<T> : IValueConverter { public BooleanConverter(T trueValue, T falseValue) { True = trueVa...