My OR Experience

Hey Commanders!

So this game has now cost me a small fortune. Got the game a few weeks back, then decided I needed a controller, which made the ship handling much better. Now I've gone and bought the OR DK2, which I got set up just in time for the Gamma 1.01 breakage... Thanks Ben! :p

That little glitch aside, I am loving the highly immersive feel whilst flying around the galaxy. Being able to properly track the direction you want to head in is so cool. Whether in combat, overshooting your destination or just adding a bit of flare to your docking style (aka crash landing), the effect is awesome! I'm not regretting spending ~£400 on all this in any way :D

I do have some observations that I'd like to raise, but these are just details for potential future improvement...

I found the set up instructions for the OR a little confusing at first, but it is actually very simple and really didn't take too long considering what a clever bit of kit this is. I was initially a little disappointed with the resolution on the device, as I took the 1920x1080 HD selling point as meaning more than it is. Not having played with any other VR kit, I didn't expect to be seeing the individual screen LEDs as highly magnified as they are. This limits the graphics quality available to ED and that is a shame, but I accept that as a current technical limitation and don't have a major issue about it. It's not spoiling the game for me, so I just look forward to things improving over time as they always do. This is the future of gaming!

As far as in-game settings go, I tried many of the suggestions such as over-sampling to improve the readability of the text but didn't find it any better. In the end I've simply settled for the low quality preset which gives a smooth frame rate and, as long as I look directly ahead at the text I want to read, rather than using eye movement alone to scan across, the text is easily readable.

Finding out about the F12 reset view option was a big help. For some reason the camera position sometimes recalibrates in-game and I end up looking out from my virtual chest or having an out of body experience, floating high up above where I should be. Not sure if this is the game or the OR drivers but, once I'm sitting comfortably, if I use F12 to set my position then I would expect it to remain that way without auto-magically choosing to mess with my set up, and not only that but then get it wrong.

Some additional work would be very welcome on improving some of the flat views, such as the maps and game options. Wrapping them around the field of vision in some way might work. I don't really want to keep straining myself to stretch across so far just to read what's down the far left hand side.

The side HUD panels can also be a little awkward as they keep closing whilst I'm trying to read the info and navigate the menus. It seems like they need to be a little less sensitive to head movements once they are active. This is more of a problem whilst flying due to the acceleration head-bobbing effect which, as others have posted, does not work well as part of a VR experience for me and should be made configurable.

Finally, I get regular random pulses of brightness across the screen. Not flashes like the Hyperspace lightning, but just a slight momentary increase in the overall brightness level. This could be from the game or maybe a fault on my OR, I'm not really sure. Does anyone else get this? It's not something I've seen in any of the discussions I've read so far.
[Edit: This problem was quickly solved by Mark D in post #2, and was due to hyperthreading being enabled on my i7]


In conclusion very happy and thoroughly enjoying the ED universe through my OR eyes :D
 
Last edited:
.... Finally, I get regular random pulses of brightness across the screen. Not flashes like the Hyperspace lightning, but just a slight momentary increase in the overall brightness level. This could be from the game or maybe a fault on my OR, I'm not really sure. Does anyone else get this? It's not something I've seen in any of the discussions I've read so far ....

Welcome, nice post. On the final point - not sure about 'regular random' ;). I've seen similar but may not be the same. During testing I got some low frame rates and appeared to get random pulses linked to loss of head tracking. However you mentioned turning your graphics down to low so hopefully not this. The other time was when I turned Hyperthreading on my quad core CPU which gave me regular pulses every second or two (so much so I've turned it straight back off).

Are you using Hyperthreading, how many cores does windows task manager show (my quad core showed 8)?

Sorry if I missed it - what graphics card so you have?
 
Thanks for the response Mark D and good point on my choice of words. What I meant was 'frequent, random' :)

Okay, what you describe about the hyper-threading does sound similar, and I have i7 950 showing 8 cores in Task Manager. I'll try switching off hyper-threading later and see if that corrects the issue. GFX card is a GTX 770 which seems to be plenty powerful enough to run the OR.
 
