Unity patch 5.2.1p2 is out

So far it looks good in our testing. Overall, I would recommend using it. However, there is a bug (not VR-specific) where MSAA on some android phones will cause a black screen. For now, you can disable MSAA. Unity is working as fast as they can on a fix, which will probably appear next week.

Cool! Is it an issue with some Android phones in general, or with S6 / Note 4 specifically ?

Pressing Play to preview my project in the editor reliably crashes 5.2.1p2 :/. The crash doesn't occur in 5.2.1p1 and earlier versions. Submitted a bug report with ticket ID 732698_o8ec3mrpe772bro4 .

"motorsep" wrote:
Is it an issue with some Android phones in general, or with S6 / Note 4 specifically ?

I haven't reproduced it yet, but it appears to be S6-specific.

"Svenviking" wrote:
Pressing Play to preview my project in the editor reliably crashes 5.2.1p2

Can you provide the crash stack and ideally the log, too?

Seems VRDevice.isPresent is always true on Unity 5.2.1p2 (even without Oculus Rift).
Unity 5.2.1p1 is fine.

"vrdaveb" wrote:

"Svenviking" wrote:
Pressing Play to preview my project in the editor reliably crashes 5.2.1p2

Can you provide the crash stack and ideally the log, too?

I reproduced the crash reliably more than ten times earlier, closing and reloading Unity, trying with my DK2 on or off, loading different scenes (the crash did not occur in a new scene, but did when transitioning from my loading scene to my main scene), etc. But... it seems to be fixed now :?. I've been trying but I'm no longer able to reproduce it.

If it still matters, the crash stack was included in a Unity bug report with ticket ID 732698_o8ec3mrpe772bro4, case number 732698. If the files are still available on my system I'm not sure where to find them(?)

One thing I did in the intervening time was actually build an APK -- not sure if that could be what changed things? (It built successfully, by the way, though I'm now seeing glitchy black squares on my Canvas when dragging a slider. Seems to be related to the Fill image.)

Ah, the crash started occurring again. Seems to be related to

OVRPlugin.dll caused an Access Violation (0xc0000005)
in module OVRPlugin.dll at 0033:f9b417b0.

Will PM the crash dump etc.

"KatsuomiK" wrote:
Seems VRDevice.isPresent is always true on Unity 5.2.1p2 (even without Oculus Rift).
Unity 5.2.1p1 is fine.

This is unfortunately a deal breaker for me at the moment :(. Is there a utilities equivalent that may still work to reliably detect if the Rift is connected?

"KatsuomiK" wrote:
Seems VRDevice.isPresent is always true on Unity 5.2.1p2 (even without Oculus Rift).
Unity 5.2.1p1 is fine.

Yes, it seems you are right. We are looking for a work-around.

With the utils, try "OVRManager.isHmdPresent"