Vrtk: Unity 2017 compatibility

[cameronoltmann]

Controllers are missing in Unity 2017. Making the following change resolves this:

Commit: 0acab31a39414f6818da389ff3971627b863df35
File: Assets/VRTK/SDK/SteamVR/SDK_SteamVRBoundaries.cs

Change line 27 from:
#if UNITY_5_6
to:
#if UNITY_5_6 || UNITY_5_6_OR_NEWER

[thestonefox]

This was changed in a previous PR https://github.com/thestonefox/VRTK/commit/43638c8b0d7f0132cb8708cd6049be9ccd3fa877

Because apparently an older version of Unity 2017 didn't require the Update Poses.

I think this is a case of Unity Betas not being stable enough to make decisions on.

[cameronoltmann]

Interesting. As of b10, it's necessary again. Wasn't in b9. Love it.

On Sat, Jun 24, 2017, 11:23 PM StoneFox [e-mail] wrote:

This was changed in a previous PR 43638c8
https://github.com/thestonefox/VRTK/commit/43638c8b0d7f0132cb8708cd6049be9ccd3fa877

Because apparently an older version of Unity 2017 didn't require the
Update Poses.

I think this is a case of Unity Betas not being stable enough to make
decisions on.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/thestonefox/VRTK/issues/1318#issuecomment-310885282,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABjV1zN-5H-YKqM-KFfUVsl7KCxHmC62ks5sHfzRgaJpZM4OEdxI
.

[thestonefox]

This is why it's best to stay well away from Unity betas :D

Let's close this ticket and deal with it when unity 2017 is released

[nylki]

Let's close this ticket and deal with it when unity 2017 is released

Apparently thats today :)

[thestonefox]

@nylki afaik VRTK 3.2.1 is compatible with Unity 2017.1 - Quite a few people are using it already

[nylki]

@thestonefox Ok. good to know, thx for the heads up!