Unfortunately I cannot mitigate the issue without some manual work, as the this would require a complete restructure of both our build servers and git repository layouts.
I was wondering why the complete package name Microsoft.MixedReality.Unity.FrozenWorld.Engine.1.1.1 must be included in the path, instead of just FrozenWorldEngine or alike. This cange removes 37 chars from the path, and I asume only one version needs to be embedded in the unity package.
I was importing the WLT assets through the MixedRealityFeatureTool, and I get the issue of the installation path length as described at https://learn.microsoft.com/en-us/mixed-reality/world-locking-tools/documentation/howtos/initialsetup#a-warning-note-on-installation-path-length. On the contrary to what the note states it has not been fixed (yet).
Unfortunately I cannot mitigate the issue without some manual work, as the this would require a complete restructure of both our build servers and git repository layouts.
I was wondering why the complete package name
Microsoft.MixedReality.Unity.FrozenWorld.Engine.1.1.1must be included in the path, instead of justFrozenWorldEngineor alike. This cange removes 37 chars from the path, and I asume only one version needs to be embedded in the unity package.