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

You can now use one version of Unity for all Windows Mixed Reality Devices #1335

Closed
StephenHodgson opened this Issue Nov 10, 2017 · 16 comments

Comments

Projects
None yet
7 participants
@StephenHodgson
Copy link
Collaborator

StephenHodgson commented Nov 10, 2017

HoloLens and IMHD devs can now use any version of Unity for production (So long as it supports Windows Mixed Reality) on the latest master branch checkout 842c4a1

Couple of notes:

  • you must use Unity Editor 2017.2.0p1 MRTP 4
  • You must have the latest Windows SDK (10.16299.0) installed, and the MRTK build window will now always default to using it.
    • We now use Windows SDK API Contracts to check to make sure the device the app is installed on can call/use the API we're attempting to use, and will now compile correctly.
  • The latest releases still require specific unity versions and SDK targets. Follow all instructions there.
@StephenHodgson

This comment has been minimized.

Copy link
Collaborator

StephenHodgson commented Nov 10, 2017

@raedbenz

This comment has been minimized.

Copy link

raedbenz commented Nov 10, 2017

Does this mean i can use Unity Editor 2017.2.0p1 MRTP 4 with MixedRealityToolkit-Unity for Unity 2017.2.0? or do i have to create my own packages from latest code in master branch ?

@StephenHodgson

This comment has been minimized.

Copy link
Collaborator

StephenHodgson commented Nov 10, 2017

Does this mean i can use Unity Editor 2017.2.0p1 MRTP 4 with MixedRealityToolkit-Unity for Unity 2017.2.0?

You were always able to use the MRTP 4 with the latest release (In fact I updated the release notes to inform users to use that version).

You'll need to create your own package from the latest sha I posted above. I specifically said:

The latest releases still require specific unity versions and sdk targets. Follow all instructions there.

I'm working on a new release with all the fixes, and might have it ready by this weekend.

@LocalJoost

This comment has been minimized.

Copy link

LocalJoost commented Nov 11, 2017

For now I would very much recommend MRTP4 for immersive apps as apps generated with previous versions tend to have 'double vision' sometimes for objects close by. Particularly controllers ;)

@genereddick

This comment has been minimized.

Copy link

genereddick commented Nov 11, 2017

Does it matter which version of Unity you use, 2017.2.n or 2017.2.n-MRTP4, if you are targeting HoloLens? Is MRTP4 meant only / primarily for Windows headsets?

@StephenHodgson

This comment has been minimized.

Copy link
Collaborator

StephenHodgson commented Nov 11, 2017

Well, considering the HoloLens is a Windows headset, it should be okay ;)

Yeah the build I made the other day works for both IHMDs and HoloLens with the 2017.2.0p1-MTRP4 unity editor.

@StephenHodgson StephenHodgson changed the title You can now use any version of Unity for all Windows Mixed Reality Devices You can now use one version of Unity for all Windows Mixed Reality Devices Nov 12, 2017

@raedbenz

This comment has been minimized.

Copy link

raedbenz commented Nov 12, 2017

Where can I keep track of latest unity MRTP releases?
Thanx

@StephenHodgson

This comment has been minimized.

Copy link
Collaborator

StephenHodgson commented Nov 12, 2017

Unfortunately Unity has decided to hide them away in some forum post.

The latest Unity MRTP builds appear here in descending order.

Also the main readme always has a link to the Unity Editor we're currently using for the project:
image

@raedbenz

This comment has been minimized.

Copy link

raedbenz commented Nov 13, 2017

Any luck with creating new release package? I tried creating it myself but when deleting old one from my project and importing new one, build process freezes 100% CPU. I get 8 instances of UnityShaderCompiler.exe hogging cpu.

@StephenHodgson

This comment has been minimized.

Copy link
Collaborator

StephenHodgson commented Nov 13, 2017

No, the master branch is too unstable at the moment to make a release.

@LocalJoost

This comment has been minimized.

Copy link

LocalJoost commented Nov 13, 2017

Well that is interesting. What AM I supposed to use then when I make new version? I usually just pull the master branch ;)

@StephenHodgson

This comment has been minimized.

Copy link
Collaborator

StephenHodgson commented Nov 13, 2017

Lol yeah, I do too.

That's why I usually try to get fixes in asap.
I'm using the toolkit as a submodule in my projects.

The nice thing about submodules is that you get to choose the checkout Sha you wanna use. Plus it's easier to roll back if something bad happens.

@jasonhbartlett

This comment has been minimized.

Copy link

jasonhbartlett commented Nov 27, 2017

Quick question: If the HL is running 10.14393 but I can only target to build to 10.16299 when using the above specified versions of Unity and MRTK, am I going to still be able to deploy to HL? Will this throw all kinds of errors due to namespace problems between VR and XR, etc?

@StephenHodgson

This comment has been minimized.

Copy link
Collaborator

StephenHodgson commented Nov 27, 2017

@jasonhbartlett Yes, you're locked into using either the 15063 or 16299 SDK (Based on the Unity Editor version you're using). We have a Windows API checker that makes sure the API compatibility works.

@shllybkwrm

This comment has been minimized.

Copy link

shllybkwrm commented Nov 27, 2017

"Keep in mind that the editor will crash if you play in editor without a IMHD."
What does this mean if you're only developing for HL? I rely on the editor to test small changes very frequently...

@StephenHodgson

This comment has been minimized.

Copy link
Collaborator

StephenHodgson commented Nov 27, 2017

It means you should keep to the main Unity Releases and to not use the MRTP builds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment