Search Issue Tracker
Active
Votes
1
Found in
2019.4
2020.3
2020.3.9f1
Issue ID
1399139
Regression
No
MRTK controls don't work when used in build
Reproduction steps:
1. Open the user's attached project
2. Enter Play Mode and move sideways with "A" and "D" keys.
3. Navigate to "MoveLeft_H1" or "MoveRight_H2" Button and press it a few times
4. Exit Play Mode
5. Build and Run the project
6. Repeat 2-3 steps
Expected result: You are able to navigate and interact with the Scene in the build
Actual result: You aren't able to navigate and interact with the Scene in the build
Reproducible with: 1.0.2 (2019.4.38f1, 2020.3.33f1), 1.3.0 (2019.4.38f1, 2020.3.33f1)
Could not test with: 2021.2.19f1, 2021.3.0f1, 2022.1.0b16, 2022.2.0a10 - MRTK errors: "Use of unassigned local variable 'colliderByTransform'" etc.
Notes: Controls work in Play Mode but not in build.
Reproducible in Standalone and WebGL builds.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment