-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST] Allow moving the MRTK settings asset #922
Comments
@keveleigh will investigate a fix to address this request. |
@Schroedingers-Cat, I've just opened #969 to fix this! If you have time, please give the change a try and ensure it works for your use case. Thank you! |
@keveleigh thank you so much for the ping and the implementation! I'm happy to test it out at the end of next week when I'm back at work. Since I'm using the MRTK Feature Tool to install MRTK3, I wonder if there is some documentation on how to install the git repo into a Unity project? |
@Schroedingers-Cat which version of the Core package are you currently using? I can generate a one-off test package for you. |
@keveleigh that would be great! I'm currently using |
Sorry for the delay here! Please give this package a try. https://1drv.ms/u/s!AukaW5h_NnGsksdKky1IRFxqSutn-A?e=rIW4YA You can import the tarball through the Unity Package Manager: https://docs.unity3d.com/Manual/upm-ui-tarball.html |
Describe the problem
MRTK3 is adding visual noise to the Unity Assets root directory by placing its MRTKSettings.asset file in the MRTK.Generated directory. Moving this directory will break building causing an error that no profile has been defined for the current platform. The error is wrong and misleading because MRTK3 expects the MRTKSettings.asset at a specific location in the Assets directory.
Describe the solution you'd like
Previous versions of the MRTK (e.g. MRTK 2.8) had no problem moving the MRTK.Generated directory to a different place. It would be great if you could bring this back.
Describe alternatives you've considered
Moving the directory myself but that causes a build issue.
The text was updated successfully, but these errors were encountered: