Hi!
The problem is, that i have no camera image, only black screen.
Unity 4.3.2
Vuforia 2.8.7
iOS 7.0.2 - iPad mini
Device Log:
Thanks!
Hi!
The problem is, that i have no camera image, only black screen.
Unity 4.3.2
Vuforia 2.8.7
iOS 7.0.2 - iPad mini
Device Log:
Thanks!
Unity 4.3.2
Vuforia 2.8.7 (Sample app 2.8.9)
iOS 7.0.2 - iPad mini
Device Log:
Same issue here: Unity 4.3.4f1, Vuforia 2.8.7, iOS black screen
Devices tested: iPhone5 and iPhone4s both running iOS 7.0.6.
Additional item that I have not seen in this thread:
I have UnityPro and iOS Pro. This issue happened after I upgraded the license to iOS Pro (was only Unity Pro, iOS Free originally). I tested on a version of Unity Free and it did not have the bug.
Sorry, I am confused, as you have re-used an existing thread that was related to building Unity Vuforia apps on PCs. This results in a black screen because it is imported.
The latest version of Vuforia and the latest version of the samples work fine on the latest version of Unity 4.3.3/4 - there is no screen.
So.... going back a step, what exactly is the problem?
N
Sorry, didn't realize the original post was about building on windows.
Anyway, I'm building on Mac os, with Unity 4.3.4 and Vuforia 2.8.7.
With a Unity iOS Pro license, the live camera view comes out black.
However, with Unity iOS Free, the live camera view is fine.
The camera also works in 4.2.2 Unity iOS Pro.
Are you testing with the iOS Pro license? This is the version that let's you replace the unity splash screen.
Tried on Iphone5 and 4s both running iOS 7.0.6.
Yes it works in play mode. Works for android builds, works for iOS Free version. I fully tested this and found that the only failing combo was Unity 4.3 with Unity iOS Pro.
Had to revert to 4.2.2 to get work done. I'm in the middle of production, and I don't have the time to go back right now. Can I install Unity 4.3 in a separate folder for testing? Not sure.
Have you guys tested with Unity iOS Pro license? -- this is Unity's new Licensing scheme. There is a separate Pro upgrade for base Unity, for iOS and for Android. My license info in the about Unity screen says: Unity Pro, iOS Pro, Android Pro
Can I install Unity 4.3 in a separate folder for testing? Not sure.
Yes - rename your existing Unity installation directory and this way a new installation will not overwrite it
...though you need to decide whether this is right for you
Have you guys tested with Unity iOS Pro license?
Of course - you have no idea of the enormity of testing that goes into Vuforia ;)
N
Okay, so I installed Unity 4.3.4 to another folder. I tried an empty scene with the vuforia.unitypackage and used the AR camera and a Tracker. This worked fine.
So I went back to my scene that was causing problems in 4.3.4 (black screen). I had reverted the scene to 4.2.2. This required me to rebuild the assets a few times, since there were errors caused by the reversion to an old version. This scene worked fine in 4.2.2. I then re-updated it into 4.3.4 and now it is working fine!
I believe this issue arose when I updated my license from iOS Free to iOS Pro. IE, the scene had been built and tested ok in iOS Free, then the license was updated to iOS Pro and I got the black screen. So I guess the solution is to rebuild the assets after a license change like that.
I am getting this problem as well. The old probelm was a conflict with Neat and their social media plugin if I recall. They both were creating a PostprocessBuildplayer file. Neat offered a work around. I have been unable to get that workaround to work with 4.3.4 Unity and 2.8.7 Vuforia. Has anyone been able to get Neat Social Media Plugin 1.5.3 with Unity 4.3.4 and Vuforia 2.8.7. I know that sounds specific, but those are the current versions (as of this posting) for all those plugins and I was told conflicts were resolved.
Thanks!
Vuforia 2.8.9 image target sample app also not working, only black screen
Could you please check again because if this is happening then there is something fundamentally wrong. Try with a new project and import the sample - also try play mode first to check. Also, make sure that you are using OpenGL ES 2 rather than 1, as this can lead to a black screen.
N