ok had done all of that apart from the Aero, so i just tried that and it had no effect still have left eye on right eye with an overlap in the middle.
How to get the DK2 working
- Thread starter Michael Brookes
- Start date
ok had done all of that apart from the Aero, so i just tried that and it had no effect still have left eye on right eye with an overlap in the middle.
Have you tried restarting the drivers and service using the Oculus tool ? Sometimes it plays up a bit. Is the Dk2 res set to 1920x1080 @ 75hz ?
yes i have tried restarting the services and restarts of computer.
its odd as it works fine for everything else except Elite and windows desktop.
Hmm, tricky one. Have you tried a different USB port. Have you updated to the latest firmware and SDK ?
Thanks for the help stevesideas you have been most helpfull, i think it may be time for a format not been that long but a few hardware changes so might be a good idea and then try again me thinks.
I've never found a format to be the answer for hardware issues. You might want to try taking all other peripherals out to see if that helps first..Good luck
Can anyone tell me what the point of the lower resolutions selections when in oculus mode are for? The game runs super juddery for me (as expected), but I noticed that when I put it in one of the weird vertical resolution it was super smooth, only the image wasn't right.
Is it possible to play E
in the DK2 on any resolution other than 1920X1080?
Thanks
Is it possible to play E
in the DK2 on any resolution other than 1920X1080?Thanks
Can anyone tell me what the point of the lower resolutions selections when in oculus mode are for? The game runs super juddery for me (as expected), but I noticed that when I put it in one of the weird vertical resolution it was super smooth, only the image wasn't right.
Is it possible to play E
Thanks
Lowering the resolution has probably increased your fps. Juddering occurs when your fps drop lower than 75 on the dk2.
Performance with 3.0 and 0.4.3
Hey guys, been trying to test out beta 3.0 with my Rift. I've been noticing some loss of performance to well below 75 FPS now. I'm not sure if it's 3.0 or the fact that I'm on runtime 0.4.3 - can anyone else comment if they are seeing any performance issues in 3.0 using either Oculus runtime?
Hey guys, been trying to test out beta 3.0 with my Rift. I've been noticing some loss of performance to well below 75 FPS now. I'm not sure if it's 3.0 or the fact that I'm on runtime 0.4.3 - can anyone else comment if they are seeing any performance issues in 3.0 using either Oculus runtime?
I'm in the same boat. Beta 2 was great, DK2 worked awesome, now... I can't get more than 10fps with the rift after tinkering for 30 minutes to get it to render to the correct screen (the rift).
So I'm unable to play with the rift until this is fixed. Oculus Runtime 0.4.3, DK2, Set as secondary display. Extend mode. Legacy Support checked.
Framerate as such seems ok. Latest nvidia driver for my GTX 770, SDK 0.4.3 running on extended mode. Flying currently an Eagle and when I move my head, even turning around there is some sort of threshold, once I cross it there is a short break/stutter and a after that a change in saturation (less) and brightness (more bright). Had that in beta 2 but less and only when I was moving down towards the joystick. Any idea?
Okay I tried it with Direct Mode and it worked fine... for 2 minutes... and only in solo mode because I was unable to connect to the server. However, reactivity and latency seemed really good, with still 75 fps (I've a GTX760, an overclocked i7 and 16 GB RAM). But after 2 minutes of testing, it started lagging and framerate dropped to 30 - 40 fps, with several 1 to 2 seconds freezes and Oculus position unsyncs.
I hope these bugs will be fixed quickly, but it seems promising.
I hope these bugs will be fixed quickly, but it seems promising.
I'm not sure if I've done something different but the rift is working better for me since beta 3. Still judders but is much more playable now - hovering around the 75fps mark most of the time but dipping fairly regularly. I updated to the latest Nvidia drivers and updated the SDK. Initially I thought it was because I had set the DK2 to 1920x1080 (originally I set it up at 2560x1440 to test oversampling) but I put it back to the higher res and it still worked much better than Beta 2. For me there seem to have been some really good optimizations for DK2.
I tried with direct mode but only get as far as the initial loading screen. After that I can hear the menu clicking but can't see anything on the DK2 screen.
I tried with direct mode but only get as far as the initial loading screen. After that I can hear the menu clicking but can't see anything on the DK2 screen.
How do you get direct mode working? Didn't for me.
I had no issues going from 0.4.2 to 0.4.3 in beta 2. The performance drop was in moving to beta 3.
Direct mode ran for me with the 0.4.3 runtime only. No-go with 0.4.2. The only available resolution settings belonged to my monitor, though, which locked me to 60Hz at 1080p and left me on the corner of judder street and blur boulevard. Extended mode with Rift as secondary display worked well though. Direct mode needs to be patched to force the Rift's native resolution and refresh rate, with the options grayed out in game.
I just got my DK2 yesterday, and I'm at a loss as to how to make it go with E: D --or anything else beyond the stuff in the SDK, but lets stick with what is important, yes? Anyway, what follows is a bit disjointed, because I'm at a loss to create a rational troubleshooting plan, even.
[First, the relevant seeming bits of my setup: EVGA 780, 1xAsus PB287 4k Primary (Adam), 1xPB278 1440p (Betsy) secondary and now the DK2 (Chuck) which should be the tertiary. Adam uses the Displayport on the VGA, Betsy uses one of the DVI-ports, and Chuck has now taken the HDMI. Yes. I gave them names. I was getting lost, I can't imagine how anyone else was feeling]
I set the DK2 in extended mode.
I start E: D
I set E: D to full screen
I set it to the tertiary display
I set it to OR-Headphone mode
I hit apply.
And then things get strange. It starts putting the image feed for the OR into a window on the desktop... sometimes Adam, sometimes Besty, but never Charley (at least as far as I can tell... looking at the thing with it off my head there are moments it seems to be sending display to it, but there is never anything but my background there when I put the thing on...
Like I said... I think I'm missing something painfully obvious, but I don't know what it is...
thanks for any help.
EDIT: Got it! What was happening was that between hitting apply to go to the OR and actually getting the damn thing on around my glasses, it was switching back to the previous display mode.
I do have one remaining problem, though which is this: how do I get it to center properly? It keeps wanting me to twist my head at a 15-20 (?) degree angle to look at menu's et. al. dead on. The Galaxy Map is nearly unusable thereby, for example.
Still. Wow. just... wow.
[First, the relevant seeming bits of my setup: EVGA 780, 1xAsus PB287 4k Primary (Adam), 1xPB278 1440p (Betsy) secondary and now the DK2 (Chuck) which should be the tertiary. Adam uses the Displayport on the VGA, Betsy uses one of the DVI-ports, and Chuck has now taken the HDMI. Yes. I gave them names. I was getting lost, I can't imagine how anyone else was feeling]
I set the DK2 in extended mode.
I start E: D
I set E: D to full screen
I set it to the tertiary display
I set it to OR-Headphone mode
I hit apply.
And then things get strange. It starts putting the image feed for the OR into a window on the desktop... sometimes Adam, sometimes Besty, but never Charley (at least as far as I can tell... looking at the thing with it off my head there are moments it seems to be sending display to it, but there is never anything but my background there when I put the thing on...
Like I said... I think I'm missing something painfully obvious, but I don't know what it is...
thanks for any help.
EDIT: Got it! What was happening was that between hitting apply to go to the OR and actually getting the damn thing on around my glasses, it was switching back to the previous display mode.
I do have one remaining problem, though which is this: how do I get it to center properly? It keeps wanting me to twist my head at a 15-20 (?) degree angle to look at menu's et. al. dead on. The Galaxy Map is nearly unusable thereby, for example.
Still. Wow. just... wow.
Last edited: