Forum Discussion
Problems with the screen image using SDK 0.4
I've googled like crazy, but I can't seem to find anything about this issue. At first, I thought it had something to do with upgrading the SDK, but it's happening on fresh, untouched projects as well. I can't figure this out.
This is what is being output on a fresh, empty scene with the OVRCameraController placed in the scene and the background set to green. "No sensor detected" also pops up. I tried googling that as well, and all that came up was people having issues playing older Oculus Rift games on the DK2.
It's really, really hard to find any solutions through all of the buzz the oculus rift generates outside of the development community, so I apologize if this has been asked before.
This is what is being output on a fresh, empty scene with the OVRCameraController placed in the scene and the background set to green. "No sensor detected" also pops up. I tried googling that as well, and all that came up was people having issues playing older Oculus Rift games on the DK2.
It's really, really hard to find any solutions through all of the buzz the oculus rift generates outside of the development community, so I apologize if this has been asked before.
9 Replies
Replies have been turned off for this discussion
- I'm not seeing the problem. Could you describe more what it is that's wrong?
Do you have a development kit plugged in or not? - The problem is visible in the screenshot. The images seem to be too low, past the bottom of the screen, and the top of the screen has no image at all. The dev kit is plugged in.
- Can you get the test scene from the Oculus Config tool to render correctly?
- Yes, the test tool and other compiled unity demos work correctly for me.
- Hmm... This might sound silly but did you restarting your computer and reimporting everything?
- Just did. I'm getting the same issue.
- It seems to render correctly both in editor and in the builds when I set the rift's display mode to direct. Positional and motion tracking don't work either way, however. This is only happening to my builds. I've run other peoples' builds with no issues in any mode they support.
- In my experience that is just how it renders if there's no HMD connected and it can't get the correct distortion variables - which is why the viewports appear to be too low.
It's likely not a rendering issue but an issue with detecting the HMD correctly in the first place. - Weird. The plugin must not be working in my editor or builds. It's working in other peoples' builds.
