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

I've got the same issue. Demo scene works fine in Direct Mode but when I start Elite it shows the Rift doubled view with head tracking and everything...just on my regular monitor. The only option is "primary monitor" in the game.
Did you make sure the OR Service is running in windows?
 
I got my DK1 a long time ago, and the DK2 on July 30th. Adding my name to the list.

------------------------------
Please keep the following text in when updating, so everyone knows what's what...
Green for shipped/delivery.
Yellow for paid and confirmed next batch.
Dates are in UK format, Day / Month / Year
Times are in 24hr format, time zones are all PDT, use this site to convert from other time zones:
http://www.timeanddate.com/worldclock/converter.html

If you quote the text to edit, remove the quote block before saving otherwise others can't then use quote to update.

01/07/2014 @ 09:42 PDT - Baton
01/07/2014 @ 16:12 PDT - Anthony Jones
04/07/2014 @ 02:54 PDT - Juniper

11/07/2014 @ 02:00 PDT - brumster
16/07/2014 @ 14:31 PDT - CMDR Pham Nuwen
23/07/2014 @ 12:28 PDT - Jhondidfool
25/07/2014 @ 02:38 PDT - Technotica
27/07/2014 @ 01:54 PDT - Mark D
28/07/2014 @ 03:31 PDT - Mumrah
30/07/2014 @ 00:01 PDT - CMDR JAVILM
02/08/2014 @ 12:15 PDT - RaistlinUK
05/08/2014 @ 05:33 PDT - Viajero
05/08/2014 @ 05:59 PDT - Mikevet
06/08/2014 @ 04:53 PDT - Hadron42/Cmdr Jonathan E
06/08/2014 @ 07:33 PDT - Coolts
08/08/2014 @ 04:07 PDT - Tomas
08/08/2014 @ 14:13 PDT - Ceud
16/08/2014 @ 12:56 PDT - Ref Minor
17/08/2014 @ 12:42 PDT - Pannad
19/08/2014 @ 06:36 PDT - KickahasTier
22/08/2014 @ 07:57 PDT - Nomadski
23/08/2014 @ 02:44 PDT - si77
24/08/2014 @ 06:40 PDT - Carcharodon
26/08/2014 @ 06:16 PDT - Dooguk
28/08/2014 @ 02:07 PDT - Jim Chapman / CMDR Turnip
29/08/2014 @ 12:51 PDT - MadMossy / CMDR MadMossy
31/08/2014 @ 12.10 PDT - Kroenen
 
First Testing:

- Direct Mode didn't work
- Extended Desktop Mode work fine in Menu, but when I want to start a Tutorial Mission it freeze on the Loading Screen.

Without DK2 it loads the Tutorial.

As I expected we need 1-2 Hotfixes... never play on Patchday. ;)
 
Did you make sure the OR Service is running in windows?

