1.19.50 did not do anything for keyboard control on iPhone.
The mouse cursor still flies around the screen
the mobile controls sometimes appear for no reason.
the cursor does not work in menus, inventory, or really to click anything but blocks.
when you go out of the inventory after using your finger To move objects around, the camera stops responding to the mouse.
plus a load of other bugs.
please fix this Mojang
Since 1.19.40 is now officially out, I want to write an update with the keyboard and mouse support.
Note: This only pertains to iPhone. As I do not have an iPad, I cannot test it on iPad, but from another recently added comment, it works much better on iPad. This is a report for the iPhone version.
At first inspection, there has been some improvement in 1.19.40. Menus and inventories still can’t be accessed, but now you do not have to turn on Split Controls in Touch Settings to see and use the crosshairs (previously, even though the crosshairs sometimes appeared, you could not place or break blocks without Split Controls turned on). There are other aspects of keyboard gameplay that I have not yet tested, but overall that seems to be the only improvement. As I mentioned before, the menus and inventory still cannot be used with the mouse. Also, the mouse cursor does not lock at the center of the screen or disappear as it should when in mouse mode. This results in accidentally closing the game when clicking on the home bar after looking down, and clicking at random parts of the screen will cause the touch controls to appear.
If i discover any other improvements or new bugs, i will make another comment for that.
The game has many many bugs when it comes to using kbm on iPhone. It seems like it works on iPad, but on iPhone.
Menus cannot be used (including inventories, settings, the main menu, etc).
The chat seems broken (you cannot press Shift otherwise it stops typing in the chat box).
The mouse does not stay centered on the screen, instead the cursor flies all around (which can cause issues in certain parts. Issues include clicking while the mouse is in certain areas brings up the mobile controls, and pressing the bar at the bottom of the screen [used to close the app] it will close without warning).
After using your finger to craft or control menus (as you need to do), you have to press and drag your finger across the screen and click the mouse in order to move the camera by moving the mouse (it becomes unresponsive otherwise).
Idk why it was marked as resolved but it isn’t
Sorry. I thought it would be simpler to just create a new one instead of editing the other. I have updated the original issue report with the bug list. Should I delete it?
Here’s an updated video talking about the bug:
https://youtu.be/78Vrs_rc5Oo
I did that and it didn’t do anything. The mouse still doesn’t work to click anything but attacking/destroying and use item/interact with stuff like doors.
Can confirm. I’m on an iPhone 8 and it never ran Minecraft badly (it actually worked better than my friend’s Xbox). But since 1.19, it has lagged extremely bad. Chunks take ages to load, sounds load several seconds after they should, Framerate drops, and the game occasionally freezes. And to top it all off, I got disconnected from a friend’s world due to lag and when I loaded back in, my entire save file for that world had been lost (meaning inventory and levels vanished).
I know it says the issues are resolved up there, but they are very much not. I was playing just a few minutes ago, and chunks load so slowly to the point where I almost can’t go exploring anymore cause every 5 seconds I have to sit and wait 10 for the chunks to load
Seeing as others are having this same problem, it’s clearly not just my hardware, and hopefully Mojang cam fix the iOS version of the game, cause it’s close to unplayable with the lag I’m getting.
This happened to me recently in my main survival world (nearly a year and a half old). I think it’s linked to realism, cause I joined my friend’s realm and then left and joined the world. Upon leaving and rejoining, everything was normal.