RaceRoom Racing Oculus DK2 and Simracing

I'm lucky I don't get any kind of motion sickness, but I do get scared sick playing Alien Isolation , does that count ?

Is the effect of "tunnel vision" is disturbing ? with no peripheral view

Interesting article about AC and oculus rift:

" The biggest complaint I have about playing Assetto Corsa on the Oculus Rift DK2 is nothing whatsoever to do with the software itself, but the limitation of the DK2′s panel. In racing, you’re constantly hunting the horizon for information on upcoming corners or distant cars. Even though Oculus’ 2nd generation development kit headset is vastly improved in terms of resolution compared to its predecessor, it just doesn’t pack enough pixels to make gazing into the distance anything other than a jumble of dots. That’s not to say Assetto Corsa is unplayable on the Rift, far from it. It merely serves as a reminder that we’ll have to wait until the first consumer edition of the Rift to alleviate the issue."

http://www.roadtovr.com/assetto-corsa-oculus-rift-dk2-virtual-reality-preview/

First I was going to to order one unit but I will wait for the final release.

@noorbeast I would have to disagree with the statement that sharp vision is more important for racing than [combat] flight. Usually people use very subtle braking and turning markers such as cracks on the road, but you can alternatively use bigger markers that are found in plentiful amounts on any track and are clearly visible in the Rift. I have no issue with this since I have started car simming with VR so I never used subtle markers in the first place, so I have no issue with re-learning all of that. With flight sims however that's not possible because there can't be "bigger markers" for landmarks in the distance which are already the only markers, and small airplanes with barely distinguishable silouettes let alone tiny militray markings on them, because there's simply nothing else in the sky. I'm in no big disadvantage markers-wise when driving in the Rift (I'm in a huge advantage FOV and headtracking-wise), but flight sims are pretty much impossible to play competitively. Still fun to just aimlessly fly around though, especially if you're going to quit the game without landing.

It has to be noted that by comparison to HD triples (or even single HD panel), even CV1 with its UHD screen will still be heavily lacking of picture clarity and while you may be able to see some of the small markers, subtle markers will still be invisible until they get right up your nose, and the same thing with landmarks and enemy airplanes. If you want hard numbers, typical PPD (angular resolution - direct measurement of picture clarity) of an HD monitor is 50-80PPD depending on how large is the monitor and how far is it set, whereas DK2 is slightly above 15PPD, and CV1 is supposedly slightly under 25PPD assuming it's going to use that 21:9 UHD Samsung panel.

I have not tried a combat sim but for Prepared the dk2 works perfectly. It is by far superior to any kind of monitor setup however that is only my opinion.

@noorbeast Thanks, that's a very good points. However, tweaks are just tweaks ultimately, and you're supposed to use your real vision, not special tricks.
>Do be realistic, if you are using a Rift, joystick and in-cockpit view you will never be competitive in something like Arcade mode for games like War Thunder
Arcade mode is specifically designed with mouse control and casual player in mind, and it takes it to such a far extent that using cockpit view and a joystick makes you handicapped against mouse users with nose camera view. With DCS or IL-2 that's not the case because the game is only designed to work with joystick and support for other input methods is rudimentary.

Hi guys, I had some time this morning and modified the Oculus SDK 0.4.3 to compensate for the DK2 headtracking via shared memory (well, windows file mapping). Going to do further testing in the coming weeks, but it fixes Noorbeast's jerkiness when the camera is fixed on the platform. There's hope yet! Here's how I did it:
1. I send the position of my pots via serial from my microcontroller to my Motion Simulator program via serial-over-usb.
2. I added an extra thread in my program which receives these values, transforms them into roll/pitch and finally into a quaternion. This value is stored in shared memory.
3. The Oculus SDK retrieves this quaternion and uses it to calculate the pose sent to the game.

Was pretty simple, will probably wait until the Oculus SDK settles down and then I'll share these findings with the SimTools devs.

@John Hien Nguyen That's excellent! Although it would be better if there would be some convention about it, so best to share as soon as possible. If more sim software developers will pick it up, Oculus may eventually officially support that.

Wow thats awesome !! If you need me to do any testing for you I can do no matter what state it is I would like to be some kind of help

Wish I had the knowledge to work stuff like this out, I just know how to follow instructions and use a bit of initiative and good with DIY

Wow, that's exactly what I thinked to solve the problem by software, but It can work perfectly only in a very "high definition" motion sim, because every delay will be a problem to the right position calculation. Do you have some video that's show this thing?

@nclabs Since he reads data from pots and immediately sends it back to PC, I beleive the latency wouldn't depend much on rig type, more on how the messaging pipeline is organized.

I was referring to the real simulator delay, I mean the frame where we sit on. But even with some slow and swingy simulators it can be a good solution, because even if we can't solve the issue, with a little bit of tuning we should be able to reduce it a lot. So, GO @John Hien Nguyen !

@nclabs Yes I see what you're saying, but pots are reading immediately relevant data since they are directly connected to the rig. The only latency there could be if the assembly is very loose and jerks around terribly, but it's not like even latency, more like tracking mismatch. Other than that, it's a latency imposed by pipeline processing design.

Probe They produced one like me dizzy