Closed Naphier closed 9 months ago
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.
This issue has been closed by an automated process because it is stale. If this is still an issue please add a new comment with more recent details and repro steps.
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!
MRTK 2.3.0 Unity 2019.3.3f1 Visual Studio 2019 v16.4.5 (with MSBuild installed v15.9.21.664)
====
Unity builds the Unity Project fine, but when it tries to compile the VS Project to build the appx it fails to find the below file:
File does not exist in that directory. I have created that directory and added the file and then a new error:
It appears that
$(VCTargetsPath)
is not resolving correctly when run from Unity. If I open the generated VS Project I am able to build fine. I checked and$(VCTargetsPath)
resolves toC:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160
on my machine. And indeed the file in question exists there.