search

microsoft / MixedRealityToolkit-Unity

This repository is for the legacy Mixed Reality Toolkit (MRTK) v2. For the latest version of the MRTK please visit https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity
https://aka.ms/mrtkdocs
MIT License
6k stars 2.12k forks source link

Importing samples with UPM generates "Invalid AssetDatabase path" warning #9800

Closed elbuhofantasma closed 8 months ago

elbuhofantasma commented 3 years ago

Describe the bug

When importing all example scenes into a project from the Examples UPM package, an "Invalid AssetDatabase path" warning for the sample that is being imported.

Screenshots

image

Your setup (please complete the following information)

david-c-kline commented 3 years ago

At first glance, this appears to be due to the standard assets package (source of materials, etc) being in the library/packagecache folder.

while researching this issue, i discovered a similar report about the XR Interaction Toolkit: https://forum.unity.com/threads/xr-interaction-toolkit-sample-import-error.1095388/

david-c-kline commented 3 years ago

The scenes with references to materials in the packagecache do work. I will try moving the standard assets into the Assets folder to see if this eliminates the warning (i expect it will).

Doing so will require adding logic similar to what is done for the shaders (copy to Assets, require explicit permission to overwrite) along with the risk of overwriting customer changes to materials, etc.

david-c-kline commented 3 years ago

Moving to 2.x future while we investigate why Unity 2020 chose to point this out in packages that reference assets in the library folder.

MalteRei commented 3 years ago

I am having the same issue although with Demos - Input. Is there an ETA on when this will be fixed or a workaround? I can also provide more information if that helps with triage for the issue.

keveleigh commented 3 years ago

@davidkline-ms This feels like it could be a Unity bug, especially if other packages (like you pointed out XR Interaction Toolkit) are hitting it.

polar-kev commented 2 years ago

The scenes with references to materials in the packagecache do work. I will try moving the standard assets into the Assets folder to see if this eliminates the warning (i expect it will).

Doing so will require adding logic similar to what is done for the shaders (copy to Assets, require explicit permission to overwrite) along with the risk of overwriting customer changes to materials, etc.

@davidkline-ms, are we confident this is a Unity bug?

keveleigh commented 2 years ago

Ping @davidkline-ms

IssueSyncBot commented 8 months ago

We appreciate your feedback and thank you for reporting this issue.

Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.

Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.

Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.

Thank you for your continued support of the Mixed Reality Toolkit!