Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.3.0-pre.1
Issue ID
XRIT-40
Regression
No
On WMR characters chosen on virtual keyboard do not appear in text field
+Synopsis+
One of the test stations in the VR scene from XR-Interaction-Toolkit-Examples-Internal includes a text field. On Quest One when I selected the text field, a virtual keyboard appeared. I typed on the keyboard and the characters appeared in the field. However, when I do the same thing on my Windows MR HMD, no characters appear in the text field.
+Configuration+
Unity 2020.3.44f1
XRI 2.3-pre.1
Scene = XR-Interaction-Toolkit-Examples-Internal/VR/Assets/Scenes/WorldInteractionDemo
Build Settings = UWP
XR Plugin Provider = WMR
Acer Windows MR HMD
Universal RP
+How to See the Bug+
If you have trouble seeing this bug using your own local repo, my project is attached in case this turns out to be specific to my settings.
If your project path is to long then you will get build errors. I ran my test from c:/VR.
Using Unity 2020.3.44f1 open the WorldInteractionDemo scene.
Verify Build Settings and Project Settings per Configuration above.
Build and Run on your Windows MR HMD.
Navigate to the text field and select it.
When the virtual keyboard appears, type on it using the hand controllers.
No text appears in the text field; this is the bug.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leaks when Instantiating Objects with SerializeReference
- Currently selected Action Map switches to the first Action Map in the list and it's first Action when editing the Binding Path of a newly created Action
- "F" default focusing Unity shortcut zooms out when the first time focusing the GameObject
- DropdownField options added with PointerDownEvent are not shown when clicking the DropddownField for the first time
- References are reset to "None" when opening the project
Resolution Note:
The Windows Mixed Reality plugin is no longer supported by Unity, please migrate to the OpenXR plugin for proper support of this behavior.