I managed to find a more recent solution as a temporary fix, it might help someone until MS fix the issue in a future update.
Edge on hololens is working quite well with WebXR, no workarounds needed. Want to share a playground or a demo that doesn’t work (and should, of course )
I’ve seen the same thing as @Mal_Duffin, it’s not Babylon specific, any WebXR demo stops working.
I was actually in the middle of working on something, and the same demo first worked, when I restarted edge it seemed to do an update. After which it stopped working. Honestly heartbreaking and made me pause webxr development for a little bit while I look for another device to test with.
can you share the OS and browser version? I want to understand what could be the cause here
According to the link @Mal_Duffin shared it’s the combination with OpenXR that’s the issue.
His versions are:
Windows version OS Build: 22621.1324
I haven’t checked mine
I wanted to check, so I updated my system, and now… WebXR doesn’t work. No flag helped. Updating now to 22621.1328, hoping for a fix.
I hope it’s fixed, but last time it took literal months. But at that time VR still worked, I think both are now broken so that might make it higher priority
So that didn’t work as expected - device is in recovery mode, update failed. I’ll wait for the next nightly update and see if it helps. No luck so far.
Hiya @RaananW - if you follow the instructions in the link I posted, you’ll be able to get back to a working WebXR version. It’s a bit of hassle, but it works consitently ( I’ve done it a couple of times now )
It’s hard to know if this has been flagged internally, so that the internal team know about it and are working on a fix. It’s a right PITA, but def worth raising the issue - the more times it’s reported, the higher up the priority list it might go.
Looks like they’re aware and working on it, so that’s good. But no idea when it would be fixed. Again, last time it took months
Did any of the new nightly updates to the HoloLens 2 fix this issue?
I still have no direct answer, and i can’t update my device because the update (1468) crashes the entire system.
That def sucks!