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

Oculus DK2 tweak WOW nice

I just went into the folder:

C:\Users\yourusername\AppData\Local\Frontier Developments\Elite Dangerous\Options\Graphics

then opend the setting.xml and where:

<StereoscopicMode>3</StereoscopicMode> and changed 3 to 4 and it changed
in to WOW now it runs butter smmoth and everyt hink looks twice as sharp. dont know what that changes but for me it looks from blurry and not good readable to sharp and and no judder AWESOME

Hope it helps some guys of you to for me its just :eek:

EDIT: oh and a turnd of BLOOM and BLUR
 
Last edited:
Best Practices for using Oculus Rift (Beta 2.02)

Best Practices (Pre-flight) for using Oculus Rift in Elite. (Beta 2.02)

Make sure you have updated your Oculus Runtime to 4.2

Make sure you have flashed/updated the new firmware to your Oculus from the 4.2 runtime

In the Oculus configuration utility set the Rift Display mode to Extended. (Direct to Rift, isn’t fully supported for Elite.)

Recommended that you have the power supply that came with the Oculus plugged in, (I’ve experience bad head tracking without it.)

Make sure the OVR Server is Running, (Previously you had to disable this, not any longer.)

Make sure to temporally disable any virus scanning software, this can lead to performance issues.

Make sure to temporally disable any backup software. (Anything causing heavy disk action will cause your machine to slow down.)

Shut down any extra machine services/applications you might be running.

Once you start Elite, if the game doesn’t appear in the Oculus you will need to go into the graphic setting and switch the monitor to Secondary or Tertiary, depending on your setup.

Make sure to turn on 3D (experimental) for the Oculus in the graphic settings.

If you’re still having issues, try restarting your machine. (I’ve had issues with my Oculus not being recognized by my machine until after a restart.)

The easiest way to solve the Jittering / Judder issues is to lower the resolution, that the Oculus screen is rendering, (The new Oculus quality slider, seems to do this also, but without having to guess a resolution to jump to) if it cleans up the issue then you know, you need to lower some of your setting. Each machine is different; it’s up to you to find what’s comfortable.

A good place to test the highest dependency on frame rate is when inside or near a station.

Adjusting shadow quality will provide the biggest adjustment to frame rate. (Especially if switched to off)

Adjusting Anti-Aliasing to Off, or SMAA if you have extra bandwidth.

Adjusting Ambient Occlusion to off will provide some frame rate.

You might want to adjust the Bloom, depending on your preferences.

You might want to adjust the Blur, depending on your preferences.

The blurring that people are seeing, I believe is the time warping that has been implemented in Beta 2. This is to help with low frame rates, but if your fame rate is too low, it can get really bad.

The Oculus is very GPU intensive, I'm using a GTX 480, and while I'm almost jidder/jutter free, I have to run without shadows on.

I'm sure I've missed something, but I'm just trying to make life a little easier for those having issues, by providing a preflight-checklist.
 
First post here. Im playing with the Oculus Rift DK2, my pc its i72600k, r9 280x, 16 gb of ram, good motherboard and a 600w PSU.
In beta 1 i played with the rift, everything on minimum, it worked fine everywhere but in stations. in beta 2 its much, MUCH smoother and looks better, but.
My PC turns off while playing.
After a while of playing, my PC just turns off, no alarm, no anything, it just turns off the same way if you just unplugged it. CPU temps are fine, and GPU seems fine too, its not hot, but it doesnt make the same inmense noise it made on Beta 1, where after 5 minutes of play the fans on the GPU would be maxed and the GPU temps at 80 celsius.
On beta 2 fans dont get as fast, but the PC just crashes.
Ive run both prime95 stress test and furmark for like half an hour and the PC its fine and not overheating, yet somehow ED on the rift turns off the PC randomly.

It sounds like your power supply is starting to fail. It could of been stressed previously. Your kind on the edge with recommend power for the R9 280x. Try lowering the resolution inside the rift, this won't tax your system as much, and try playing in that type of setup and see if it works. if you then increase the resolution and it shuts down, its most likely the power supply not being able to provide enough power. Also it doesn't hurt to clean all the dust that get collected in these machines. Get some compressed air, and give it a good cleaning.
 
Last edited:
Thanks for the tips Raxxla :)

I don't have any problem running Medium settings in a Spaceport with my 780ti but as soon as I load up the Targeting Tutorial in the Asteroid belt I have to set everything to Low or Off to achieve 75fps and no Judder!

I'm hoping this is a bug or problem with the current build as I managed to use High or Med settings in all situations in Beta 1.06
 
The asteroid belt is pretty much a worst case scenario for any graphics card, particularly when you're level with the upper/lower limits because it has to draw every asteroid out to the edge.
 
But is Ice really that more GPU intensive than Rock?!

Never had this kind of performance issue in Beta 1 bounty hunting in an Asteroid Belt, and that was using Med settings preset with the DK2. Now I can't even use Low preset without judder and that's with a few canisters floating around, no NPC's and offline!! Doesn't seem right...
 
Thanks for the tips Raxxla :)

I don't have any problem running Medium settings in a Spaceport with my 780ti but as soon as I load up the Targeting Tutorial in the Asteroid belt I have to set everything to Low or Off to achieve 75fps and no Judder!

