Search Unity

Should we move to 5.6 beta?

Discussion in 'Daydream' started by Claytonious, Dec 14, 2016.

  1. Claytonious

    Claytonious

    Joined:
    Feb 16, 2009
    Posts:
    904
    Now that the 5.6 beta is up, will you be posting something here in this forum when it's time for us to switch over from the GVR preview 13 to the 5.6 beta? (I saw nothing about Daydream in the release notes over there yet).

    Thanks!
     
    Claytonious, Dec 14, 2016
    #1

  2. mgear

    mgear

    Joined:
    Aug 3, 2010
    Posts:
    9,448
    this was in 5.6b1 notes,
    - Player: Native Daydream integration as a VR target for Unity VR applications.
     
    mgear, Dec 14, 2016
    #2

  3. Claytonious

    Claytonious

    Joined:
    Feb 16, 2009
    Posts:
    904
    Ah, I overlooked it. Thanks!
     
    Claytonious, Dec 14, 2016
    #3

  4. joejo

    joejo

    Unity Technologies

    Joined:
    May 26, 2016
    Posts:
    958
    I would hold off on using 5.6b1 unless you really want to live on the edge. There are a number of issues in that release that will be corrected in b2 and b3 but due to timing didn't make b1. Feel free to kick the tires and what not but be aware that things are rough.

    If you make use of the Google VR SDK then I would wait till b3 for sure.
     
    joejo, Dec 14, 2016
    #4
    tnydwrds likes this.

  5. 00christian00

    00christian00

    Joined:
    Jul 22, 2012
    Posts:
    1,035
    After b3( or around that version) will you stop to release specific daydream build or they will continue in parallel?
     
    00christian00, Dec 14, 2016
    #5

  6. joejo

    joejo

    Unity Technologies

    Joined:
    May 26, 2016
    Posts:
    958
    I believe we will stop releasing specific builds but I am not the person who gets to make that decision. :)
     
    joejo, Dec 14, 2016
    #6

  7. tnydwrds

    tnydwrds

    Joined:
    Jun 11, 2013
    Posts:
    9
    Because at that point there will be no need for GVR SDK?

    So there shouldn't really be any attempt to use GVR SDK with the 5.6 betas?
     
    tnydwrds, Dec 15, 2016
    #7

  8. joejo

    joejo

    Unity Technologies

    Joined:
    May 26, 2016
    Posts:
    958
    There is an issue in the current beta where a Unity Build compile define is incorrect. This define causes a number of issues when trying to compile the Google Unity SDK in your project in 5.6b1. Unfortunately it was caught too late to make the b2 release so it will be in the b3 release.

    The Google Unity SDK is still an important package developed by Google for the community and is not owned or maintained by Unity.
     
    joejo, Dec 15, 2016
    #8
    acorrow and tnydwrds like this.

  9. acorrow

    acorrow

    Joined:
    Jan 4, 2015
    Posts:
    32
    Just to be clear here on one thing: Will 5.6 still make use of the GVR SKD? Or will this be natively implemented in Unity VR? Also is there any existing documentation as to how this will be integrated?

    Somewhat assuming the idea of "No Prefabs Needed" if the SDK is still there, as being that the GvrController, GvrDisplayMain, etc will just be static classes loaded if the player settings have Daydream enabled. But who knows. Any documentation would be great to get a head start on it. Thanks
     
    acorrow, Dec 15, 2016
    #9
    tnydwrds likes this.

  10. joejo

    joejo

    Unity Technologies

    Joined:
    May 26, 2016
    Posts:
    958
    I think there is a lot of confusion about what is being integrated natively and what is not. To help clarify I need to make the following statements:

    1) The Google Android NDK is the native interface to the Google VR system, which includes both Cardboard and Daydream.
    2) The Google Unity SDK is a Unity package distributed by Google that provides a lot of utilities, helpers and examples (including prefabs and controller simulation/access).

    What is integrated natively into Unity is #1, the Android NDK. What is NOT integrated at all is the Google SDK (#2) with all the controller and example code.

    That being said, we are working on native controller integration (5.7 is the current target for that), but it will most likely not replace the need for most of the Google Unity SDK code. The native integration will be very low level and the SDK has a lot of functionality built around the controllers that would still be valid and useful.
     
    joejo, Dec 15, 2016
    #10
    recruit_tatsuya, tnydwrds and acorrow like this.

  11. acorrow

    acorrow

    Joined:
    Jan 4, 2015
    Posts:
    32
    This is a great clarification. Thanks!
     
    acorrow, Dec 15, 2016
    #11

  12. WendelinReich

    WendelinReich

    Joined:
    Dec 22, 2011
    Posts:
    228
    According to the Unity blog 5.7 will never exist. Does this mean native controller integration wont come before "Unity 2017" (set to appear in April)?
     
    WendelinReich, Dec 16, 2016
    #12

  13. joejo

    joejo

    Unity Technologies

    Joined:
    May 26, 2016
    Posts:
    958
    Yes. Sorry for the confusion about the name.
     
    joejo, Dec 16, 2016
    #13

  14. kexar66

    kexar66

    Joined:
    Feb 27, 2013
    Posts:
    48
    Is current 5.6.0b4 good enough to migrate?
     
    kexar66, Jan 19, 2017
    #14

  15. joejo

    joejo

    Unity Technologies

    Joined:
    May 26, 2016
    Posts:
    958
    Yes. Now that the integrated Google VR NDK is 1.10 it should be OK to start migrating (caveats about general Beta quality an Issues apply).
     
    joejo, Jan 19, 2017
    #15

  16. WendelinReich

    WendelinReich

    Joined:
    Dec 22, 2011
    Posts:
    228
    I have to disagree though - I just got beta 4 and realized in horror that movement of fast objects is jittery (as mentioned in this thread). How did this old Gear VR problem manage to reappear?
     
    WendelinReich, Jan 20, 2017
    #16

  17. joejo

    joejo

    Unity Technologies

    Joined:
    May 26, 2016
    Posts:
    958
    Please file a bug report as noted in the thread you are linking and report back the case if.
     
    joejo, Jan 20, 2017
    #17

  18. WendelinReich

    WendelinReich

    Joined:
    Dec 22, 2011
    Posts:
    228
    Done, it's case number 872723
     
    WendelinReich, Jan 21, 2017
    #18