InputField issue in standalone build on linux

Text input fields work correctly in editor and in stand alone windows builds from my Unity 2017.3.0f1 installation on Ubuntu18.04, however when I run a standalone linux build and type in any InputField every key entry is duplicated.

Edit:
When testing further if I try to type in capital letters in the input field only one of the inputs for each key-press is in capitals ... e.g. pressing Shift + F results in fF displaying in the input field.

 

I just came to the forums looking for a solution to an identical problem. Seeing the behavior using a TMP_InputField.

 

Unluckily, I have the same problem on Ubuntu 16.04, I'm using Unity 2017.3.0f1, and I have tried compiling my project using Unity 2017.3.0f3 windows version, but it still doesn't work.

 

I just downloaded Unity 2017.3.0p2 and test it, but the problem still existed.
And I found another problem about input filed on Ubuntu 16.04: I can't input Chinese using fcitx input method, both in editor and executable program.

 

The bug is marked fixed, but only in 2018.1 beta? Does that mean there is no stable version of Unity where it's actually fixed? It's a pretty serious bugfix to leave out of the recent 2017.4.

 

Any updates on the status of this fix? Is it available in any version of Unity yet? 2017.4, 2018.1?

 

I have the bug with Unity 2018.1.0b13

 

Any updated news about this? I haven't seen this fix in a patch yet.

 

Hello, any updates on this? My game requires user input, however problem mentioned above still exists.

 

Any chance this fix is in 2018.1.3f1 and missed the notes like 2017?

 

Ok, thanks a lot for the update!

 

I have initial reports from our QA team that a Linux standalone build on 2017.4.4f1 (which I assume should have the fix since 2017.4.3f1 is supposed to) did not fix our input issues. I will see if I can get more details, have you heard of any others saying this fix didn't work?

 

Yeah, we are still having issues. Our game has some standard third-person MMO style controls. You can strafe right/left with A and D for example. One symptom is if you hold down either of those keys for about 5 second and then left go, it will continue strafing that direction for quite a while, and if you try to hit the opposite key, it's ignored for a while as well. It's like the input is buffered and continued for much longer than it should be.

I can get a more technical explination / details if needed, but Linux input issues are not fixed for us.

I thought this bug was marked as fixed, but now it looks like it isnt?

https://issuetracker.unity3d.com/is...ot-getkey-changes-values-while-key-is-pressed

 

Sorry, more info, it is Ubuntu 15.10 that we have this issue on, which I think is technically older than Unity officially supports, we don't have the issue on 16.04. We can open up testing to a wider user base to see who else experiences this.

Edit: Actually, we upgraded that machine to a clean 16.04 and it still has the issue. Inputs work fine on Unity 2017.2 builds, but not 2017.4 builds (both using latest patches.) Not sure what the issue is, some hardware difference?

 

Ok, the latest clue is that it is related to framerate/performance. We were able to reproduce on the machine that wasn't having the issue by reducing the framerate (the other machine that has the issue always runs the game slow because it is older.) At ~60 fps, input seems fine. At ~30, it starts to get delayed a bit, 25 or below, it's very noticeable, it's like input buffers up and all movement controls are delayed. The lower the framerate, the more delay and buffering. This doesn't happen in our game on Windows, and doesn't happen in Unity 2017.2 linux builds, but does happen in Unity 2017.4 linux builds.

 

Ok, I've created a new bug report, using the example Unity project that ships with the Unity installer. The Unity issue number is 1049679

 

The bug is now public, please vote on it https://issuetracker.unity3d.com/is...or-linux-standalone-builds-with-low-framerate

 

@Schubkraft can we get an update on the status of the fix for the 2018.1 branch?
A major issue rendering a whole desktop platform unusable for this long doesn't seem like an improvement to the QA process claimed last year

 

Cool, thank you
Any details on when it might hit public? 2018.1.8 already?

 

Thank you, Schubkraft

 

More or less the same story in 2018.2.2
In a simple UI input field pressing left shift results in a special character |
using the right shift prints a j like character.
So all attempts at an uppercase letter result in an extra character. You can delete the character, but it's entirely unintended.

I don't see the keys being held down improperly though.

 

I saw a staff member saying 2018.3 was "before the end of the year" I assume 2018.4 is after that? Are there any suggestions how we can go about working around this? I suppose scanning the text for the characters OnValueChanged and removing them?

 

Any news? An update is sorely needed to fix the "shift printing characters in Linux" thing.

 

So now we are 1.5 years later and this bug is still present in 2019.1. Can we get a fix already pretty please?

 

I'm talking about the bug where when you enter text into a GUI.Input it gets duplicated, so when you want to type 'hello' it actually enters 'hheelllloo'. I thought this was only occuring with the old GUI inputfields, but upon testing I saw it also happens with the InputField in a UI Canvas. I'm using 2019.1.0f2 on Linux Mint 18.2. This Unity version is the most stable I found, but the bug I'm describing makes it impossible for me to make even a very basic UI with text inputs. I must note I haven't made a build to see if it happens there too, I'm experiencing this in playmode while in the editor.

 

When I make a build the input works normal, but in the editor it's a serious problem. I work around this by manually polling input events and checking which key is pressed, then set the text in the inputfield, which is far from ideal from a development point of view.

 

I can confirm this issue is solved in 2019.3.0a12

 

Unity Linux version "Inputfield" cannot input Chinese