ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread

I can`t get it to work.

I`ve looked for fixes, but there are none to be found.

NOTE: the so called fix on this forum isn`t a fix, it`s just how you set up the rift and i`ve done this- it works fine. It just won`t work with Elite.

So have you got the rift set as your second monitor? And in the config utility it's set to extended display? And when you load Elite on your monitor, then select secondary display, and under vr mode select oculus rift with headphones and that's how you do it. Are you doing any of those things differently?

Note I'm on an older AMD cpu so on previous versions I had to unplug the camera on my DK2 to get it working.
 
I can`t get it to work.

My DK2 works fine with every demo and i use it with Cineveo without issue.
It won`t work with Elite, however.

Whenever i activate the DK2 all i get are split screens that don`t overlap. Each of those screens also extend far beyond the borders of the lenses so i`m sitting there with two screens on which i really can`t see anything.

Was hoping beta 2 would fix it, but no.

I`ve looked for fixes, but there are none to be found.

NOTE: the so called fix on this forum isn`t a fix, it`s just how you set up the rift and i`ve done this- it works fine. It just won`t work with Elite.

Firstly just double check that you are on the most recent Oculus rift runtime (0.4.2) and you are on the most recent firmware (2.12).
Doesn't take long to check and if it's those things then you'll spend ages jumping through hoops trying to resolve the issue when you could have resolved it quickly if you'd just double checked.

IF you are on the most recent versions then I would suggest turning the rift off and starting up the game.

Change the settings so you can play it AOK on the monitor (and test it, have a little fly around) and then exit the game. Restart the game with the DK2 turned on and in Extended mode.
Go into the options, make sure you select the correct display for the DK2, make sure you have selected the correct resolution for the DK2 (1080p unless you are supersampling and I'd suggest not doing this till it works normally)). Set it to Oculus rift speakers or headphones. Apply and ensure it displays AOK on the rift. If it's not imediately OK try a quick PC reset to be sure.

If that doesn't work close the game down and go back to your desktop. With the rift on and in extended mode go to your screen resolution settings. Ensure that you DK2 is setup as 1080p resolution and 75hz refresh rate. If not put them to those settings and retry the game again (double check the graphic settings to ensure everything is OK in there and you are on 1080p/74hz).

Post back here if that doesn't work.
 
Last edited:
For those who have low Fps.
Set vsinc off and regulate your framerate in your gpu settings set that to maximum 77frames
Or so. This will gain you a few frames because your monitor isn't cutting off the half rendered ones.

Cheers
 
Whenever I use the Oculus in game, it kinda keeps 'greying out' the image from grey to color constantly, Im definitely sitting in the tracking volume and press F12 to re-center and it keeps doing this. It works fine on other Oculus demos but in Elite this is a constant problem for me.
 
Whenever I use the Oculus in game, it kinda keeps 'greying out' the image from grey to color constantly, Im definitely sitting in the tracking volume and press F12 to re-center and it keeps doing this. It works fine on other Oculus demos but in Elite this is a constant problem for me.

Double check runtime and firmware versions. At a guess the other demos are using an older version of the SDK while E: D now uses 0.4.2 and maybe that's causing the issue.

If they're up to date then I'm not sure, try wiping the camera lens :)
 
For those who have low Fps.
Set vsinc off and regulate your framerate in your gpu settings set that to maximum 77frames
Or so. This will gain you a few frames because your monitor isn't cutting off the half rendered ones.

Cheers

Good tip, thanks. Have some rep. :)
 
ED isn't finding my DK2 - and I have the latest beta runtime installed... I tried direct and extended screen modes... no joy.

Any tricks?
 
Last edited:
Yepyep I did update last night but I'll try again

Double check runtime and firmware versions. At a guess the other demos are using an older version of the SDK while E: D now uses 0.4.2 and maybe that's causing the issue.

If they're up to date then I'm not sure, try wiping the camera lens :)
 
ED isn't finding my DK2 - and I have the latest beta runtime installed... I tried direct and extended screen modes... no joy.

Any tricks?

Can you explain what you mean by it "isn't finding" your DK2?

When you have Extended mode enabled and the Rift switched on, can you see a desktop through Windows?

Is it arranged to the left of your main monitor?

Can you specify a monitor in E: D graphics options?

