Hello everyone.

The Mixed Reality Forums here are no longer being used or maintained.

There are a few other places we would like to direct you to for support, both from Microsoft and from the community.

The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.

For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.

If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.

And always feel free to hit us up on Twitter @MxdRealityDev.
Options

Unity beta 18

I was using beta 16 fine and able to debug within visual studio fine, but installed beta 18 this week, and can't seem to run in debug mode. Which makes debugging a pain, relying on a load of Debug.Log statements. Anyone else seen this or is it just me.

Basically when I run in debug mode, I can see the start of the trace and it starting, but then crashes and quits out with out really getting anywhere.

Best Answer

Answers

  • Options
    Jarrod1937Jarrod1937 ✭✭✭

    Interesting, sounds similar to what I'm experiencing with debugging. Though I'm using beta 16. Hopefully 20 will be the fix I need as well. I also have to admit, it's a pain, I'm making due with printing out debug text to UI, but doesn't help when I need to step through the code.

Sign In or Register to comment.