Search Issue Tracker
Duplicate
Votes
0
Found in
2018.4
2019.4
2019.4.15f1
2020.2
2021.1
2021.2
Issue ID
1310181
Regression
No
[UWP] Virtual object accuracy tracking loss on HL1 and HL2
How to reproduce:
1. Open the attached "Submission.zip" project
2. Build to UWP
3. Open built solution in Visual Studio
4. Start Debugging on Remote Machine (Debug ARM64 for HL2)
5. Walk around the virtual object and see it through different perspectives
Expected result: Virtual object stays in place when moving around it
Actual result: Virtual object accuracy tracking loss is visible (object is floating, you can see it in the attached video "repro.mp4" )
Reproducible with: 2018.4.31f1, 2019.4.19f1, 2020.2.3f1, 2021.1.0b4, 2021.2.0a2
Notes:
- The issue is less visible in HL1, but still occurs
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
- Freeze on DynamicHeapAllocator::InitializeMemoryRegion when entering Play mode in a specific scene
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
This is a duplicate of issue #1242142