I did try downsampling (or oversampling as I called it :rolleyes:) but didn't find it any better and figured it was just wasting CPU/GPU muscle. Although, I have only been able to play with the OR since G101 and that is not exactly a fair test.

With G102 arriving any minute I'm hoping that, with the new right eye Ben Parry has just whittled out of a fresh chunk of code for me, things can only get better! I'll play around with the graphics settings again and see what I can squeeze out of my rig.
 
Last edited:
Welcome!

you won't notice the pixels after a bit, today was the first time since I got the rift that I have played on a screen, and I found it disappointing by comparison even though it was a much higher resolution.
 
HaHa, my eyes and brain cell adjusted very quickly and even with the G101 hiccup I still wouldn't go back to using the monitor. The initial disappointment I mentioned in my OP was completely blown away by an explosion of pure wonder & delight :D
 
Thanks for the response Mark D and good point on my choice of words. What I meant was 'frequent, random' :)

Okay, what you describe about the hyper-threading does sound similar, and I have i7 950 showing 8 cores in Task Manager. I'll try switching off hyper-threading later and see if that corrects the issue. GFX card is a GTX 770 which seems to be plenty powerful enough to run the OR.

You are welcome mate. Probably a red herring but worth a quick try to rule it out, only took 2 mins to turn on/off in BIOS. The other thing is it could have been a combination of my setup at the time, CPU = I7 920, ED Beta 2.x, Windows 7 and Hyper threading. I don't remember anyone mentioning a similar problem so I never brought it up on the forums. For my rig it was very clear, turned on HT = pulsing flash in ED, turned off and went away.

Our graphics cards were also similar :) For Beta 2.x I had the GTX 770 (great value card). I used MSI afterburner which displayed the FPS within the Rift and could only get a steady 75 fps in a hanger / eagle with LOW graphics and turning down the Oculus slider quality to mid. IMHO turning down the Oculus slider made the text very bad so I upgraded to a GTX 970. I know others with the GTX 770 have High graphics and are fine most of the time e.g. in space but choppy in stations etc under Beta 2.x I've been busy playing and not retested recently with later ED releases which may be more efficient.

Good luck, would be interested to hear how you get on.

Update : the above was all in extended mode
 
Last edited:
Hyperthreading.. this is one thing I have not tried for the vision latency changes. Glad I read this thread, I'll try that to see if it resolves the issue. Thanks!
 
Hyperthreading.. this is one thing I have not tried for the vision latency changes. Glad I read this thread, I'll try that to see if it resolves the issue. Thanks!

Saviornt I meant to ask earlier - what are 'vision latency changes' geniunley not a term I've heard before?
 
Last edited:
Hyperthreading was the issue. Awesome quick fix and rep well deserved. Cheers Mark D :D

I'm now running settings at high, except for turning off AA. Getting a little bit of motion jitter as I move my head but it's nothing major and looks so nice now that G102 has fixed the right eye brightness levels. I might have a play with downsampling later but for now I need to get back to ED:cool:
 
Last edited:
Saviornt I meant to ask earlier - what are 'vision latency changes' geniunley not a term I've heard before?

If you close the OVR server in task manager (you need to close the OVR services in order, I'll have to double check as I am at work atm).. but this is what causes the screen to lose saturation for a split second (positional tracking is lost). Then, if you go to the OVR folder, you can manually start the service(s). This allows for a window that shows you the verbose logs.

When the vision latency changes, it errors in this order:

The logs fail in this order:

Ransac failed in xxxxxx ns
Ransac succeeded in xxxxxx ns
Sequence id = 9 with xx votes
cameraToHMDoffset: -xxxxxx
skipped x frames
Tracking reset due to vision latency change <was 0.xx, now: 0.xx>

The last step seems to reverse itself each time the tracker resets from high to low latencies, example: <was 0.41, now: 0.98> to <was 0.98, now: 0.44>
 
Back
Top Bottom