Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0a5
2018.2.13f1
Issue ID
1099427
Regression
Yes
[HoloLens Remoting] XR.WSA.Input.InteractionManager works just on first remote session
Steps to reproduce:
1. Download 1099427_repro.zip
2. Switch platform to UWP
3. Enable XR support and WSA remoting
4. Build project
5. Open and build Visual Studios solution (x64, Local machine)
6. In HoloLens launch Holographic remoting player.
7. When app launches enter HoloLens IP and press connect button
8. Perform air tap motion. Notice sphere color changes
9. Disconnect and reconnect to HoloLens
10. Perform air tap motion. Notice sphere color doesn't change
Expected results: After reconnecting to HoloLens InteractionManager works as intended.
Actual results: After reconnecting to HoloLens InteractionManager stops working. Doesn't recognize tap motion.
Reproduced with: 2018.2.17f1
Not reproducible with:2018.2.0a5
Regression introduced in: 2018.2.0a6
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (2018.3.X):
We are no longer fixing issues in 2018.3. If your issues still occurs in Unity 2018.4 or Unity 2019.3 and greater, please re-submit your bug for consideration.