I'm using Unity Pro 4.6.0f2, with the 0.4.4 runtime and integration package, and now my built executables show a black screen after launching. The game window preview in Unity works fine, and renders the scene as I would expect. However, when launching the built game executable, I see my scene for a split second, then everything goes black. I have toggled every option in Player Settings, to no avail. Using the 0.4.3 runtime and integration, I had no such problems. Is anyone else experiencing this?

Oddly enough, I'm experiencing this exact problem on Windows with the same configuration, and my Mac OS X builds actually work. However, the symptom you described is exactly what I see on Windows: proper display in Game window, but only a split second of vision before blackness in the builds.

That's odd. Is there anything in output_log.txt? Are you using D3D11 or D3D9?

Nothing of note in output_log.txt, all of the text in there is unrelated warnings that I know the causes of. I've tried this in DirectX 9 and DirectX 11. At first it appeared that DX9 worked and DX11 did not, but currently both exhibit the same behavior in the latest runtime.Also, OP is experiencing this problem on OpenGL and it works when I run my build on OpenGL, so it seems that it is at least not entirely contained within the graphics platform.

Are you using any image effects or additional scripts that would be modifying the eye textures or VR settings? Does the issue occur with the Tuscany scene that comes with the integration? If the runtime affects it, does it still occur when you switch between direct and extended mode?

Same problem here with OSX (Mavericks), except for the Fastest and Fast quality setting, which show darker shades than Windows build and apparently some chromatic aberration. After testing it seems the difference in the Unity player quality settings is that Antialiasing is disabled for those two settings. Did I miss something?Tuscany demo works (crawls at 3fps, but I guess that's due to machine specs).

OSX Builds go black immediately | Meta Community Forums

11 Replies

Replies have been turned off for this discussion

Jyakku
Honored Guest
12 years ago
Oddly enough, I'm experiencing this exact problem on Windows with the same configuration, and my Mac OS X builds actually work. However, the symptom you described is exactly what I see on Windows: proper display in Game window, but only a split second of vision before blackness in the builds.
vrdaveb
Oculus Staff
12 years ago
That's odd. Is there anything in output_log.txt? Are you using D3D11 or D3D9?
Jyakku
Honored Guest
12 years ago
Nothing of note in output_log.txt, all of the text in there is unrelated warnings that I know the causes of. I've tried this in DirectX 9 and DirectX 11. At first it appeared that DX9 worked and DX11 did not, but currently both exhibit the same behavior in the latest runtime.

Also, OP is experiencing this problem on OpenGL and it works when I run my build on OpenGL, so it seems that it is at least not entirely contained within the graphics platform.
vrdaveb
Oculus Staff
11 years ago
Are you using any image effects or additional scripts that would be modifying the eye textures or VR settings? Does the issue occur with the Tuscany scene that comes with the integration? If the runtime affects it, does it still occur when you switch between direct and extended mode?
jblasco
Honored Guest
11 years ago
Same problem here with OSX (Mavericks), except for the Fastest and Fast quality setting, which show darker shades than Windows build and apparently some chromatic aberration. After testing it seems the difference in the Unity player quality settings is that Antialiasing is disabled for those two settings. Did I miss something?

Tuscany demo works (crawls at 3fps, but I guess that's due to machine specs).
jblasco
Honored Guest
11 years ago
Just tested the application in another machine (previous ones had Intel HD graphics cards. This one was a 2011 Macbook Pro with an ATI HD 6750M and OSX 10.9). Black screen problem does not appear in this one.
cybereality
Grand Champion
11 years ago
If you disable AA on the other build quality, does that fix the issue?
jblasco
Honored Guest
11 years ago
In my case it should, since originally only Fastest worked and Antialiasing was the only difference between Fast and the next one before I changed it in the build.
Maybe boiserm can test it and confirm this.
Will also check what's said on viewtopic.php?f=34&t=4567&p=60919&hilit=chromatic+osx#p60919
for the chromatic aberration problem in case I overlooked that setting :/ .
vrdaveb
Oculus Staff
11 years ago
If you're using deferred rendering, be sure to turn AA off (that is, MSAA, not AA as a post-effect). MSAA isn't supported by deferred rendering and if you enable it on a render-to-RenderTexture, it can cause black screens. Are you still seeing the issue without AA enabled?
jblasco
Honored Guest
11 years ago
I won't be able to check it until tomorrow (UTC+1 here), but that's most likely to be the issue. Will post when tested.
Thanks a lot!