Closed elbuhofantasma closed 9 months ago
I think we've seen this issue pop up in the past - it's a bit tricky because of the fact that the assertion is happening in Unity asset importing code.
We've also hit some other challenges associated with the GLTF loading code (right now we're still on a fork that has basically has diverged from the source quite a bit), so there might be a more holistic solution here involving doing the GLTF work correctly (i.e. as some non-forked approach, since it's caused issues around duplicate loaders and other things in the past)
This issue also occurs on this commit: https://github.com/microsoft/MixedRealityToolkit-Unity/commit/a97278881a9a72d24326609fa40c963bce530442
We should look into this for the MRTK v3 public release.
And is nothing to do by then?
This issue has been marked as stale by an automated process because it has not had any recent activity. It will be automatically closed in 30 days if no further activity occurs. If this is still an issue please add a new comment with more recent details and repro steps.
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 visithttps://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!
Describe the bug
When importing the Examples '.unitypackage', the Error "Assertion failed on expression: '!name.empty()'" was output in the Unity console. The Unity console does not display any other information about this Error.
To reproduce
Steps to reproduce the behavior:
Expected behavior
The Unity console should display more helpful information to the user when issues generated by the MRTK occur. There should also be no Errors when importing the '.unitypackage' for MRTK Examples.
Screenshots
Your setup (please complete the following information)
Target platform (please complete the following information)
Additional context
Unity log output: