Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.

Still no news on a 2017.2f03 version?

Discussion in 'EditorXR' started by DragonSix, Oct 22, 2017.

  1. DragonSix

    DragonSix

    Joined:
    Jul 2, 2013
    Posts:
    37
    ^

    The patchnotes of the release of 2017.2 mention compatibility with EditorVR. But it seems the current build doesn't work.
     
    DragonSix, Oct 22, 2017
    #1

  2. amirebrahimi_unity

    amirebrahimi_unity

    Unity Technologies

    Joined:
    Aug 12, 2015
    Posts:
    400
    amirebrahimi_unity, Oct 23, 2017
    #2

  3. unity_andrewm

    unity_andrewm

    Unity Technologies

    Joined:
    Jun 25, 2015
    Posts:
    73
    To preview EditorVR support for 2017.2 you can work off the github branches. The branch Amir mentioned, or even the main 'development' branch at https://github.com/Unity-Technologies/EditorVR now work with 2017.2.

    As far as another official 'release' - we're working on it. There are some technical issues we are working on to make sure we are satisfied with what we release.
     
    unity_andrewm, Oct 23, 2017
    #3

  4. jashan

    jashan

    Joined:
    Mar 9, 2007
    Posts:
    3,304
    Could you please update the FAQ in this forum and documentation (this should be on https://github.com/Unity-Technologies/EditorVR/ and https://docs.google.com/document/d/13Md9Z5sXNy96qyivpLOakFU-CJ5Uhpm1bS-WJp2SkWE/edit)? I have just spent about 10 minutes looking for this information and almost thought we'd have to stay on 5.6 with our project if we want to use that feature.

    So, just to be sure: This currently works with an experimental build of Unity 5.6 but we could also import the package from GitHub into Unity 2017.2 and it would also work? What about current 2017.3 betas?
     
    jashan, Nov 10, 2017
    #4
    De-Panther likes this.

  5. unity_andrewm

    unity_andrewm

    Unity Technologies

    Joined:
    Jun 25, 2015
    Posts:
    73
    The github branch works with 2017.2 and the .3 betas. I recommend 2017.2.p1 or greater because there were some critical performance improvements in those builds and forward.
     
    unity_andrewm, Nov 15, 2017
    #5

  6. jashan

    jashan

    Joined:
    Mar 9, 2007
    Posts:
    3,304
    Ah, that's good to know. I'm hoping to make the move to 2017 next week, and then I'll jump right into 2017.2.p1 (or later ;-) ).
     
    jashan, Nov 16, 2017
    #6