Hey @3LiON
We’re aware of this issue and it’s fixed internally, coming out in update 2.6 most likely.
Thanks for the feedback.
Hey @3LiON
We’re aware of this issue and it’s fixed internally, coming out in update 2.6 most likely.
Thanks for the feedback.