With version 13.611 it should not have this issue any more (and hopefully still work if you'd saved it with the new numbers instead of booleans)
By the way - either "false" or "true" would have resulted in the program reading "0" because it was (incorrectly) expecting an integer value in the XML, not a boolean. So, scaleFilter=1 should have meant true and 0 should mean false.
Doesn't matter any more since the xml should now be back to saying "true" or "false" as intended!