search

microsoft / MixedRealityToolkit-Unity

This repository is for the legacy Mixed Reality Toolkit (MRTK) v2. For the latest version of the MRTK please visit https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity
https://aka.ms/mrtkdocs
MIT License
6k stars 2.12k forks source link

BuildWindow doesn't work for me #131

Closed aaronsnoswell closed 8 years ago

aaronsnoswell commented 8 years ago

I don't know if the BuildWindow is stable yet but I haven't been able to get it to work.

I'm using Unity HoloLens 5.4.0b24-HTP (64-bit), Visual Studio 2015 Professional with Update 3 that came out a few weeks ago, and the latest HoloTooklkit as of the time of writing (commit 117f8c5d344ddaf2314012ddb7602a2078b9ce0d, 2 days ago).

I've exported the HoloToolkit as a Unity package, then re-imported it into my new HoloLens project. When I manually build my VS2015 solution, then build and deploy, my app works fine. When I use the HoloToolkit 'Build Window' to try and build the SLN, APPX and deploy, msbuild will run in the console that pops up for a few minutes, then I get errors in the Unity status bar down the bottom of the Unity editor. E.g. in the screenshot you can see a "System.NUllReferenceException: Object reference not set to an instance of an object", although sometimes I see other errors.

Screenshot of error

Does anyone know if the HoloToolkit build window is functional at this point in time? If it is, can I help write some documentation about how to use it correctly? I haven't been able to figure it out yet.

This is a re-post of this Unity HoloLens forum topic. This bug post is possibly related: https://github.com/Microsoft/HoloToolkit-Unity/issues/98

riverar commented 8 years ago

Hey there @aaronsnoswell, this feature works but may be a little rough around the edges since it's brand new. Are you using the latest from this repository? Can you click Open SLN and build from that Visual Studio instance? I found a one-time open of that solution to change the platform target from Any CPU to x86 is required before things start working correctly.

jwittner commented 8 years ago

@riverar The one time change to x86 strikes me as really odd. Looking at the MSBuild command we are explicitly trying to specify x86.

@aaronsnoswell If you could try the steps one at a time and let us know which one is failing that would help us narrow in.

Thanks!

jwittner commented 8 years ago

@aaronsnoswell Also, if could find that error in your console, we might be able to get a file and line number, which would really help! =)

aaronsnoswell commented 8 years ago

Hi folks. I'm a away for a few days but will give both your points a shot when I get back. Watch this space.

jwittner commented 8 years ago

@aaronsnoswell There have been several fixes since you opened this bug. Please let us know if you're still seeing problems. =)

aaronsnoswell commented 8 years ago

Hi :) I don't have time to test at my end right now. Please close the issue and I'll re-open if I am still seeing it in the future :) Cheers!

On 29 Jul 2016 10:31 a.m., "Josh Wittner" notifications@github.com wrote:

@aaronsnoswell https://github.com/aaronsnoswell There have been several fixes since you opened this bug. Please let us know if you're still seeing problems. =)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/HoloToolkit-Unity/issues/131#issuecomment-236064197, or mute the thread https://github.com/notifications/unsubscribe-auth/AA7EW5uYVl1_EMqMJ-kukUDNfjLd2n0yks5qaUnigaJpZM4JRgaH .