It's an issue I've introduced with v3.11 and I'm glad the update to the latest Development Build fixes the issue for you.