It looks like the frame is getting corrupted in some way, which I would expect to be closer to a Rosetta 2 bug. Can you make a step-by-step process that reliably produces this? I can try on my Intel Mac to see if it's something involving a locale change regardless of CPU architectures.

引用自 flibitijibibo：

It looks like the frame is getting corrupted in some way, which I would expect to be closer to a Rosetta 2 bug. Can you make a step-by-step process that reliably produces this? I can try on my Intel Mac to see if it's something involving a locale change regardless of CPU architectures.

1. Launch the game.
2. Press «Globe/fn» button to switch language.
3. Graphic crashes.
P.S. Sometimes it fixes with same way as I create it.
Link 1: Works well: https://youtu.be/MrLIsfbfZk0
Link 2: Graphic crashes: https://youtu.be/OeKXYlWaC7k

Got it, thanks for the steps! Upon closer inspection this function key is unique to M1 MacBooks, so it may take time to be able to reproduce (I don't have the hardware available). But, if I were to take a guess, the engine doesn't like when the OS switches languages during runtime. We do have a language option in the options menu though, for what it's worth!

I'll see if the locale change is a multiplatform issue and report back if so!

引用自 flibitijibibo：

Got it, thanks for the steps! Upon closer inspection this function key is unique to M1 MacBooks, so it may take time to be able to reproduce (I don't have the hardware available). But, if I were to take a guess, the engine doesn't like when the OS switches languages during runtime. We do have a language option in the options menu though, for what it's worth!

I'll see if the locale change is a multiplatform issue and report back if so!

Thank you! I’ll wait! Please, keep me in progress here. Good luck! And another request: can you fix a issue when game works only on english keyboard but don’t with others, like on this video: https://youtu.be/qAvF56D5mrM
It was the first reason why I pressed the function key when game launches.

This might be because of keyboard layout - I believe the engine assumes QWERTY and doesn't try to map default keys based on the keycode, just the scancode. If you want input to be layout-agnostic, you can add /usescancodes:1 as a launch option and it'll always enforce QWERTY layout.

引用自 flibitijibibo：

This might be because of keyboard layout - I believe the engine assumes QWERTY and doesn't try to map default keys based on the keycode, just the scancode. If you want input to be layout-agnostic, you can add /usescancodes:1 as a launch option and it'll always enforce QWERTY layout.

Thank you for this advance! Good luck with fixing this graphic glitch!

引用自 flibitijibibo：

This might be because of keyboard layout - I believe the engine assumes QWERTY and doesn't try to map default keys based on the keycode, just the scancode. If you want input to be layout-agnostic, you can add /usescancodes:1 as a launch option and it'll always enforce QWERTY layout.

Greetings. Is there any progress in this case?

Nothing yet - when the core team pushes another update I'll get it in, but the scancodes option is still the best way to get around the issue.

引用自 flibitijibibo：

Nothing yet - when the core team pushes another update I'll get it in, but the scancodes option is still the best way to get around the issue.

Thank you for answer! Now it works quite well. But today I opened the game through Steam Big Picture. Glitches had back... Reopened without Big Picture – no glitches...

Hello! I've just discovered: if I turn the game with glitches into window view from full screen, glitches disappears.

Hello! Still nothing?

Yeah no update yet. I was expecting an update sooner but it's still in development. I'll post when it's out!

引用自 flibitijibibo：

Yeah no update yet. I was expecting an update sooner but it's still in development. I'll post when it's out!

Thank you!