Closed anderium closed 2 years ago
not a mac user so i can't really suggest anything, but the attached log statements about ButtonSystem
are not related. more information about what input devices you're trying with and what your regional settings are (system language, keyboard layout) may help.
if the game crashes again please attach logs immediately after the crash (without starting the game again, as they will get overwritten).
I was using Japanese Romaji as input system on my built-in keyboard. Changing to "ABC", which is supposed to be the same, solves the typing issue! Thanks a lot! (And my system language is set to Dutch, btw)
As for the logs, I made sure not to start osu! again, but they weren't crashes. I quit the game normally after trying to type.
I tried opening from launchpad again and it crashed again… I think it just cut off the logs without anything special appearing in them: database.log, performance.log, runtime.log
The crashing seems unrelated to being unable to type, and might be related to the issue I linked earlier, or #7791.
Likely fixed since merge of IME support in framework: https://github.com/ppy/osu-framework/pull/4907
Let's close for now.
Hi, I'm a new osu! player and thought I'd use lazer immediately, but I ran into a bug:
When opening osu! I usually can't type in the textboxes. Pasting text with
cmd+V
and other shortcuts do work. So do the backspace and escape buttons (and I presume other special buttons).osu!lazer version: 2021.907.0.0 on .NET 5.0.1 macOS X version: 10.14.6 Mojave MacBook Pro: 13-inch 2017, (probably) retina display, Intel 1536 MB video-card. Apple claims I have 2 8GB cores, but most software, including osu!, detects 4 cores.
I've tried opening osu! in 4 different ways (logs seem identical except for timing):
Double-clicking the app icon in Finder/Desktop. Nothing seems weird in the logs to me: database.log, network.log, performance.log, runtime.log Video on YouTube. (It's impossible to see, but I'm trying to type before pasting
hello world!
)Clicking on the app icon in the Dock. (Behaviour seems identical to method 1.) Again, nothing seems weird in the logs to me: database.log, network.log, performance.log, runtime.log Video on YouTube.
Using Spotlight to search and then open osu!.app. (Behaviour seems identical to method 1 and 2.) Again, nothing seems weird in the logs to me: database.log, network.log, performance.log, runtime.log Video on YouTube.
Using launchpad, this used to crash osu! first, while opening it on the second try. Now that I want to reproduce it, though, it seems to open osu! as the others, keeping me unable to type… With this method, I experienced something similar to #12323 when opening for the second time. osu! didn't become visible by itself, but I could make it visible by clicking the app icon in my dock. Using this method typing became possible.
Even though what I described here seems to happen most often, I've had osu! crash with method 1-3 and it only crashes half the time with method 4.
Perhaps osu! doesn't realise it becomes active when opening?
And lastly something I noticed was that most of the logs contained the following:
Whereas a few others, I don't think I uploaded them, didn't switch back to
Initial
afterTopLevel
:These cases still seemed to have the typing problems, sadly.
If I find a workaround or I can reproduce what happened with method 4 again, I'll try to update this!