Yeah, restarted it as well. Restarted PC, ran demo scene in direct...nothing got direct working :(

Fortunately, it worked when I set it to extended (service still running) and made the Oculus my only display via Win-P to avoid any refresh rate issues. Got booted a lot but that's just server stuff to be expected. Had the issue I saw mentioned elsewhere where sometimes there were no stars and the "particles" moved around me weirdly.

Even with those (to be expected) issues at the launch of a huge update, it was a huge improvement. Barely any stutter in stations, in space and in battles it's almost perfect. Everything looks much crisper and cleaner and I'm looking forward to playing some more tomorrow when I get home from work. For now I'll let the server issues settle down and get some sleep :)
 
Has everyone updated the Oculus runtime to 4.2? According to the patch notes, Beta 2 is incompatible with earlier versions of the runtime.
 
Yep, 4.2 here.

Initially had direct mode working fine, but very poor framerate (but very sharp display). went to check CCC settings as I appeared unable to set 75fps in config, DK shows as disabled (as it should). Went in Oculus config to set the DK as extended; got a blue screen!!!

On reboot, have been unable to set direct DK in game (works fine with Oculus config test). Uninstalled, and re-installed the OR drivers to no avail.

Have not been able to reproduce the blue screen, DK works fine as direct or extended (minus in ED...) and getting poor frame rates (crossfire not working properly).

Will wait for patch :(
 
Yep, having serious issues here. SLI & Direct Mode doesn't work even with latest firmware & runtime, and in trying to turn it off, somehow my NVidia drivers have uninstalled themselves, so I'm updating again.

Going to try direct mode with SLI disabled next.

I particularly like how enabling/disabling SLI requires me to shut down like 8 programs before the changes will take effect, that's just great, that is.
 
WoW I can`t believe how beautiful this game looks now with the DK2, it`s like a new game. Forget everything you have seen in beta 1, it`s a new dimention in every aspect, I can almoust touch the freacking planets jesus.
:eek::eek::eek:
 
Got to play for a while tonight and holy hell, what an improvement. Massive "resolution" increase so to speak, I can see more, more clearly than ever before by a mile. Menus are MUCH easier to read (even though I always could read them) just a massive improvement.

Going to try SLI tomorrow and see how that goes as I got a wee bit of ghosting in congested areas, so hopefully that'll help.

Wish I wasn't so tired and kids didn't have school in the morning but, for me anyway, this is a massive improvement. Just awesome.
 
Direct mode does not work for me too.
Extended mode works. but when I exit ED it does not close the window and i have to kill it with task manager.
also im having issues with lens flairs not looking right and something weird happening to my ships windshield transparency .
 
Ok yeah, Direct Mode is still a no go, but SLI is working.

Direct Mode plus SLI caused my machine to completely crap itself, had to hard reset to get it back.
 
Hi

I'm having a problem getting the DK2 working too. I have firmware version 2.11, and I don't see an option for Rift mode in 3D settings. I've also tried Direct and Extended modes (in Direct mode there's no secondary display shown).
I've also tried:
Turning off legacy support of the config utility
Restarting the service.

No, luck so far

Any suggestions guys?
 
I'm using a "lowly" 660ti and if anything performance is worse for me. In stations or asteroid areas there is a strange "ghosting" where the graphics smear all over the place when I turn my head side to side...

In 1.06 I would get some judder due to low fps but at least there was no smearing like I see now...
 
Direct Mode worked first time for me, but Crossfire didn't. Was quite sharp image wise, but very jerky - particularly the Galaxy map which was unplayable. :(

So I fiddled with the in-game graphics settings to try and eek out more performance to help with the judder, and now the game doesn't display in the Rift at all - only a monitor (in Rift mode). Head tracking still works though. Demo scene still works fine.

Got to go to work now, but will try again later tonight. Hopefully a patch will be available by then.

Edit: 2 x Msi 7870s, Oculus 0.4.2 runtime, 2.12 firmware.
 
4.2 here, extended mode, service running.

Ghosting is essentially GPU lag, if you're below 75fps you get ghosting and the more it drops the worse ghosting gets. Very little ghosting for me, just the usual hard hitting fps areas.

Hopefully SLI will fix that for me.
 
Hi

I'm having a problem getting the DK2 working too. I have firmware version 2.11, and I don't see an option for Rift mode in 3D settings. I've also tried Direct and Extended modes (in Direct mode there's no secondary display shown).
I've also tried:
Turning off legacy support of the config utility
Restarting the service.

No, luck so far

Any suggestions guys?

All I can find in the Beta2 change log about this is:
- If Oculus Rift isn't present or the SDK could not be initialised, don't show the Oculus Rift options in the 3D dropdown list part of the graphic options menu

http://forums.frontier.co.uk/showthread.php?t=43776

EDIT: Other Rift updates:
- Fix for crash when shutting down the game by clicking on the close button while rendering to Oculus Rift
- Fix for GalaxyMapCamera when Oculus Rift is enabled
- Make sure the reference camera, which is used to provide the rendering service with a projection matrix, uses FOV and aspect ratio taken from the stereo cameras when Oculus Rift is enabled
- Radar not being displayed on hyperspace when rendering to Oculus Rift fixed
- Give the stereo extra display (used for showing the undistorted image of the left eye on a separate window) a default size which is more suited to DK2
- Time warp fixes for Oculus
- Updated Oculus SDK to version 0.4.2. This SDK isn't compatible with runtimes 0.4.0 and 0.4.1, so installation of runtime 0.4.2 is mandatory
- Added the setting 'Oculus Image Quality', a slider that controls the parameter 'Pixels per Display Pixel' passed to the SDK when calculating the recommended texture size. This gives users more control to find the right balance between quality and performance for their particular setup. Since low values of the setting can have a very dramatic effect (e.g. text can become unreadable), the user is asked to confirm the selection even when only this setting has been changed (using the already existing confirmation dialog). The slider is only enabled if stereo mode is set to Oculus Rift, and it will not be shown in the graphic options screen if an Oculus Rift wasn't detected
- Disabled depth testing for the landing pad schematic material as its billboard is now partially occluded by the cockpit after the Oculus depth
- When disabling Oculus stereo mode, if using Direct Access, make sure the swap buffer gets recreated
 
Last edited:
Back
Top Bottom