Search Issue Tracker
Not Reproducible
Not Reproducible in 1.12.X
Votes
1
Found in [Package]
1.12.0
Issue ID
ISXB-1369
Regression
No
[InputSystem] The isTracked control reports a value of 0 when system language is set to Turkish
Steps to reproduce:
1. Download and open the attached user's project "UnityInputSystemCultureBug.zip"
2. Set system language to Turkish in Windows Settings
3. Connect a Quest 2/3 device and enable Meta Link
4. Open the Input Debugger (Window > Analysis > Input Debugger)
5. Enter Play Mode
6. In the Input Debug window, double-click on HeadTrackingOpenXR to show details
7. Notice there are two controls for isTracked: "ıstracked" (no dot on the i) with the expected value (1 when HMD is tracking, 0 when it is not) and "isTracked" with the default value (0) no matter what
Expected results: An input action bound to isTracked has a value of 1 when the HMD is tracking and 0 when it is not
Actual results: The input action bound to isTracked always has the default value of 0 (See attached "Results.png")
Reproducible on: Input System 1.12.0 (2022.3.56f1, 6000.0.36f1, 6000.1.0b4, 6000.2.0a1)
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Notes:
-Can be fixed by replacing "featureName = featureName.ToLower();" with "featureName = featureName.ToLowerInvariant();" in Library\PackageCache\com.unity.inputsystem@1.7.0\InputSystem\Plugins\XR\XRLayoutBuilder.cs. This makes the InputAction bind properly and shows only an "istracked" control in the Input Debugger.
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Not reproducible with Input System 1.14.2
Resolution Note (1.12.X):
Not reproducible with Input System 1.14.2