Grey rectangle in view

This issue is driving me mad. Screenshot below for reference. Looks identical to the above.



Example of a new scene:


I also deleted the OVR and reimported. It did work for a time but now also won't go away after a reimport, app restart, or computer restart. It all began with OVR 0.4.1

Things I've tried:
• New scenes don't fix it.

• New projects with a fresh import of the OVR do. So I figured it was an interaction with a script or asset in my project.

• Started removing assets and plugins to see if something was interacting. Removed everything but terrains. It still remained.

• Tried reverting to an old project where it appeared less, but no luck.

• Builds worked for the first run of the app, but on the third the rectangle returned.

My guess is that its related to the health warning screen. Looking into the disable thread to see if this solves my problem while developing to reactivate after.

It may be unrelated, but Unity bugs on playing the scene. For 1 second I see some beautiful random glitch art like the below. This only began around the time the rectangle appeared. These glitches then appear in my textures. Randomly. :cry:



System info:
Macbook Pro
2.3 GHz Intel i7
8GB DDR3 ram
OS X 10.93
Unity 4.5.3f3

Hoping someone out there brilliant has solved this before!

Turned off the health warning and found the gray rectangle remains.

It is also unrelated to any UI. Removed all menus and menu assets from project and it appears.

Hi

Yes I've also tried many many things and it still doesn't change anything. It's not even a GUI or anything like that.
What i have done though is restart my project a dozen times till the grey rectangle disappears.
But then it comes back later. So it's not even a constant issue in the program. It DOES disappear at some point. Just not for long...

Still working on it. This is really annoying.

I'm getting the same issue with the Tuscany demo in Unity on Mac OS X (i.e. Game view shows white/grey rectangle in the middle of the screen).

Anybody manage to determine root cause for this, and/or identify a fix or workaround?

EDIT: I built a Mac Standalone Build from the same project and the issue does not occur when running the app, so the issue only seems to occur within Unity.

DK2
Unity 4.5.3f3
Mac OS X 10.9.4
SDK 0.4.1
Firmware: 2.11

@Arnaudbaernhoft

Same here. Restarted a few times and it will creep its way back in. Now it won't leave my latest. I can even remove all items from the project and it is there on relaunch.

/cry

@MattSimpson

Did you try launching the build more than once? I've found the first build does not have the rectangle, but following launches can. My third launch seems to guarantee it.

Do you have an additional HMD plugged in? You could see this behavior if DK1 and DK2 were both plugged in.

Alternatively, are you developing without an HMD plugged in at all? Does this issue go away when an HMD is plugged in?

Hello everyone.

I'm having the same trouble here. Gray rectangle in the middle of the view on every scene (Tuscany and my own). I tried to play with the view distances without success.

Any progress on the cause on your side ?

I had the same issue and I found it related to the "quality" selected at startup.
(my HMD is not connected at the time i'm testing)

It appears to be kind of "random", check it out :
I run in fullscreen, 1680x1050, a standalone mac os APP built with latest unity pro 4.

First serie of test :

Fantastic : no rectangle
Beautiful : gray rectangle (like on screenshots posted by members above^^)
Good : no rectangle
Simple : black rectangle
Fast : no rectangle
Fastest : gray rectangle

Second serie of tests : (same settings, same resolution, same application)

Fantastic : Black rectangle
Beautiful : Black rectangle
Good : Black rectangle
Simple : no rectangle
Fast : black rectangle
Fastest : no rectangle

Third serie of tests :

Fantastic : Black rectangle
Beautiful : Gray rectangle
Good : Dark-gray rectangle
Simple : Gray rectangle
Fast : no rectangle
Fastest : White rectangle

Hope it helps figuring it out :)

This appears to be a race condition with some legacy latency tester code we have in the SDK. So far, we have only repro'd this on OS X when an HMD is not plugged in. If you're seeing this issue outside of that setup, please let us know here.

It may not be ideal, especially with a laptop, but leaving your HMD plugged in should be a temporary workaround.

Sorry guys, we'll get this fixed soon.