In every previous SDK release when I press play in Unity 4 I got this kind of view:
This also enabled head tracking, so I could grab the DK2 and use it as a 3D mouse to scan around the environment, quickly check draw calls and poly counts etc. I believe it only worked in extended mode or when I paused the Oculus service.
However with 0.6.1.0 I now get this static view, with no DK2 tracking:
Is this an intentional change for 0.6.1.0? With the stereo view it's easy enough to resize the window to an approx size for one eye but I really miss the DK2 tracking. I could write a mouse-look script or something but I found it very useful.
This also enabled head tracking, so I could grab the DK2 and use it as a 3D mouse to scan around the environment, quickly check draw calls and poly counts etc. I believe it only worked in extended mode or when I paused the Oculus service.
However with 0.6.1.0 I now get this static view, with no DK2 tracking:
Is this an intentional change for 0.6.1.0? With the stereo view it's easy enough to resize the window to an approx size for one eye but I really miss the DK2 tracking. I could write a mouse-look script or something but I found it very useful.
Don't suppose anyone has found a solution to this?
Basically 0.6.1.0 disabled headtracking, stereo view and gives completely erronous values for polygon count and draw calls (from the actual 50-100 to 300-400). It seems to be counting all the cameras in the scene including the helper one.
Switching to Direct X 11 mode fixes these issues but you run into the nasty Unity 4 | Android bug where lightmaps are overexposed like this:
Basically 0.6.1.0 disabled headtracking, stereo view and gives completely erronous values for polygon count and draw calls (from the actual 50-100 to 300-400). It seems to be counting all the cameras in the scene including the helper one.
Switching to Direct X 11 mode fixes these issues but you run into the nasty Unity 4 | Android bug where lightmaps are overexposed like this:
