Yes, it’s probably related to a rare issue in one of the third party libraries we use, potentially caused by buggy bluetooth drivers. I can try to disable/remove the code triggering this, as the game shouldn’t use it anyway, but it’ll be a bit of work. Hopefully with the next update.
