-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
android. keyboard bugs #31391
Comments
Next time you record a video, try to record in horizontal (by start recording in horizontal), so that the game screen is not squashed like that. And also, upload the video directly to github, or use a more proper format, not Youtube Shorts. For now, others trying to work on this can view the video with normal YT player at https://www.youtube.com/watch?v=iKUzJoTEseA Either try to zoom in, or download the video, etc. |
there was a problem with uploading videos to github, I uploaded a horizontal video to YouTube |
Can you elaborate a bit more on this? For example,
|
sorry for the word bacchanalia (Russian word, didn't think it was not in English). I also encountered the fact that when pressing enter on the keyboard, the previous message is sent, although the message is not typed. It is not possible to repeat this, but it is captured on the first video Screenrecorder-2025-01-02-13-04-08-436--online-audio-convert.com.mov |
Type
Other
Bug description
the bug is related to the keyboard in the laser osu. for unknown reasons, a bacchanalia occurs when trying to write the second and subsequent messages without hiding the keyboard
ps. I believe that such a bug occurs not only in the multiplayer chat, but also in the map search, the search for a multiplayer room by name, in general, everywhere where you can only write text
Screenshots or videos
https://youtube.com/shorts/iKUzJoTEseA
Version
2025.101.0
Logs
1735812739.runtime.log
1735812739.performance.log
1735812739.network.log
1735812739.input.log
1735812739.auth.log
1735812261.runtime.log
1735812261.performance.log
1735812261.network.log
1735812261.input.log
1735812261.auth.log
The text was updated successfully, but these errors were encountered: