Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Assertion failed: Removing Assets/HoloToolkit/UX/Resources/Models/Cursor/Cursor_move/CursorRing.fbm/templates because the asset does not exist
See original GitHub issueOverview
When opening the MRTK MASTER branch for the first time, the following error appears:
Assertion failed: Removing
Assets/HoloToolkit/UX/Resources/Models/Cursor/Cursor_move/CursorRing.fbm/templates because the asset does not exist
Expected Behavior
No errors when opening project.
Actual Behavior
Assertion failed: Removing Assets/HoloToolkit/UX/Resources/Models/Cursor/Cursor_move/CursorRing.fbm/templates because the asset does not exist
Is displayed in the console on startup.
Unity Editor Version
MRTP4
Mixed Reality Toolkit Release Version
MASTER
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Removing Assets/Internal/Scripts/TestScript.cs because the ...
Assertion failed : Removing Assets/Internal/Scripts/TestScript.cs because the asset does not exist.
Read more >Assertion Failed: Removing something that wasn't added?
If I click Ignore everything works fine & as expected and I do not recieve a crash. It's really annoying but doesn't seem...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
https://github.com/Microsoft/MixedRealityToolkit-Unity/pull/1305#discussion_r149527717
Looks like GitHub didn’t automatically close these issues when merged into master. I’ll close these manually and look into why.