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

KING5TON

KING5TON
Have my 980 overclocked to 1355Mhz base, 1444Mhz boost. Memory left at stock.
Playing on the High preset with Vsync off.

In stations I still see drops below 75fps, the minimum I saw it drop to was 60fps but that was only for a second, mainly it fluctuated between 80 and 65fps depending on where I was in the station (i.e. docked and looking at the station from the outside seemed the worst).
Ring systems seemed OK though, saw one drop to 70fps for a second but it mainly fluctuated between 80 and 75fps.

You have to really look for judder though, if you weren't looking for it I think you wouldn't really notice. with AA off/Shadows lowered etc.... I'd be surprised if it dipped below 75fps at all.

I did record a video but it's a bit wonky due to it being recorded in portrait, tried rotating it and uploading to youtube but the output wasn't that good and you couldn't really make out the FPS so I abandoned it.

Will repeat the process on Tuesday/Wednesday with Beta 2 and report back.
 

Georgio

Georgio
I know it seems obvious but if you're in the Rift view anyway, surely you can get better performance if the display to your monitor is disabled so that all resources can go to the Rift display - or is this too simplistic?
 

Sanderson

Sanderson
Mad Mike said:
On my machine it does not display to monitor at all in ED in the rift.....
Click to expand...

Mine also. Singlr GTX770 atm, butter smooth except in stations, while multiplayer (all group) is completely unplayable. Screen locks once a second no matter what I do. Not really jutter, more like skipping. Not sure it's DK2 related though.
 

RaistlinUK

R
Bargain of the century or just been taken for a ride

Just bought a Saitek X52 pro on eBay for £50 used boxed excellent condition to use on my rift setup. This is what the joystick and throttle in game are based on isn't?
 

Obsidian Ant

Obsidian Ant
KING5TON said:
Have my 980 overclocked to 1355Mhz base, 1444Mhz boost. Memory left at stock.
Playing on the High preset with Vsync off.

In stations I still see drops below 75fps, the minimum I saw it drop to was 60fps but that was only for a second, mainly it fluctuated between 80 and 65fps depending on where I was in the station (i.e. docked and looking at the station from the outside seemed the worst).
Ring systems seemed OK though, saw one drop to 70fps for a second but it mainly fluctuated between 80 and 75fps.

You have to really look for judder though, if you weren't looking for it I think you wouldn't really notice. with AA off/Shadows lowered etc.... I'd be surprised if it dipped below 75fps at all.

I did record a video but it's a bit wonky due to it being recorded in portrait, tried rotating it and uploading to youtube but the output wasn't that good and you couldn't really make out the FPS so I abandoned it.

Will repeat the process on Tuesday/Wednesday with Beta 2 and report back.
Click to expand...


Looks like the GTX 980 has some great performance then! Thanks for posting this. :)

I just went and did some tests for the sake of comparison on my GTX 780. I'm using a DK1, so it won't be direct comparison, but it gives an idea.

I set the resolution to 1920x1200:

Supercruise: 56fps
Federal Distress: 48 - 57fps
Hathor Rings: 50-57fps
Dahan Station Outside: 52 - 62fps
Inside Station: 26-32fps :eek::eek:

And at 1280x800:

Supercruise: 89-95fps
Hathor Rings: 80-85fps
Dahan Station Outside: 72+ fps
Dahan Inside Station: 60-62fps


My specs:
i5 2500k
GTX 780 SC
8gb Ram

All at stock speeds.
 

Gilmir

Gilmir
RaistlinUK said:
Just bought a Saitek X52 pro on eBay for £50 used boxed excellent condition to use on my rift setup. This is what the joystick and throttle in game are based on isn't?
Click to expand...

X52 pilot here, as well ;)
The ingame stick is definitely based on this one. Throttle somewhat.
It's funny though, as the animations don't really match unless you use the default bindings (which suck imho). So if you eg rebind yaw to the x axis and the rotation to roll (which works perfectly with this stick) the stick ingame moves left/right when you actually twist it.

Anyway - it's really great to fly once you set up everything.
Currently I never touch the keyboard while in ED. You just have to get to know the profiler a bit to deactivate the mouse functionality of the throttle.
 

Juniper

Juniper
At the moment, I get lots of judder with my DK2 - especially in stations, but pretty much everywhere else too.

I have three monitors, but even disabling two of them doesn't make a difference, which is rather odd to be honest.

I'm running two AMD 7870s which are Crossfired together (which I know E: D doesn't yet support) so I'm hoping that the introduction of CrossfireX support & direct mode for the DK2 will give me smooth(er) performance.

Right now though, although it looks & feels awesome, the judder makes it hard to play for any length of time... and that's disappointing. :(
 

Adam Lusardi

A
Juniper said:
At the moment, I get lots of judder with my DK2 - especially in stations, but pretty much everywhere else too.

I have three monitors, but even disabling two of them doesn't make a difference, which is rather odd to be honest.

I'm running two AMD 7870s which are Crossfired together (which I know E: D doesn't yet support) so I'm hoping that the introduction of CrossfireX support & direct mode for the DK2 will give me smooth(er) performance.

