Search Unity

Issues v2.0.0-Beta2 VS RC2.1

Discussion in 'VR' started by Bahmann, Jun 28, 2019.

  1. Bahmann

    Bahmann

    Joined:
    Mar 5, 2019
    Posts:
    15
    Hello Folks,


    We are currently producing some Training modules on Unity 2018.3.6f1 and the Windows Mixed Reality toolkit v2.0.0-Beta 2.


    We now wanted to upgrade to 2019.1.8f1 because of LWRP, ShaderGraph, VisualEffectsGraph, which would be very handy to create the upcoming modules.

    Sadly, we found out that the current Version we were using from WMRT is not compatible with Unity 2019.

    Luckily, there is the possibility to upgrade to Version RC2.1 that is compatible but it has many Scripts missing and the structure is completely rewritten, so that we have to rewrite our whole code/scripts.

    Is there an detailed overview what has changed after 2.0.0-Beta 2?

    Additionally:
    1) I've got it running with "just" the new scripts from MRTK but we need to redo the snapping of Gameobjects to specific areas when colliding.

    2) The "new" Raycast has some kind of Rubberband feeling to it. The "old" one was just a straight line and drag and dropping didn't feel so slow with the newer version. Is there a way to change this??

    Raycast Beta Version

    beta.png

    Raycast RC2.1
    RC2.1.png
     
  2. chbecker2

    chbecker2

    Official Microsoft Employee Microsoft Employee

    Joined:
    Dec 26, 2018
    Posts:
    6
    Hi Bahmann, thank you for the feedback on MRTK to build VR apps!

    1. Post new issues to GitHub
    2. Join us on Slack - holodevelopers.slack.com

    Many, many things were added since Beta2, high level check out the release notes on MRTK's GitHub releases tab.
     
    JasonCostanza likes this.