Hi o1ek, if you're on the Windows build, v0.41b was just added which fixes this issue! Apologies for the inconvenience and big thanks for reporting this :)
I will also write and announce the update notes for v0.41 soon.
Thank you. 41b fixed the issue )
