Search Issue Tracker
By Design
Won't Fix in 4.2.X
Votes
0
Found in [Package]
4.2.1
Issue ID
XRMB-23
Regression
No
[InputSystem] InputSystem.onDeviceChange is not called in runtime
Reproduction steps:
1. Open the attached project ("ca1263946se.zip")
2. Open "VRScene" scene
3. Enter Play mode and look around with HMD
4. Observe that Information is printed in front and in the right
5. Build and Run the project
Expected result: Information is printed in front and on the right of the HMD
Actual result: Information isn't printed
Reproducible with: 2019.4.12f1, 2020.1.9f1, 2020.2.0b7, 2021.1.0a1
Could not test with: 2018.4.28f1 (XR SDK not available)
Tested with:
- Oculus Rift
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note:
The InputSystem.onDeviceChange event behavior between Editor Play Mode and built executables is not consistent due to the way Input System operates. The onDeviceChange event is indeed invoked in both, but only on built executables, the event isn't invoked after script initialization (ie Awake method). From XR perspective, this is working as intended. If the behavior would change, it would require work from Input team instead.
Resolution Note (4.2.X):
The InputSystem.onDeviceChange event behavior between Editor Play Mode and built executables is not consistent due to the way Input System operates. The onDeviceChange event is indeed invoked in both, but only on built executables, the event isn't invoked after script initialization (ie Awake method). From XR perspective, this is working as intended. If the behavior would change, it would require work from Input team instead.