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

grodenglaive

grodenglaive
SilverlightPony said:
I haven't been able to get the Rift working in the combat tutorial demo at all. No matter what I do, the game never gives me an Oculus Rift option in the 3D graphics settings menu. :(
Click to expand...

the_wretched said:
It is possible the OR support is not in the demo? Haven't tried that...
Click to expand...
someone posted in the oculus forum that it works in the demo version. Weird that you don't even get the option... was your rift plugged in at the time?
 

wowwow9

W
Is anyone experiencing judder using rift? Judder improved after gamma released but it still occurs.
I set the resolution to 1366x768 and all graphic settings to "low", the judder gone but I can't see the words clearly because the resolution is too slow.
here is my configuration:
iMac late 2012 version, bootcamp to Win7 64bit
i7 3.9GHz
32GB ram
GTX 680MX 2GB ram
Oculus rift DK2 0.4.3 runtime
 

BoggiBlanko

BoggiBlanko
SilverlightPony said:
Plugged in and turned on. Tried both direct and extended mode, no luck.
Click to expand...

Try this: Before you start the game hold the windows button and press p.. then go to the right (only projector) look through the rift (I know its not easy) and start the game... Also make sure you set the display mode to extended in the Oculus Rift Config!
 

SilverlightPony

SilverlightPony
Mark D said:
Hi SilverlightPony,

Sorry if I missed it but is the Oculus desk demo working OK?
Click to expand...
It's been a while since I ran it, but it worked fine when I did. It also works fine in Alien: Isolation.

BoggiBlanko said:
Try this: Before you start the game hold the windows button and press p.. then go to the right (only projector) look through the rift (I know its not easy) and start the game... Also make sure you set the display mode to extended in the Oculus Rift Config!
Click to expand...
I'm on a desktop, not a laptop. And as I said, I've tried with both Direct and Extended mode. And there is no way in Hades I am disabling my other screens entirely just to get the Rift to work, that's absurd.
 

fviktor

F
Gamma 1.0.3 issue: F12 does not calibrate the front direction of DK2's head tracking any more

New Oculus Rift DK2 problem: As of Gamma 1.0.3 the head tracking calibration seems to be broken. On pressing F12 nothing happens, then some random seconds/minutes later it suddenly calibrates, but to the then current (essentially random) head position. It makes ED unplayable with Oculus Rift unless you already have the correct head tracking "front" direction calibrated.

Created ED Ticket #53018 for this
 

Juniper

Juniper
fviktor, it's good that you're filing tickets, but nobody else is allowed to view your tickets so there's no point in linking them. :)
 

fviktor

F
fviktor said:
Gamma 1.0.3 issue: F12 does not calibrate the front direction of DK2's head tracking any more

New Oculus Rift DK2 problem: As of Gamma 1.0.3 the head tracking calibration seems to be broken. On pressing F12 nothing happens, then some random seconds/minutes later it suddenly calibrates, but to the then current (essentially random) head position. It makes ED unplayable with Oculus Rift unless you already have the correct head tracking "front" direction calibrated.

Created ED Ticket #53018 for this
Click to expand...

Workaround:

- Edit config file: %AppData%\Local\Frontier Developments\Elite Dangerous\Options\Bindings\Custom.binds
- Modify the primary key in <OculusReset> to something which works. Make sure you don't make a duplicate with this.

Is this binding available on the in-game Options / Controls menu? I cannot seem to find it...

BTW, Gamma 1.0.3 periodically resets the head tracking, the timing seems to be completely random and does not depend on the key mapped. The default mapping of F12 just collides with some in-game menu now.

I stop playing ED with DK2 now due to the too many issues. DK2 will be useful for other games/things, however. For example Minecrift works perfectly with that. :)
 

CHristina

CHristina
***************************************JUST TO NOTE***********************************

DISCOVERED THIS.
IN ED graphic options.
when setting to 75hz.
if ,like me ,you though it was coloured red = not accessible.
EVEN IF THIS SETTING IS 'FADED OUT " =COLOURED RED.. YOU CAN STILL ACCESS this 'Panel' and CHANGE IT to 75hz.
 

Soliloquy

Soliloquy
CHristina said:
if ,like me ,you though it was coloured red = not accessible.
EVEN IF THIS SETTING IS 'FADED OUT " =COLOURED RED.. YOU CAN STILL ACCESS this 'Panel' and CHANGE IT to 75hz.
Click to expand...
Huh! That is interesting! I will try it once I get home tonight. I think it may be related to my low persistence issues.
 

the_wretched

T
fviktor said:
Gamma 1.0.3 issue: F12 does not calibrate the front direction of DK2's head tracking any more

New Oculus Rift DK2 problem: As of Gamma 1.0.3 the head tracking calibration seems to be broken. On pressing F12 nothing happens, then some random seconds/minutes later it suddenly calibrates, but to the then current (essentially random) head position. It makes ED unplayable with Oculus Rift unless you already have the correct head tracking "front" direction calibrated.

Created ED Ticket #53018 for this
Click to expand...

That is weird. My costom binding (middle mousebutton) works fine in 1.03. I use the mouse button as I find it much easier to locate with my headset on and can reach it without leaning forward, unlike the F12 key.
 

[VR] Mad Mike

[VR] Mad Mike
fviktor said:
Gamma 1.0.3 issue: F12 does not calibrate the front direction of DK2's head tracking any more

New Oculus Rift DK2 problem: As of Gamma 1.0.3 the head tracking calibration seems to be broken. On pressing F12 nothing happens, then some random seconds/minutes later it suddenly calibrates, but to the then current (essentially random) head position. It makes ED unplayable with Oculus Rift unless you already have the correct head tracking "front" direction calibrated.

Created ED Ticket #53018 for this
Click to expand...

really? that is strange. I played for an hr or so last night and didnt have that.

hope you get it sorted for yourself however.
 

Soliloquy

Soliloquy
CHristina said:
DISCOVERED THIS.
IN ED graphic options.
when setting to 75hz.
if ,like me ,you though it was coloured red = not accessible.
EVEN IF THIS SETTING IS 'FADED OUT " =COLOURED RED.. YOU CAN STILL ACCESS this 'Panel' and CHANGE IT to 75hz.
Click to expand...
I just tested this, and as far as I can tell, it doesn't work. It looks like you're changing the red settings, but the change doesn't stick. Next time you go into that menu, the setting has returned to what it was.

In other news, after the last update, low persistence now seems to work regardless of whether DK2 is primary or secondary monitor. Still have to turn the Oculus Image Quality slider down to about 50% to avoid juddering, though. Maybe I just have to buy a stronger GPU.
 

elkar

elkar
Jaeger said:
But I'm getting along just fine with a 670M so... huh?.
Click to expand...

Usually _60 is old chip and _70 and above is new one. with _60 being mainstream and _70+ above average. So there can be usually big differences. But it still doesnt sound right. 670M is small card for laptops, i always thought it's never on par with normal full size PC ones. So 670>670M.
 
You must log in or register to reply here.
Back
Top Bottom