Mixedrealitytoolkit-unity: Issues with UnityGLTF submodules when updating MRToolkit

[rigma]

Overview

Hello there! So, I just updated my version of MRToolkit for Unity on a project and my Editor says something strange to me: the UnityGLTF.GLTFSceneImporter.cs has ambiguous references between GLTF namespace and GLTF.Schema.

So far, I've only got this class impacted by those ambiguous references, and they concern the following ones:

• GLTFRoot
• MeshPrimitive
• Scene
• Node
• TextureInfo
• Image

I think the issue comes from that the two namespaces are used in the class, should it be better if we use only one? If we do this, which namespace should I keep for this class? GLTF or GLTF.Schema?

Expected Behavior

The package should be imported without errors in Unity.

Actual Behavior

Steps to reproduce

1. Take an old project made with MRToolkit
2. Update the MRToolkit with the new released one
3. Enjoy your compilation error

Unity Editor Version

2017.3.1f1

Mixed Reality Toolkit Release Version

2017.2.1.2

[StephenHodgson]

Did you delete the whole MRTK package in your project before reimporting?

[rigma]

Yes we did and the issue still occured.

[StephenHodgson]

1. Enjoy your compilation error.

I laughed way to hard at this. 😂

[StephenHodgson]

@keveleigh any ideas here?

[rigma]

So, I gave another try today by removing the whole package and by importing it again, and the issue had dissapeared. But another one took its place in the compilation error castle...

With this error, I'm not able to launch the _Play mode_, and I have some components, like the CompoundButtonMesh which are not working anymore (not able to change the ButtonMeshProfile in this case).
Hopefully, this time, I was able to reproduce it on an empty project, that I've put on this repository to illustrate the issue.

[SimonDarksideJ]

This new issue confused me, as in the latest release (this past week) the "SharingWithUnet" was completely moved to examples. Yet your error shows it in the Main HoloToolkit folder, which shouldn't be possible.

[rigma]

It confuses me too. But, even after I download again the new release's package, the error is still here, in the main HoloToolkit folder. Do I need to import the examples package too?

[StephenHodgson]

@DDReaper I don't think we made a patch release for that issue just yet.

@rigma just remove the Sharing with unet folder if you're not using it, if you are then move the stuff from the sharing with unet examples folder into your project.

[keveleigh]

We definitely need to make a patch release for the non-building release (SharingWithUNET issue). We have the draft ready to go, right?

[StephenHodgson]

Planning on it.

[keveleigh]

Sweet! I misread that as "I don't think we'll make", so sounds good :)

[rigma]

@StephenHodgson it worked just fine, thanks again for the assistance!

I think we can close this issue now.