Right now though, although it looks & feels awesome, the judder makes it hard to play for any length of time... and that's disappointing. :(
Click to expand...

Have you tried just one. I have one but cannot safely say no judder as I maybe not susceptible to it and cannot run the camera yet till B2
 

Juniper

Juniper
Adam Lusardi said:
Have you tried just one. I have one but cannot safely say no judder as I maybe not susceptible to it and cannot run the camera yet till B2
Click to expand...

No I haven't... although I'm not sure how much of the second card it's using. Certainly all my monitors (including the DK2) are plugged into the one card.

To be honest, I'm not going to go messing around in the innards of my PC and remove cards etc when Tuesday may solve all my problems (and if not, then I start investigating fully).

I was just having a bit of a moan. :p :D
 

Rewind303

R
KING5TON said:
Have my 980 overclocked to 1355Mhz base, 1444Mhz boost. Memory left at stock.
Playing on the High preset with Vsync off.

In stations I still see drops below 75fps, the minimum I saw it drop to was 60fps but that was only for a second, mainly it fluctuated between 80 and 65fps depending on where I was in the station (i.e. docked and looking at the station from the outside seemed the worst).
Ring systems seemed OK though, saw one drop to 70fps for a second but it mainly fluctuated between 80 and 75fps.

You have to really look for judder though, if you weren't looking for it I think you wouldn't really notice. with AA off/Shadows lowered etc.... I'd be surprised if it dipped below 75fps at all.

I did record a video but it's a bit wonky due to it being recorded in portrait, tried rotating it and uploading to youtube but the output wasn't that good and you couldn't really make out the FPS so I abandoned it.

Will repeat the process on Tuesday/Wednesday with Beta 2 and report back.
Click to expand...

Nice. So the 980 needs a little more oomph currently than the standard clock it would seem. With the dk2 optimisation aparently happening on Tuesday's b2 all should be gravy!
 

Juniper

Juniper
Adam Lusardi said:
Yes Tuesday should be fun I'm hoping my one 7970 will hack it as just up graded from a formidable 6870 due to the Rift.
Click to expand...

I hope it works well for you... it should do.

BTW, I suspect the reason why the camera doesn't work for you is because you haven't stopped the OVRService.exe. That fixes the problem in 99% of cases I've heard.
 

Adam Lusardi

A
No I suffer from the AMD SSE4.1 RISC problem.

Side note I went to play the other day, got bad drift in the station twisting my neck to raise landing gear whilst having to twist the head set around my face to keep the right menu up, I accidently hit the boost button. Well that ended my testing till B2.
 
Last edited:

Pham Nuwen

Pham Nuwen
Hi, I finally received my dk2 and was able to get it working without to much of a fuss using the 0.4.2 Oculus runtime and Elite 1.06.

The problem that i'm having is that my IPD is much lower than the average of 63.5 mm. This makes everything completely blurry since i'm looking through the sides of the lenses instead of the centers. I was able to mod my rift and bring the lenses closer together (with some cardboard and duct tape lol) and everything is incredibly sharp now. But in order for this to work properly i need to be able to adjust the lens separation values in software as well. If i don't then my eyes diverge and i get a really bad double image. I can easily adjust the lens separation in my own engine and Half life 2 even has a variable for it that you can change but unfortunately Elite Dangerous does not. I found directions for a hack from vr-gear.com (He sells a 3d printed lens adapter as well):

Download a Hex editor like HxD or Hex Edit.
Locate the right .dll/.exe to edit. (See lower down how to find those).
Backup the .dll/exe in case you want to revert / mess it up.
Open it in the editor and Search for Hex 4A0C823D, this is equivalent to the float value 0.0635f (which is the LensSeparation variable in the SDK in OVR_Stereo.cpp) - make sure the search dialog is set to "Hex-values" not Text-values.
Fortunately, this value is only used for LensSeparation in the current SDK version and often only appears once in games and demos. If you find a second, then that is a bit trickier because that value might be used elsewhere in the game/demo's logic. In that case trial and error or locating of other Oculus variable in the proximity can help.
Replace that value with the corresponding value (below) for your Lens Separation Attachments. Do not set it to your IPD, it must be in accordance to the new Lens Position.
(See this post if you want to know how/why this works: https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=11190&start=120#p171036)
69.5mm = 04568E3D
59.5mm = 46B6733D
Save and share your experience. I doubt there has been much focus on it by Oculus so it may well not work as intended and perhaps a slightly different value may work better for you.

Elite: ED\EDLaunch\Products\FORC-FDEV-D-1002\EliteDangerous.exe - There are two instances, the first one in block CE19CB-CE19CE is the one. Figured this out by trial and error, changing the other one crashes multiplayer :p
Click to expand...

But it doesn't seem to change anything. The offsets are also different so i'm guessing this was done on a older version of Elite. I was able to get the hack to work on the Tuscany demo but only on the older 0.4.0 runtime. It seems like something has changed in the runtime that overrides it as well as in Elite.

Does anyone have any experience with this or could possible provide some insight? I know beta 2 is right around the corner but i would love to get a jump on this issue asap.

Cheers!
 
You must log in or register to reply here.
Back
Top Bottom