Search Issue Tracker
Third Party Issue
Third Party Issue in 1.8.X
Votes
0
Found in [Package]
1.8.0
1.8.1
Issue ID
OXRB-196
Regression
No
Crash on "Microsoft::Holographic::AppRemoting::Timestamp::Timestamp" when entering Play Mode with Holographic Remoting for Play Mode enabled
How to reproduce:
1. Open the attached project "hand-tracking-with-remoting.zip"
2. Open Mixed Reality>Remoting>Holographic Remoting for Play Mode
3. Enter your HL2 device IP into Remote Host Name
4. Enter Play Mode
Reproducible with: 1.8.0 (2021.3.27f1), 1.8.1 (2021.3.27f1, 2022.3.3f1, 2023.1.2f1, 2023.2.0a21)
Reproducible on: Windows 10
* Assertion *
Expression: "IsValid() || (timestamp == s_invalidTimestampValue)"
Function: "Microsoft::Holographic::AppRemoting::Timestamp::Timestamp"
File: "D:\\a\\_work\\1\\s\\src\\libremotingcommon\\src\\Timestamp.cpp"
Line: 158
Message: "Forbidden timestamp value."
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
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
- LocalizationSettings.InitializationOperation hangs when re-entering Play Mode with Domain Reload disabled
Resolution Note:
We have shared this issue with Microsoft and they indicate the fix will be available in an upcoming release.
Resolution Note (1.8.X):
We have shared this issue with Microsoft and they indicate the fix will be available in an upcoming release.