Search Issue Tracker
Duplicate
Votes
2
Found in
2017.2.0f1
Issue ID
954044
Regression
Yes
Crash in UnityEngine.XR.WSA.Input.InteractionManager:Initialize
Steps to reproduce:
1. Open the attached project
2. Open the Crash scene
3. Switch platform to WindowsStandalone (or Windows Store, if you have Red Stone 2 installed)
4. Play the scene
5. Observe the native crash
Actual results: Unity crashes
Expected results: Unity crashes
Reproduced with: 2017.2.0f2, 2017.3.0b2, 2017.3.0b5
Not reproduced with: 2017.2.0b10
Regression introduced in: 2017.2.0b11
Comments (3)
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- 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
camerontynespnnl
Jan 02, 2018 17:43
This is still an issue with 2017.2.1f1
initializing the event in any method causes a crash.
PhilipKeenanPhilips
Dec 11, 2017 16:58
Still having issue
solidsnake530
Oct 20, 2017 10:33
I am having the same issue in 2017.2.0f3 and 2017.2.0f3 MRTP.