Can you select 'Oculus Rift (Headphones)' in 3D mode?
 
Yepyep I did update last night but I'll try again

Always best to double check the easy stuff before you start looking for more esoteric fixes for issues. If I had 10p for every issue that turned out to be something simple that was overlooked because someone (in some cases me) was sure it was the case then....well.. I wouldn't be a rich man but I'd have a few extra quid :)
 
I'm struggling here guys, I have the latest runtime (0.4.2) etc.. and can get to the menu and change over to my Primary monitor and set the Refresh Rate up to 75hz - however, when I try play the game (open play) I see the orange sidey for a brief second then I am left staring at a black screen! Anyone else had this and managed to resolve it?
 
I'm struggling here guys, I have the latest runtime (0.4.2) etc.. and can get to the menu and change over to my Primary monitor and set the Refresh Rate up to 75hz - however, when I try play the game (open play) I see the orange sidey for a brief second then I am left staring at a black screen! Anyone else had this and managed to resolve it?

That's a server issue atm. Try the tutorials, they should work.
 
I'm struggling here guys, I have the latest runtime (0.4.2) etc.. and can get to the menu and change over to my Primary monitor and set the Refresh Rate up to 75hz - however, when I try play the game (open play) I see the orange sidey for a brief second then I am left staring at a black screen! Anyone else had this and managed to resolve it?

I have ticketed this (as have a ton of other people) - and the ticket has been changed to 'resolved'. Patch later today should fix it.
 
Having lots of trouble here. First, this is my setup:

Hardware

  • Core i5-3570K @3.40GHz
  • GeForce GTX 770
  • 16 GB RAM
  • Asus display at 1920x1080 60Hz (display supports up to 2560x1440), connected via DVI
  • Oculus Rift DK2 connected via DVI-HDMI adapter
  • Saitek X52 HOTAS

Software

  • Windows 7 Professional 64-bit
  • Oculus Runtime 0.4.2
  • Oculus Firmware 2.12
  • DK2 HMD set to extended mode, secondary screen
  • Oculus service running. Tried both 32-bit (default) and 64-bit versions

Game settings

  • Set 3D mode to Oculus Rift (Headphones)
  • Display set to secondary
  • Resolution set to 1920x1080
  • Refresh rate set to 75 Hz (non-selectable)
  • Graphics settings set to HIGH (I had it on custom for better graphics, symptoms remained the same)

Symptoms

  • In the load screen for the tutorials: Orange spinning ship appears for a fraction of a second, then disappears. The mission text remains there while the mission loads.
  • Lots (LOTS) of ghosting/judder on the DK2 if I turn my head. Game runs silky smooth if I keep my head stationary.
  • From the tutorials, the game freezes when I go back to the main menu. Music keeps playing, but even the positional tracking stop workings and the Rift shows a static main menu.
  • When loading the online mode solo, the orange spinning ship appears for a fraction of a second, then it and the mission text both disappear and the screen stays black after a LONG time afterwards the game loads.
  • Have been unable to play the open game yet. Seems to never end loading.
  • After playing for a while, the ghosting disappears and the game runs smoothly. Not sure at what moment the transition happened.
 
I have ticketed this (as have a ton of other people) - and the ticket has been changed to 'resolved'. Patch later today should fix it.

I have had fun playing Beta 2.0 today - in solo because of the multi player / server problems.

Just restarted the launcher and it forced me to choose 'Upgrade', not quite sure what that was about. Will retest now :D (nothing on the Launcher news suggesting the patch is out)

--------------------
*UPDATE : Galaxy map IS now working for me 'online' and the sky/stars are back. Was able to SC to another location for the first time BUT still getting kicked out a lot (says server disconnect) so going back to solo for now.

**PS message just came up saying' Beta 2.01 now released' so I must have just got lucky with timing. Or maybe not as it now says I can't start (online or solo) as my 'Client is too new'. LOL my client says Beta 2.01 so perhaps they are updating the backend now? Patience ... back in now :p
 
Last edited:
I have had fun playing Beta 2.0 today - in solo because of the multi player / server problems.

Just restarted the launcher and it forced me to choose 'Upgrade', not quite sure what that was about. Will retest now :D (nothing on the Launcher news suggesting the patch is out)

Oh, I just saw the upgrade as well. Testing it now. :)
 
Back
Top Bottom