Unity 5.2.2 is out!

The main difference is that you no longer get a black screen on Gear VR.

"vrdaveb" wrote:
The main difference is that you no longer get a black screen on Gear VR.

5.2.1p4 was crashing for people, so I am wondering if that's no longer an issue.

How about performance in 5.2.2 on Gear VR ? Any better than with 5.2.1p3 ?

The performance problem is still there, correct?

This is just anecdotal, but I upgraded my project and and it ran much (~12 FPS) slower than on 5.1.3p2 in the editor.

I then built a 64-bit executable version and it just emptied my primary display of all UI and then did nothing. I had to kill it via Task Manager.

Well, apparently 5.2.2f1 is officially recommended version for VR. Hopefully new Utils are coming out soon.

"motorsep" wrote:
5.2.1p4 was crashing for people, so I am wondering if that's no longer an issue.

5.2.1p4 was never a recommended version due to a black screen on Android, but the only problem reports I have seen on PC were due to user error (using old runtimes, bundle ID conflicts, trying to use Utilities after disabling VR).

"matteumayo" wrote:
The performance problem is still there, correct?

In my tests, performance is not significantly different from 5.2.1p3. We are still looking at reports of slowdown going from 5.1.3p2 to 5.1.3p3.

"motorsep" wrote:
Hopefully new Utils are coming out soon.

5.2.2f1 still uses PC SDK 0.7 and mobile SDK 0.6.2. We will release new Utilities when we add PC SDK 0.8 support in the near future.

"vrdaveb" wrote:
5.2.2f1 still uses PC SDK 0.7 and mobile SDK 0.6.2. We will release new Utilities when we add PC SDK 0.8 support in the near future.

Is mobile SDK still relevant to Unity 5.2.2 devs ? If so, why is there such a huge gap between mobile SDK and PC SDK versions ? (as if all focus is on PC SDK and Rift)

Unity supports Gear VR and the Rift. Oculus has separate native SDKs for the two hardware platforms and the numbering schemes are basically independent.

Still a confusion with Oculus SDK 0.5.0.1 and Unity 5.2.2.1F1 is it supported or not?
If not then what is the best setup ?

Yes, 5.2.2f1 + 0.5.0.1 still works on OSX. However, we've found position tracking never works on El Capitan due to some changes in how the driver API works. We don't have an ETA on a fix yet. The workaround right now is to avoid upgrading.