I'm hoping this is a bug or problem with the current build as I managed to use High or Med settings in all situations in Beta 1.06

Yeah Asteroid belts are really intensive, (forgot about those) you have so many draw calls to the GPU, that is something that will need to be optimized by the Dev team. It all depends on the complexity of the shaders, lighting and transparency of the FX's. but all that will come with time.
In development, First, it's about making things look good. Second, it's trying to make them look just as good with less demand on the hardware.
 
It sounds like your power supply is starting to fail. It could of been stressed previously. Your kind on the edge with recommend power for the R9 280x. Try lowering the resolution inside the rift, this won't tax your system as much, and try playing in that type of setup and see if it works. if you then increase the resolution and it shuts down, its most likely the power supply not being able to provide enough power. Also it doesn't hurt to clean all the dust that get collected in these machines. Get some compressed air, and give it a good cleaning.

I do think its the PSU, and bought a new one, that corsair one wich is 750w and gold rating. Its that for sure, but i find it interesting that it ONLY happens on this beta, as the older beta made the card whine but did not crash the PC, and the card got crazy hot, while it doesnt get that hot on the new beta, but crashes.
 
But is Ice really that more GPU intensive than Rock?!

Yes, because of the shaders for Ice being used, and all the particles that they are using for the fog FX's.I'd suggest lowering the FX settings and see if that doesn't help. It's isn't all about polygon count, it's about render calls, and how much there is on top of each other. And if it's transparent, and/or real time lit. It gets expensive.
 
just flew trough an ice asteriod belt shooting and looting, everything on high (smaa) exept blur and bloom off, in oculus/speakers mode butter smooth!! seems there is a big performance drop when using oculus/headphones mode!..
---i5, gtx970, win7---
 
After upgrading to Beta 2.0.x movement has been very smooth with the DK2. However I'm experiencing another issue with the release of 2.0.x. There's a constant repeating bright gamma flash on the whole scene. When this happens the ships graphics get a little stutter to the back.

It's most visible and occurring when docked inside a space station, but happens on all scenes. It's on all graphic settings (even low) so I think it's not related to graphics intensity.

I'm very curious if other people are experiencing this issue?

My machine specs: Intel Core i7 3770, 16 GB RAM, Geforce GTX 980, Oculus Rift DK2 and Thrustmaster Warthog HOTAS.
 
After upgrading to Beta 2.0.x movement has been very smooth with the DK2. However I'm experiencing another issue with the release of 2.0.x. There's a constant repeating bright gamma flash on the whole scene. When this happens the ships graphics get a little stutter to the back.

I've had that issue in Beta 1 a lot - the bright flashes are a brief loss of positional tracking, hence the stutter (at least that's what I interpreted it as). From what I've seen this far, it appears to be completely gone for me, but I didn't have the chance to play a lot yet.
 
well just did an hr.... really good experience, not many humans - 1 or 2 - I dunno if that is why it is working so much better but i cant complain.

1 thing tho. I tried tutorial 2 in the asteroid belt. even on low it was an uncomfortable experience in VR, ideally FD could do with lowering the detail of them in low detail to make it as accessible as possible.
 
After upgrading to Beta 2.0.x movement has been very smooth with the DK2. However I'm experiencing another issue with the release of 2.0.x. There's a constant repeating bright gamma flash on the whole scene. When this happens the ships graphics get a little stutter to the back.

It's most visible and occurring when docked inside a space station, but happens on all scenes. It's on all graphic settings (even low) so I think it's not related to graphics intensity.

I'm very curious if other people are experiencing this issue?

My machine specs: Intel Core i7 3770, 16 GB RAM, Geforce GTX 980, Oculus Rift DK2 and Thrustmaster Warthog HOTAS.

I've noticed, tracking seems to be an issue with this release. It might be related to the Runtime, because I've noticed it in other demos, and it was happening a lot with the Beta 2.0.X release. When the camera loses tracking it will make the screen color saturation go grey/indicating loss of tracking. I suggest you try moving/adjusting your camera, and make sure you're using the power adaptor that came with the Rift. Also look for any items around the house that may be causing IR interference, like a possible remote, game console/kinect, or movement detector for an alarm system. Using the camera on a smartphone can help find IR light.
 
- System map is massively bugged for me, but awesome nevertheless. I can see the planets out to my right, looking stunning in 3D, but have weird orange swirls everywhere

I think your point of view for the system map is inside the star. and what you're seeing is the star highlights.

I haven't figured out how to move in the system map - my joystick appears to move a cursor sideways over the various planets, and the info menu changes as I select them, but I can't zoom back to actually look at the whole map.

Anyone had any success with that?
 
Hey guys I should be getting my DK2 around the end of this week and didn't know if you guys have any tips on what I should do to make Elite look the best or run the smoothest?
 
Hi guys, just joined the forum. Can anybody tell me what the oculus graphic slider does?

I have a 4690k i5 at 3.9 ghz with a r9 290tri x and can play on medium in most situations. I get judder in the asteroid field with everything on low or off does this seem right with you guys?.

What does bloom do ? Like post a few pages back turning motion blur had the biggest effect.

One last question. What does SMAA do ? Will my 4 gig of VRAM help with that ?


Thanks in advance.
 
Back
Top Bottom