Issues using 2.2.0 on 1.7.0, with MRTK3 and OpenXR

@localjoost , are you still on OS 1.7.0? I can try to make sure I have the same OS as well to weed that out.

@whebert that is correct.

@whebert nope 1.8.0. I basically upgraded everything on the device and in the app

@whebert I see the same results as you do. The permission dialogue and then the red square that occasionally turns green.

@localjoost have you tried updating to the latest OS version and performing a factory data reset? If that does not work, do you mind capturing a full bugreport

@kbabilinski Happy to oblige. You specify a factory DATA reset. Is that something special?

@localjoost, I think it would just be a factory reset, which would include all user data among other things.

Correct, just enable the factory reset setting before installing the OS in the Magic Leap Hub.

MLHub 2

MLHub 3

@kbabilinski Problem solved. Even without recompiling my repo app, I now see exactly what I expect. To be extra sure, I uninstalled it, removed all manual code from it that dealt with permissions, did a clean build, installed, and:

  • It asked for permission
  • It found the floor and showed red and green square as expected
  • Showed the right controller model
  • Showed a nice visualization on my hands.

One think I also noticed: when the Unity splash screen is showed, the background gets very dark, except for some edges. It never did that before. But if that's the only thing, I'll take it :slight_smile:

I downloaded my unchanged Walk the World app, and it still works - even though I ask explicitly for permission, so apparently that does not interfere with each other. But without recompiling, I even got the controller and the hands. Recompiling without the permission code and the default XR rig, it still worked. And the canvas buttons now also respond to the controller.,

So apparently something went haywire during upgrades. I updated it all the way from 1.4.0 to now 1.8.0. I seem to recall I had a beta in between, but I am not sure anymore. However, factory reset was a breeze. The only thing I found REALLY annoying was the ten foot EULA, but that was because I had forgotten to connect the controller. That was also very easy: just plug it in the device, and it 'knows' it.

Long story short: weird this happens, glad we got to the bottom of this. Cheers!

Hey @localjoost,

Awesome to hear @kbabilinski's suggestion of factory reset worked!!

Regarding the segmented dimmer you see during application start, you can set the OpenXR ML Rendering Extensions feature blend mode to Additive to make that go away (see below):

image

@whebert ,

Thanks! This works indeed. I had turned off the whole OpenXR ML Rendering Extensions because I thought I did not need them at all. I was wrong :wink: I released a new version 5.1.3.0 of my Walk the World app for Magic Leap. I hope you like it. Note the first map you ask usually s*cks, this is because the backend needs to warm up.

I have idea how the ML2 I have here could act so weird after the upgrades. Maybe I messed something up down the line

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.