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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment