The tutorial's Get Started final step has a reference to Preview Scenes module. This module is not linked. The documentation needs to provide a link if this is a supported feature.
UPDATE:
The documentation is not clear. In fact, the Preview Scenes is a step in the second tutorial of this project. This should be made clear in the tutorial documentation.

Currently there are 7 tutorials we have:

• Input Sim
• Object Manipulator
• Bounds Control
• Button
• Volumetric UI
• Dialog
• Theming

Given Dialog will go through a major refactor soon and theming is still in its early preview stage, I would propose we postpone releasing those two modules. I suggest we add a module that is even more basic than the input sim one (mentioned in #11) as well as add modules for in editor remoting and deploying the app to device.

We don't need to get the remoting and deploying modules ready for the first release, but I hope we do one for #11, whether as its own module or as a part of the input sim module.

When cloning and opening the project in the unity hub, you are prompted to install version 2021.3.28f1 of Unity, even if you have 2021.3.4f1 installed. README.MD should likely be updated to reflect this.

We should refer to this as MRTK3, not MRTK-Unity. In addition, OpenVR doesn't exist anymore, Ultraleap is misspelled (but also is not really an XR platform?)

This popup should be updated to be more relevant to MRTK3 and its focus on OpenXR.

Canvas is our preferred UI toolset; the tutorials should reflect this.

I noticed the locale was included in some links in the tutorials.
For example

We can potentially rename these modules to something like "Button (non-canvas)" and "Button (canvas)" given their contents. Pending discussion with the MRTK team.

I don't know why this is here and it probably shouldn't be.

The cubes seen are actually the hand joints, and they are not unique to input simulation. They are the actual hand joint data that is provided to the interaction system.

Also, the cubes will not be visible in-editor in the next/upcoming MRTK3 release, so this will need to be removed/edited, along with the image.

Not sure why the theming tutorial tells the user to switch to UWP.

Dialog will have a relatively major refactor coming up. The dialog tutorial will need to be rewritten.

Pointers do not exist in MRTK3. Some terminology:

• Ray interactor: the interactor that shoots a ray out into the scene to provide far interaction
• Reticle: the visual indicator at the end of the ray
• Select: the generic term for the primary action from an interactor used to manipulate an object or click a button

Scaling UI that isn't created with Canvas tooling cannot be scaled while retaining our design language. This UI should be rebuilt using Canvas if it should be scaled.

However, we recommend not scaling UI at all, because the UI sizing and metrics are optimized for our mixed reality devices and hand tracking.

The rig has a scene override on it that sets the near Z to a (way too large) 0.3m. This causes rendering problems.

For example, the text on the button is clipped by the nearZ.

Bounds Control Tutorial Step 4 Next button is still disable after completing the instruction.

I completed the instruction as described. Select Coral game object then add BoundsControl component but the Next button is still disabled.

NOTE: the Play Mode is not running

The large cover photo for "input simulation" is actually a screenshot of MRTK2.

BoundsControl is intended to be used at near-to-medium distances (with the current sizing/prefab setup). At very far distances like this tutorial (4 meters away) it doesn't work well. Recommendation; move corals much closer to user (and make smaller!)

Normal appearance with smaller objects + closer distances:

The link on "For further instructions, visit Oculus Link" redirects to an error page

MRTK3 ships with the CanvasProxyInteractor which allows users to interact with buttons, bounds controls etc. in the scene without using a simulated hand/controller. I think demonstrating that would be a great starting point. We can order the existing input sim tutorial as the second one in the list. Or we can add this to the existing input sim tutorial.

Currently the content seems to be designed more for VR than AR (the dome ceiling, the shadow, etc.). We need to make sure the tutorial is deployable to AR and VR devices while achieving a 60fps framerate.

Scene preview looks fine.
In tutorial: Mouse-Based Interaction, Step 2, when pressing play the Game view just turns black. WASD does not do anything either.
Unity 2021.3.22f1 Personal DX11.

I just want to use the old demo from mixed reality demo but even that is broken. Why was the import examples removed from the Mixed Reality Feature tool in favor of this tutorial for MRTK3??

Assets\Scripts\TutorialCallbacks.cs(3,28): error CS0234: The type or namespace name 'Editor' does not exist in the namespace 'Unity.Tutorials.Core' (are you missing an assembly reference?)

This part of the tutorial seems to imply that the developer has to check the box to enable handles on the BoundsControl. Instead, it's designed so that the user can quickly pinch/click/select/etc the object during runtime and it will enable/disable the handles without any editor tooling.

The checkbox is only meant for developers to be able to control the handles either from some external script or just to specify that the handles should start active, rather than needing the pinch action.

Hi,

Testing the aquarium tutorial (Unity 2021.3.25f1, VS 2019) with Hololens2, when I try to experiment the "CanvasButtonBar" adding Spawner to the Coral button, nothing happens in the play mode. No error in unity. Button is well configured as described in the tutorial

I tried to debug through VS and saw that the Instantiate method

 public void SpawnCoral()
    {
        Vector3 position = new Vector3(.19f, 0, .7f);
        Instantiate(coral, position, Quaternion.Euler(0, 180, 0), parent);
    }

is doing nothing. Did I miss something?

Make sure we use Graphics Tools/Standard.

This should probably explain that the preferred way for users to test applications in the editor is by connecting a headset, either PCVR, Link, or Remoting. Simulation is just a backup/fallback!

We just released pre.10 with a lot of nice quality of life features, including fixes for the input simulator.

I tried using OpenXR and Oculus in the XR plugin management to build this project as is with no luck. I then tried downloading the Oculus integration and generating an Android manifest with no luck in a successful build.

Those are the OpenXR settings for android, which are missing the Motion Controller Model option for some reason?

And also the MRTK utilities don't show an option to integrate oculus?