Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.0.0f1
Issue ID
671095
Regression
No
British keyboard inputs are not registered correctly in the Editor
How to reproduce:
1. Enable additional languages in the input settings for your Operating System
- there should be a U.S. layout as well as a British layout (neither of them should be International)
2. Open a new Unity project
3. Create a new C# script named "InputTest" with the following code:
using UnityEngine;
using System.Collections;
public class InputTest : MonoBehaviour {
bool button;
void OnGUI()
{
GUILayout.Label ("Pressing button: " + button.ToString());
}
void Update ()
{
if (Input.GetButton ("Jump"))
button = true;
else
button = false;
}
}
4. Attach the script to anything in the scene
5. Switch to the British keyboard layout (http://www.goodtyping.com/teclatUKok.png layout for reference)
6. In Project Settings -> Input find the "Jump" axis and change the Positive Button from "space" to the apostrophe (')
7. Play the scene
- Make sure the layout is still British
8. Press the apostrophe
- Note how the text stays False
9. Press the backslash(\)/vertical bar(|) key (on a US keyboard) or the hash(#)/tilde(~) key (on a UK keyboard)
- Note how the text changes to True
The hash(#) button is unbindable. Setting the Positive Button in step 6 to "#" results in no button working for that Input (not even Shift+3). This is also the case on OSX.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment