DETAILED DK2 SETUP

How do you change color scheme to predominant green

Check these out.

https://forums.frontier.co.uk/showthread.php?t=12785&page=2&p=1253173#post1253173

http://arkku.com/elite/hud_editor/

You need to edit one of the configuration files (XML), but it's easy enough & well worth doing. I use this one with the Rift

<MatrixRed> -1, 0.47, -0.19</MatrixRed>
<MatrixGreen>0.58, -0.02, -0.19</MatrixGreen>
<MatrixBlue>-1, 0.18, 1</MatrixBlue>

Which looks like this.

The reason for doing this is that there are twice as many green pixels as red or blue on the Rift's pentile display. It should cut down on screen door, and make text easier to read.
 
Last edited:
I've never done this before. Does this mean altering the coding? LOL I'm sure there's a video on a how to.

1-10 (ten being the hardest) how hard is thisfor sosomeone who isnt computer savvy?

Guys whats the secret to making my rift more smoother when I look around the cockpit? Its kinda jittery but not too bad.

Thanks
 
Last edited:
It's about a 3. ;) Not the code, just a configuration (text) file needs editing. You can use Notepad to do it.

The solution to a smoother Rift experience is to run at 75hz, and have a very fast PC. That's it. :)
 
Hey I can't lean in towards the dash anymore.

And the colors are dull now.

What the heck

[solved]

Move jack plug around until the blue light turns on. Sadly its a connection issue. Maybe a new mono plug will work? Hopefully its the plug and not the p/t.

I'm not the only one apparently who has had this same issue. Some claim replacing the jack worked perfect.
 
Last edited:
OK, at the outset I cannot stress this enough:

I have the inherent ability to repel technology, stemming from the fact that I am a 43 year old only recently introduced to computers and the like. That said, I have the Rift arriving Tuesday. Is the first post still sufficiently idiot - proof so as to enable me to get Elite up and running without me either stroking out or putting my Warthog through the monitor in frustration or am I better served chewing my wrists now already, thus bleeding out by Tuesday and thus not having the worry at all........
 
OK, at the outset I cannot stress this enough:

I have the inherent ability to repel technology, stemming from the fact that I am a 43 year old only recently introduced to computers and the like. That said, I have the Rift arriving Tuesday. Is the first post still sufficiently idiot - proof so as to enable me to get Elite up and running without me either stroking out or putting my Warthog through the monitor in frustration or am I better served chewing my wrists now already, thus bleeding out by Tuesday and thus not having the worry at all........

Truthfully?

You're going to struggle. It's a Dev Kit - for developers. In other words, people the exact opposite of what you describe above - those who know computers very well & don't mind a bit of fiddling to get things to work.

It's pretty simple to get up and running, but it's not "idiot proof". Things can, do, and will go wrong.

I would honestly suggest selling the DK2 on eBay and waiting for the consumer version, which should be out later this year.

Sorry if that's not what you want to hear, but it sounds like you're going to be frustrated with it.
 
Truthfully?

You're going to struggle. It's a Dev Kit - for developers. In other words, people the exact opposite of what you describe above - those who know computers very well & don't mind a bit of fiddling to get things to work.

It's pretty simple to get up and running, but it's not "idiot proof". Things can, do, and will go wrong.

I would honestly suggest selling the DK2 on eBay and waiting for the consumer version, which should be out later this year.

Sorry if that's not what you want to hear, but it sounds like you're going to be frustrated with it.

I persevered.........

MTiIo27.png


W.O.W..........what more can I say...........bit taken aback, really........Still trying to digest the enormity of it all. Started the slow process of improving visuals now that I got the rift set up but hell, it's worth it already as is. The feeling of actually 'being there' supersedes all else and literally takes over your senses. Phantom-limb syndrome kicks in almost immediately, having you reach for stuff and wondering why your arm is not moving. Conversely, resting your arm on your real HOTAS immediately transports you to your virtual body......I know I'm not explaining myself very well but it's a mindf#*k is what it is :D

In any event, my journey continues, albeit slowly...........One thing is however dead-cert: The journey till now has been worth the price of admission!

Onwards on fair solar winds I go.........
 
Hey all, just want to throw a thanks out to all the seasoned commanders who contributed to this thread it assisted me greatly in getting my DK2 up and running. I got my DK2 last week and it's like playing a whole new game. I cannot believe the true size of ships, ports and platforms. Dogfighting has taken on a whole new dimension. All my friends who have come and tried the DK2 are blown away too.
 
First want to thank everyone on the VR forum for being so helpful. It had definitely helped through some of the setup frustration.

One thing I'd like to add (and am hoping the OP will add to the original post), Is that measuring your IPD can be critical.
If you're in the average range, and within a couple mm of the 63.5 setting in the rift, then you should be fine. But if you're well below or above(like me) the norm, then the DK2 will likely be a disappointment.
No amount of GPU horsepower, supersampling, adaptive vsync, sweetfx, or whatever other magic is out there will be able to make up for the fact that your eyes aren't in the right position to merge and focus the images.
And just setting the IPD setting in the DK2 config DOES NOT HELP. That doesn't change the physical position of the lenses.

Thanks to atlas and djbordie (and others), but here's some of the key info I've received:
check your IPD here https://pd.warbyparker.com/

not the oculus utility, its usually way off.

if you are really past 70 ipd, then custom lens adjusters might be in order.

it definitely sounds like a lens/alignment/on ur face issue.
I've also found that a decent ruler and a mirror or a friend will give a pretty good measurement.

There is a solution: change the lens separation using this tool http://www.vr-gear.com/ or use a knife https://www.youtube.com/watch?v=H_OFWAOdYbo
For both method you will need to use a software that will change the image separation on screen in order to match the new lens separation https://drive.google.com/file/d/0B-XZ5ooeoqJdZ0FfWkl5YzNvdVk/view?pli=1 and these new OVR server files (runtime v5.0.1) https://mega.co.nz/#!S0ljzAbK!PRZjAhThrKRawzL9WT8Pn8hYvYb6XF4bElt4O0diS0s

Again, if your IPD is near average (63.5mm), then this is a non-issue. But if you're well above or below that, then it's critical to a useable rift experience.

...here's to hoping the CV1 has built in adjustments.
 
Last edited:
followed the guide, but struggling to get my DK2 working.

I have it set Extend Desktop, and set to portrait. My firmware version is 1.7 (0.6.0.0) (is this my issue??)
when ever i set the display to Secondary,and then 3D OR Speakers in ED Graphics options, my screens flicker and do nothing more.
Ive even tried setting the settings using Display Switcher app, but same thing.

My GPU is an AMD 290X (GV-R929OC-4GD) http://www.gigabyte.com/products/product-page.aspx?pid=4884#ov (with latest drive version, also tried latest Beta Version)
Windows 8.1, 8GB Ram, 512GB SSD. Intel I5-4690K
I did have more than 1 display, which i have disabled, so main display on DVI, and tried DK2 on both 2nd DVI & HDMI.
DK2 works fine in the Demo + RetroArcade etc..
Just struggling with Elite.

Anyone got any tips? or experience with same GPU as me?
 
Last edited:
I think it is your driver version. Downgrade to 0.5.0.1 drivers, that's what I'm running without issue.
I've read somewhere that the new drivers break Elite in OR, just can't find the link atm.
 
Last edited:
Thanks for the reply,

I think it is your driver version. Downgrade to 0.5.0.1 drivers, that's what I'm running without issue.
I've read somewhere that the new drivers break Elite in OR, just can't find the link atm.

Yup, will give that a shot tonight. I just found the post about problems with 0.6. fingers crossed !
 
OK downgraded to 0.5.0.1 and its working now, except i had to change it to landscapped flipped in windows display properties, but in my catalyst control it says portrait so i guess my windows is confussed.

Im getting lots of orange trace spots, so time to read some more :)
 
After reading all the issues with SweetFX Elite setup and Windows 8.1 I decided not to bother. Seems to be total confusion about getting it to work on win 8.1.
 
So I shoudl use 5.01 rift drivers. but what version of the nvidia driver is good to use?

So I should use 5.01 rift drivers. but what version of the nvidia driver is good to use?
I see some old posts on the subject but I was wondering if there is any recent info?
 
Last edited:
I borrowed a DK2 a few days ago and I've been playing Eurotrucks and the like very happily but I can't get ED to work. It works fine on non-vr settings.
I have the 1.3 sdk (Oculus home says 1.3.1), latest nvidia drivers. I set ED to HMD with speakers. I feel like I'm missing something.
When I run ED, it opens a window on my monitor, goes through the logos but crashes before it gets to the main menu. The dk2 is powered up when ED starts and I see the logos and head tracking works. It starts to load shaders then crashes to desktop.
I've been tinkering for ages and I'm frustrated now so I'm turning to you lovely people for help. I don't see anyone else with this problem.
 
Last edited:
Unstuck as 0.5/0.6 no longer compatible with ED

Are you saying the latest ED doesn't work with the 0.5 and 0.6 runtimes? What version do you recommend using? I'm running 0.6 with the latest NVIDIA drivers and the DK2 in extended mode. Unfortunately, ED (+Horizons) is not detecting the headset and I can't see the HMD option under 3D, only "Off", "Side by Side", and "Anaglyph". Any help appreciated!
 
Are you saying the latest ED doesn't work with the 0.5 and 0.6 runtimes? What version do you recommend using? I'm running 0.6 with the latest NVIDIA drivers and the DK2 in extended mode. Unfortunately, ED (+Horizons) is not detecting the headset and I can't see the HMD option under 3D, only "Off", "Side by Side", and "Anaglyph". Any help appreciated!

Pretty much, if your wanting to run ED with the DK2 your going to need to use the latest Oculus runtime (meaning direct mode only)
 
Back
Top Bottom