Nov 25 2020 10:34 PM - edited Nov 25 2020 11:11 PM
Hi All,
I am not sure if its an issue across other WMR headsets or if its just with Reverb G2 as its new, but I am seeing these artifacts while using "Use HMD for Simulation" in the Hololens Simulator.
https://www.youtube.com/watch?v=QnU-OmoSr98&feature=youtu.be
The Simulator is able to get the head tracking input and is behaving as expected, but the headset itself is unusable due to frozen frames.
Has anyone come across this before ?
Windows Build: 19042.630
Hololens Emulator Version: 10.0.19041.1124
Nov 30 2020 03:07 PM
I checked with the team, and it looks like they did pick up on your Feedback Hub submission for this issue! Thanks for reporting it :)
I know the HMD simulation is actually quite a new feature, this is a really good reminder that I need to go and try it out!
Nov 30 2020 10:17 PM
Dec 09 2020 08:04 AM
@aka_anoop I'm also experiencing this on the Odyssey+, I've tried a few different versions of the emulator including most recent (10.0.19041.1131). Hardware specs and requirements are all correct enabled, tried disabling and re-enabling hardware acceleration and toying with eye settings with 'EnableEyePoseControl' but the issue persists.
If anyone finds a solution I would love to hear about it!