Azure / azure-object-anchors

Azure Object Anchors releases and samples
https://docs.microsoft.com/azure/object-anchors
MIT License
37 stars 17 forks source link

Unity 2020: Unable to get the MRTK sample project working #17

Open AvinashNargund opened 2 years ago

AvinashNargund commented 2 years ago

Description Hi, I am trying to run the sample MRTK project on Hololens2. I updated the project to Unity2020.3.20f1. Then, I added all the necessary MRTK features using the MixedRealityFeatureTool and modified my Build settings according to the tutorial. But I am running into to two major issues -

  1. ..\mrtk\MSBuild\Projects\AOAMRTKApp.Dependencies.msb4u.g.props(22,3): error : Unable to find package Microsoft.Build.NoTargets. No packages exist with this id in source(s): MSBuildForUnity - This has bothered me the most as I have no clue what this error means and haven't found much resources online.
  2. Assets\MixedReality.AzureObjectAnchors\Scripts\TrackableObjectSearch.cs(72,13): error CS0234: The type or namespace name 'InputSystem' does not exist in the namespace 'CoreServices' (are you missing an assembly reference?) - I believe I have all the required features from MRFT so I don't know why I am still getting this error.

Development information (please complete the following information)

AR Device information (please complete the following information):

Additional Info List of features imported from MRFT -

  1. Azure Object Anchors v0.17.3
  2. Mixed Reality Toolkit Foundation v2.7.3
  3. Mixed Reality Toolkit Tools v2.7.3
  4. Mixed Reality Toolkit Extensions v2.7.3
  5. Mixed Reality Toolkit Standard Assets v2.7.3

Please let me know if I can provide additional information to help. Thanks!

craigktreasure commented 2 years ago

Shoot. I'm seeing the same. I'll get back to you.

AvinashNargund commented 2 years ago

Okay, seems like the CoreServices thing was a simple namespace problem. Using Microsoft.MixedReality.Toolkit.CoreServices.InputSystem fixed the issue. And the build issue automatically disappeared after this change (no idea why 🤷🏻 ). Now I am able to build and deploy the app.
Should I create a PR with this change?

craigktreasure commented 2 years ago

Glad you got it sorted out. Just to check, did you go through the 2020 upgrade instructions here?

AvinashNargund commented 2 years ago

Yes, I followed the instructions on that page.

Jversen commented 2 years ago

I was able to get rid of error 1 by opening assets/nuget and commenting out the first <clear />. like so:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <!--<clear />-->
    <add key="MSBuildForUnity" value="https://pkgs.dev.azure.com/UnityDeveloperTools/MSBuildForUnity/_packaging/UnityDeveloperTools/nuget/v3/index.json" />
  </packageSources>
  <disabledPackageSources>
    <clear />
  </disabledPackageSources>
</configuration>
craigktreasure commented 2 years ago

We're going to take a look at making things easier for Unity 2020. Internal reference number is 38627628.