Apologies for the late answer - as you found out adding the extension in the FX file solves the issue. However this was not intended and we have fixed this bug today on our development branch. I believe the fix will be part of an update scheduled to be released in December - but I don’t have a firm date yet.
Best regards,
Eric / Asobo