This issue could be related to:
which was not fixed in 2021.1. so anybody still using 2021.1 will have to upgrade.
The issue was fixed in 2022.1 in build 2022.1.0.2483. @koki can you confirm, that you have build 2483 or later?
1 Like