[MC-160715] The on-screen keyboard can no longer be used as of 1.13; the cursor centers itself regardless of location.

Ever since Minecraft version 1.13, I've been completely unable to play because of a change in how the game interacts with the cursor. Specifically, whereas I'm used to being able to have the cursor over Windows' On-Screen Keyboard and click keys that way (something I have to do in order to compensate for a disability), that no longer seems to be possible as it once was, because the cursor gets centered (in the process of "aiming" where Steve is supposed to look) regardless of its location on the screen. I've been told by various sources, including a prominent mod developer as well as one of your own support representatives, that this is likely due to the update to LWJGL3 that, among other things, defined some undefined behavior, but I still consider it a bug because it essentially "fixed" something that wasn't "broken", per se, in the process making the game unplayable for me.

Worth noting, this is a high enough priority issue to me that, were I a bit more competent with Java (and for that matter, programming in general... I'm a bit of a novice), I would attempt to write a coremod to override whatever part of LWJGL is causing this. As is, however, I'd probably end up making things worse and just crashing the game repeatedly. It's really a pity, considering a lot of the new content (bees, raids, etc.) looks really cool... please help 😞

What I expected to happen was...:
The mouse cursor would stay in place when it is over the on-screen keyboard, regardless of whether I'm in a menu or not. It used to work like this prior to 1.13, but according to sources including a prominent mod developer and your own support, this likely changed because of the update to LWJGL3

What actually happened was...:
Instead of the above, the mouse cursor resets before I can click any keys on the on-screen keyboard, making it completely useless and preventing me from being able to play due to my spinal cord injury.

Steps to Reproduce:
1. Load up any version of Minecraft post-1.13 release
2. open the On-Screen Keyboard that is built into Windows' "Ease of Access center"
3. Place the on-screen keyboard over Minecraft such that the Windows overlap
4. load up a world and try to click the WASD keys on the on-screen keyboard to move around (you won't be able to)

Attachments

crash-2019-09-08_08.26.03-client.txt

Comments 14

wobst.michael 2019-09-08T08:59:38Z

Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report (minecraft/crash-reports/crash-<DATE>-client.txt) here.

macks2008 2019-09-08T12:34:20Z

@miwob Done. It took a bit of finagling, both on account of my injury and because for some reason my physical keyboard won't send that keystroke combination. I had to hold F3 on the on screen keyboard (while the game was paused on account of the bug I'm reporting here, no less!) and have someone press and hold C on my wireless keyboard. It was quite the orchestration (story of my life sometimes...), but nonetheless, it's done 🙂

macks2008 2019-10-04T14:26:50Z

So on a scale of 1 to 10, how likely is this to get fixed, or at least looked at/worked on, in the foreseeable future? Don't get me wrong, I understand you have limited resources, but contrary to what you might think, this doesn't just affect me. Other people affected by this bug include but are not limited to: the other players on the private server I host, developers that receive 1.12 bug reports from me because that's the most recent version I can play on, and anyone I tell about how long it's taking to resolve this issue (a number that increases the longer it takes).
Edit: Sorry if I seem to be pushing this too hard, but to be fair, I've been dealing with this issue since 1.13 came out. The only reason it took so long to open an issue on here for it is that I thought one would have already been opened after I reported it to your email support and explained in great detail that "basically, I can't play". I don't like being obnoxious, but I also don't like bugs that sit for eternity and prevent me from enjoying all the new features you've been adding

macks2008 2019-10-07T17:49:46Z

This forge mod I found for 1.12 might have a piece of the puzzle to fixing this, but as it's for an older version of the game (before I started experiencing this problem), I'm not sure how applicable it actually is. Nonetheless, if/when you get around to trying to fix this, it might be worth taking a look, since it's open source and all: https://www.curseforge.com/minecraft/mc-mods/ungrab-mouse-mod

NeunEinser 2019-10-08T20:39:10Z

Wow, this is really unfortunate.
I find it amazing that you were actually able to play with a keyboard covering half your screen.

As Minecraft did actually improve quite a bit in terms of accessibility recently, maybe the developers will look into this at some point in the future.

Unfortunately, this will probably not be an easy fix, as it is, as you stated already, likely related to the library update.

4 more comments

NeunEinser 2019-10-09T12:39:36Z

Hey!

So, I couldn't help but looking into this some more.
I made a very simple Fabric mod that allows you to unlock your mouse at will, similar to the mod you linked here.

This does use a keybinding, and you will need to map a physical key to it, for obvious reasons. The default mapping is therefor middle click. This does clash with pick block.
If your mouse has more than the three default keys, you probably want to remap it to one of those, otherwise you will need to remap pick block to a virtual key on your keyboard.

When activating the free mouse movement, you won't be able to rotate your camera, but other inputs, like walking, are still registered. In order to move your camera again, you will need to click into the Minecraft window.

This should stay compatible in future versions, as long no major things change in the classes I edited.

Let me know if this works for you. And have fun playing again in the latest version!

Download and install Fabric (Vanilla if you are using the vanilla launcher): https://fabricmc.net/use/
Mod download (you only need the .jar file): https://github.com/NeunEinser/unlock-cursor/releases
Then simply put my jar file in the mods directory of your .minecraft folder.

macks2008 2019-10-11T14:27:43Z

Thank you so much @NeunEinser! Yeah, most people are surprised I manage to play with an on-screen keyboard, but I just drag it out of the way whenever it's in the way. I'm still not exactly good at fighting (or at least not moving around while fighting. I'd probably get crushed in PvP). Hopefully you're right on that, and that's what I keep telling myself and what people keep telling me "they've added lots of accessibility lately". I know enough about coding to know things like this are never easy (library updates, undefined behavior that you never knew was actually helping someone, etc. etc.), but I'm okay with that; I just want it fixed eventually, you know? Fingers crossed these mods can help them figure it out. In the meantime, at least I should be able to play again thanks to you!
I'm not too worried about figuring out a control that works for me. My trackball doesn't have a middle mouse button, but it does have two auxiliary buttons. Ironically, I normally have them disabled because I always end up accidentally clicking them (they are just slightly too close to the main buttons and I use the mouse with my palm) but... well, they are finally going to be useful. Alternatively or additionally, I could also set up a side button (we have accessibility buttons around here) or something with Dragon NaturallySpeaking (the speech to text software I'm using to type this. It's a bit slow to control the game directly but it could press a button for me), but the point is I have options.
Honestly the hard part for me will probably be figuring out how to use fabric, as its somewhat of a new thing from what I've heard. Is it compatible with Forge? I like a lot of mods that are currently only available for forge; If not, that's fine, just being able to play the latest snapshots is a relief. Thanks again!

NeunEinser 2019-10-11T19:45:27Z

Fabric basically does what Forge does, but since they work differently internally, Forge mods nor Forge itself are not compatible with it, unless the mod author explicitly provides a Fabric version (which essentially means writing everything twice, so it's understandable that many authors choose to not be doing that).
There is also things like OptiFabric which somehow makes OptiFine compatible with Fabric.

Installing Fabric is as easy as it as for Forge. Just download the version for the vanilla launcher and run it. The setup will install Fabric and create a new profile/installation in your launcher.

Also, @unknown just set the priority of this ticket to important, so fingers crossed they fix it during the 1.15 snapshot phase 🙂

macks2008 2019-10-15T17:25:33Z

Good news: my problem only happens if raw input is enabled in Options> Controls> Mouse Options. As such, this might not be as high a priority issue as I initially thought, since disabling that seems to allow me to use the On-Screen Keyboard normally. I don't know how I missed this setting until now (I suspect it was added sometime between last time I looked for mouse settings to help and now. I know for a fact it wasn't there in 1.13 when I checked the first time), but someone on the Forge Project's discord suggested trying it, so I did.
All that said, there might still be an underlying issue that caused this to start happening… I'm just not sure what exactly. Perhaps that setting, at least until this is fully resolved, should default to OFF? What does it even do, anyway?
In any case, I'm very happy to be able to play the game without modding again (even if it's so I can subsequently add 100+ forge mods...). Back to being a happy player 😃

As an aside, while playing around with the snapshot, I noticed it no longer seems to recognize the state of numlock, so I can't use my numpad as arrow keys... it just sees them as numbers, which means I can either have 2, 4, 6 and 8 control my movement (as I normally do with the numpad versions of those numbers) or my hotbar (as I normally do with the normal number keys across the top of the QWERTY). Amended: it just displays ambiguously. It still recognizes the numbers as separate numbers. Furthermore, while I would normally resolve this with a fairly simple AutoHotkey script (I use AutoHotkey to remap a lot of my keys), none of that seems to work on this version. Even my previously-functional remap of vk0C::Space seems to break on the snapshot... So I might have another issue to report. Shall I go ahead with that in a separate ticket?

NeunEinser 2019-10-15T20:27:38Z

Yes, please make new tickets for separate issues.

macks2008 2019-11-17T18:27:36Z

Just to clarify/summarize, this issue is at least partially resolved for Java Edition (JE) because I can disable raw input and it stopped happening, but I have the same basic problem on Bedrock Edition for Windows 10. Is there a way this can be linked so it shows up on the BE tracker?

NeunEinser 2019-11-17T18:42:10Z

It might also depend on the operating system for JE.
Bedrock Edition is separate from Java and has its own ticket numbers and a different development team. Because of this, issues that happen in both editions have to be tracked in separate issues. So please create a new ticket for the Bedrock Edition.

macks2008 2019-11-19T19:07:09Z

understood and done: BE issue #57264

Avoma 2021-01-06T10:48:47Z

Can confirm in 20w51a.