This is reproducible in a NoMask scenario.
Hi, The observed issue is fixed in our official version – R3 2018. Best regards, Ralitsa Kumanova