Add code to do some minimal config parameter checking and dump to the console what the settings are and how to change them.
Change some default settings to be more consistent.
Build paths with Path.Combine instead of +
Bundler has a different input system and has some components from much older HoloTtolkits. To eliminate conflicts, only certain parts of the current MRTK can be imported into Bundler. To update Bundler to future MRTK-Unity releases, start with the steps below. They will likely get you most of the way there. You will likely need to make a few changes to accomodate any API changes and dependency changes.
1) Delete existing MRTK components from Bundler. The following commands will accomplish that:
cd MixedRealityCompanionKit\Bundler\Viewer\Unity\Assets
rd /s HoloToolkit
rd /s Plugins\HoloToolkit
rd /s Scripts\SpatialMapping
2) Export a package from Unity with the following list of directories and files. Include dependencies in the export
...\MixedRealityToolkit-Unity\Assets\HoloToolkit\SpatialMapping\*
...\MixedRealityToolkit-Unity\Assets\HoloToolkit\Utilities\Shaders\FastConfigurable\*
...\MixedRealityToolkit-Unity\Assets\HoloToolkit\Utilities\Scripts
Billboard.cs
CameraCache.cs
DataEventArgs.cs
FixedAngularSize.cs
Int3.cs
Interpolator.cs
MathUtils.cs
PropertyChangedEventArgsEx.cs
RaycastResultComparer.cs
SimpleTagalong.cs
Singleton.cs
Tagalong.cs
WindowsApiChecker.cs
...\MixedRealityToolkit-Unity\Assets\HoloToolkit\Utilities\Scripts\Extensions\*
...\MixedRealityToolkit-Unity\Assets\HoloToolkit\Utilities\Scripts\Editor\
EditorPrefsUtility.cs
...\MixedRealityToolkit-Unity\Assets\HoloToolkit\Utilities\Scripts\CrossPlatform\Reflection\
ReflectionExtensions.cs
TypeUtils.cs
3) Import that package into Bundler
4) Do test builds and clean up any API changes and changed dependencies
Kevin K
Adam Mollis