Skip to main content
KaTsuoo1
Up and Coming
August 23, 2014

Unable To Develop Games

I got the 0.4.1 SDK, 2.11 Firmware and the DK2 shows up fine in the Configuration Utility. However, in Unity, I can't get it to work properly.

When using Extend Desktop to the HMD, I see the game view, but it appears where my scene window is. That only works for the default layout, where the scene window and game window is in the same place. If I drag the game window somewhere else, over to the rift screen for example, then both windows just show black.

When using Direct HMD Access from Apps, I don't see anything at all.

When I try to play the DirectToRift build of my game, then it just gives me the error message, Oops! The game crashed.

The only way I was able to make it work was when I played it in extended. Now I even have the problem that the game goes to fullscreen on my monitor, without giving me any launcher. Even if I could get it to give me a window, or mirror the displays, it still would not be acceptable. I need to be able to try my game as I'm developing it, just like I could with the DK1.

Unity works fine if I create a game without the DK2, so it is not Unity itself that's the problem.
    This topic has been closed for replies.

    3 replies

    Marbas
    Up and Coming
    August 23, 2014
    Testing from the Unity editor it's a mess. So I always test my Unity stuff with builds, which seems to work most of the time in direct-to-rift mode. Sometimes the build wont start, I just get a black screen like you described. Try re-running your build a second or third time and it should work. What I really miss is being able to run any rift app in Clone-mode, like on the DK1. So much easier! Please Oculus, give us Clone mode functionality back for the DK2.
    KaTsuoo1Author
    Up and Coming
    August 23, 2014
    "Marbas" wrote:
    Testing from the Unity editor it's a mess. So I always test my Unity stuff with builds, which seems to work most of the time in direct-to-rift mode. Sometimes the build wont start, I just get a black screen like you described. Try re-running your build a second or third time and it should work. What I really miss is being able to run any rift app in Clone-mode, like on the DK1. So much easier! Please Oculus, give us Clone mode functionality back for the DK2.


    Thank you for the reply.

    I liked having the game window on the rift, so whenever I wanted to try something, I could just put on the headset. But I guess it could be a hassle for someone that looks more often on the game window and also want to see the scene view at the same time.

    It's when I do extended that the game starts, but I just see a black screen. I have tried starting it countless times, no difference. In fact, if I press space, then the usual window appears with frame rate and all that. If I keep pressing space, then the different windows stack on top of each other, rather than cycling through them.

    When I try it in DirectToRift, that is when it just crashes and a window pops up, that says: "Oops! The game crashed..." etc. I doubt the rest of the message is of any use.

    However, I got the DirectToRift build to work, when I set it to Extend Desktop to the HMD. And it didn't appear to play like it would be extended, it played more like if I would have set it to Direct to rift in the Utility. The question would now be, am I getting the benefits from DirectToRift, since I have set it to extended in the Utility?
    vrdaveb
    Inspiring
    September 9, 2014
    "Marbas" wrote:
    What I really miss is being able to run any rift app in Clone-mode, like on the DK1.

    If you use extended mode and set Game view to "Maximize on Play", it should work fine with display mirroring. Does that work for you? Sorry for the experience in the editor. We are making progress toward improving that.

    "KaTsuoo1" wrote:
    The question would now be, am I getting the benefits from DirectToRift, since I have set it to extended in the Utility?

    Yes. DirectToRift makes the app run full-screen on the Rift whether you're in direct or extended display mode. It also sets the correct resolution and full-screen/windowed mode, which may fix your startup crash.
    Terms & ConditionsAccessibility statement