hi，@christophen @gchiste do you have any update information for this problem?

Same problem. Anyone know if it will be fixed on 16.1?