Forum Discussion
0.2.4 Unity Integration Issues on OS X
I'm running into compiling errors when I try to integrate 0.2.4 into Unity Pro in OS X. The Tuscany scene loads into Unity just fine, but when I go to the Game tab and hit play, I get the message that "All compiler errors must be fixed before you can enter playmode". Looking into the OVRPlayerControllers shows errors on the Gamepad, Main Menu and Player scripts.
Has anyone encountered this before? I've tried starting from an Empty project a few different times now and the result is always the same.
I'm assuming that my inexperience with Unity is the problem, but I wanted to make sure this wasn't a bug in the SDK as well.
Also, could this be a failed attempt to reconcile my custom ConfigUtil profile? I created one before I attempted the 0.2.4 integration in Unity. I don't even know if it's being used in any way yet, but I figure it's maybe worth mentioning.
Has anyone encountered this before? I've tried starting from an Empty project a few different times now and the result is always the same.
I'm assuming that my inexperience with Unity is the problem, but I wanted to make sure this wasn't a bug in the SDK as well.
Also, could this be a failed attempt to reconcile my custom ConfigUtil profile? I created one before I attempted the 0.2.4 integration in Unity. I don't even know if it's being used in any way yet, but I figure it's maybe worth mentioning.
8 Replies
Replies have been turned off for this discussion
- Are you using the latest version of Unity? The current SDK requires 4.2.
- Definitely alarming that you get errors right out of the box with the Tuscany package. Are you running Unity 4.2? Maybe it could be helpful if you pasted some of the specific errors that you get.
- Ah. I finally kicked up to the Pro version, but not 4.2. Thanks! I imagine this'll fix what ails me. I'll let you know otherwise.
Much appreciated. - posting in this so I can find it later. Good luck!
- Yep. It turns out I was the bug in question.
If you do find a fix, please let me know. It's important to me. :D
UPDATE: I'm still encountering other issues, described below... - Hmm. Now I'm getting a terrible framerate ( about 20-30fps -- which I initially attributed to the increased detail in the Oculus World demo between 0.2.3 and 0.2.4 but now I'm not so sure) and Building the Tuscany Demo produces the following error:
Missing detail texture in Terrain, degraded loading performance
UnityEditor.BuildPlayerWindow:BuildPlayerAndRun()
I noticed a very sluggish framerate even in the standalone 0.2.4 Tuscany Demo. I've tried dropping the Anti Aliasing to 2x Multisampling from 4x but the results were the same.
On the plus side, I think it's pulling in my personal config file (IPD is showing as 67.9000).
This is on a MacBook Pro Retina 13-inch. Is it possible that the latest Demo has increased spec requirements? "craigotron" wrote:
This is on a MacBook Pro Retina 13-inch. Is it possible that the latest Demo has increased spec requirements?
Intel HD Graphics 4000 should not really be sufficient enough, but I agree that there was some kind of significant performance decline even just going from 2 viewports without warping and tracking, and switching to using the SDK itself. No idea about differences between the different versions since I still use SDK 0.2.1.- Ultimately, I got the minimal integration working nicely with custom terrain at 60fps, which is what I was going for anyhow. So I'm good.
Thanks, everybody!
