How to get the DK2 working
- Thread starter Michael Brookes
- Start date
I have updated to BETA 3 and 0.4.3 version of Oculus Runtime, and now I'm experiencing strange graphical glitches playing on my DK2: instead of black color I see reddish tint, plus vertical screen tearings here and there. Overall performance is good, however this graphical issues looks ugly... Prior to 0.4.3 everything was OK.
I'm running GTX 970 SLI, i7-950, 12 GB, Windows 7 64-bit. Latest (vanilla) nVidia drivers. Other games and demos I have tried runs and looks OK, so this is Elite: Dangerous specific issues. Also, I have tried capturing screenshots, and everything is OK on them, so this is something to be with Oculus Runtime, I believe... Any suggestions?
Thanks!
UPDATE: I just have traced problem to SLI. With disabled SLI everything look normal. Also, my single Asus STRIX 970 GTX is able to run maxed out Elite with 70 FPS on Rift (SSAA is 1.5 in settings.xml). While SLI setup showing roughly 75 FPS with 95% load on BOTH GPUs... And those graphical glitches
UPDATE2: This was my faulty SLI connector... Fiddled with it a bit, and everything now works fine. However, my 2x970 SLI setup cannot run 4K Elite on Rift with 75 FPS...
Max what I'm getting is ~30 FPS when <SSAA>2</SSAA> is specified in settings.xml... Any other way to make text more readable on Rift? Thanks!
I'm running GTX 970 SLI, i7-950, 12 GB, Windows 7 64-bit. Latest (vanilla) nVidia drivers. Other games and demos I have tried runs and looks OK, so this is Elite: Dangerous specific issues. Also, I have tried capturing screenshots, and everything is OK on them, so this is something to be with Oculus Runtime, I believe... Any suggestions?
Thanks!
UPDATE: I just have traced problem to SLI. With disabled SLI everything look normal. Also, my single Asus STRIX 970 GTX is able to run maxed out Elite with 70 FPS on Rift (SSAA is 1.5 in settings.xml). While SLI setup showing roughly 75 FPS with 95% load on BOTH GPUs... And those graphical glitches
UPDATE2: This was my faulty SLI connector... Fiddled with it a bit, and everything now works fine. However, my 2x970 SLI setup cannot run 4K Elite on Rift with 75 FPS...
Max what I'm getting is ~30 FPS when <SSAA>2</SSAA> is specified in settings.xml... Any other way to make text more readable on Rift? Thanks!
Last edited:
Guys;
Can you fix the black smear on DK2 ?
This was reported by all DK2 users I know. It was present yesterday on 1.02, I didn't have the chance to test 1.03 yet, but I suppose it's still there.
Or is it a Rift SDK bug ? I supposed it's up to the game not to render pure black when using the rift.
Can you fix the black smear on DK2 ?
This was reported by all DK2 users I know. It was present yesterday on 1.02, I didn't have the chance to test 1.03 yet, but I suppose it's still there.
Or is it a Rift SDK bug ? I supposed it's up to the game not to render pure black when using the rift.
I think this is limitation of DK2 screen. This is what called refresh rate, I suppose. I see this black smears in ALL demos and games... And I don't think it can be fixed. In CV1 maybe
Yes, black smearing is fixed in DK2 just by increasing the brightness.
DK2 demos/games usually avoid rendering pure blacks to avoid this artifacts.
But at least, a brightness setting would do it (the gamma setting is not a solution as black remains black).
Well I'm testing gamma 1.04 now, and I'm not sure anymore
there's definitely some black smearing issue, but I remember it was way worse with pure blacks so maybe it's all "normal", ie as good as the rift display can do ?
- - - - - Additional Content Posted / Auto Merge - - - - -
also, can't wait for alt-tab to work
(* restarting the game *)
Yes I had this one my Q6600 machine but never yet on my Xeon. Just in case, I followed other peoples posts and plugged in the adapter that came with the Rift.
Adapter? I'm using both the power adapter and the dvi to hdmi one.
Anyway, I've tried to switch usb ports, I've tried to move the tracking camera back, nothing helps. I'm about to give up..
It's strange though that the problem went away but then came back with gamma 1.0..
And again; Elite Dangerous is the only software I've ever experienced loss of pos tracking where it never came back unless I restart (once I restart Elite Dangerous it can last for 0-3 minutes before it goes away again).
If only the cockpit didn't grey out when the pos tracking went away I could somewhat live with it..
Last edited:
I dont understand the dictate for the Runtime 4.4 now since Gamma 2. Before G2 i had a stabil ED under Runtime 4.2 (3+4 has never worked), but now i get
Runtime-Error after pressing Play, so what i can do now?
Runtime-Error after pressing Play, so what i can do now?
I just installed the full version of the game.
I have gotten the output to work with side by side on the oculus DK2.
The headtracking doesn't seems to work though. I am running the 0.4.3 Runtime.
Tuscany villa and other demos can use the head tracking.
I have gotten the output to work with side by side on the oculus DK2.
The headtracking doesn't seems to work though. I am running the 0.4.3 Runtime.
Tuscany villa and other demos can use the head tracking.
19 page thread so far and some of the early "how to get it working" advice is now obsolete. Can we have a single sticky with a comprehensive guide to getting the launch version working on DK2? This may well already be in this thread but it is impossible to tell what is relevant to the launch version and current DK2 firmware/runtime and what isnt...
I downloaded 0.4.4 runtime drivers. Now the tracker lights up, but still no head tracking.
Tried reinstalling but no luck.
Have you updated to latest firmware on DK2 ? Are you in extended mode ? Do you have the camera powered by the cable that came with DK2 ?
worked in training not ive
i played the training on sat with no issue, i wasn't expecting to do anything when i started it up this morning, the light on the camera not lighting up, so head tracking isn't working. i just spent 10 min before i had to goto work, i'll post more tonight.
i played the training on sat with no issue, i wasn't expecting to do anything when i started it up this morning, the light on the camera not lighting up, so head tracking isn't working. i just spent 10 min before i had to goto work, i'll post more tonight.
Ok, so after some playing around and updating to 0.4.4 runtime, I got the DK2 to work in ED.
But as I am quite new to DK2, I am still experiencing some issues:
1. I find when I move my head it gets very juddery and seems like the image starts separating, which becomes a bit nauseating after a while.
2. I find that the text in the UI is barely readable for me, it seems like "too pixelly" and also like the pixels are sort of separated (like the text is a bit red above and a bit blue below), I dunno if what I am saying makes sense, but in order for me to be able to read any text I have to lean in quite a bit. I suppose this might be some calibration issue or so, though the demo app for the DK2 seems to work well (and only minor "pixel separation"). Also I have no idea if that might have anything to do with me being a bit short-sighted, and not wearing my glasses when using the DK2 (just too uncomfortable with glasses). I find that the "sweet spot" of things being in focus is really quite narrow, but I do get it focussed generally.
Sorry if those questions sound very noob-ish, but I am a newbie, and would really appreciate any input on how to solve those issues.
thanks!
But as I am quite new to DK2, I am still experiencing some issues:
1. I find when I move my head it gets very juddery and seems like the image starts separating, which becomes a bit nauseating after a while.
2. I find that the text in the UI is barely readable for me, it seems like "too pixelly" and also like the pixels are sort of separated (like the text is a bit red above and a bit blue below), I dunno if what I am saying makes sense, but in order for me to be able to read any text I have to lean in quite a bit. I suppose this might be some calibration issue or so, though the demo app for the DK2 seems to work well (and only minor "pixel separation"). Also I have no idea if that might have anything to do with me being a bit short-sighted, and not wearing my glasses when using the DK2 (just too uncomfortable with glasses). I find that the "sweet spot" of things being in focus is really quite narrow, but I do get it focussed generally.
Sorry if those questions sound very noob-ish, but I am a newbie, and would really appreciate any input on how to solve those issues.
thanks!
Have you calibrated your IPD? are you running in extended mode and locked at 75Hz Not 60Hz for the judder. Might be better with the glasses and a change of eye cups.
As I don't have to wear glasses (at the moment) I'm no expert on that. Also the sweat spot is very critical on headset positioning.
As I don't have to wear glasses (at the moment) I'm no expert on that. Also the sweat spot is very critical on headset positioning.
I am in extended, the firmware version on my DK2 is 2.12 and the camera is tracking perfectly on both tuscany, HL2 and the HD rollercoaster..
Try restarting the drivers using the occulus tool. Make sure the service is running. Graphics options running in occulus mode (not side by side). Try another USB port ?
Restart computer ?
Can't think of anything else..sorry. Hope you get it sorted.
- - - - - Additional Content Posted / Auto Merge - - - - -
Do those demos work in direct and extended ?
Restart computer ?
Can't think of anything else..sorry. Hope you get it sorted.
- - - - - Additional Content Posted / Auto Merge - - - - -
Do those demos work in direct and extended ?