Frusheen

CV1 refresh rate will be 90Hz. Given that the dcs fps display counts total frames rendered it means we will need to render 180fps or 90fps for each eye versus 75fps (150 total on dcs counter) for DK2. It's a jump from 75 to 90 not 75 to 180. Given the increase in resolution with CV1 it will still require a beast of a system for dcs.

Rick, - Install the 0.7 oculus runtime and setup your IPD via the configuration utility. - launch DCS and select auto detect oculus rift then exit. - Right click on DCS icon go to properties and set it to launch in vista compatibility mode. - launch DCS and put on your rift. - press right ctrl and pause keys to show FPS. Adjust graphics options to get 150FPS and enjoy. Colour saturation is currently off. The bug was reported and a fix is coming. EDIT: fixed! :-)

Guys this debate about resolution has been hashed out before. You need to look at pixels per degree not overall pixels. Just counting pixels on a 2d monitor and comparing to the rift is pointless as it does not account for lenses and FOV.

What's your thoughts in VRsli. I have an OC 780 and could pick up a second for a lot less than a single 980ti. VRsli won't come into its own until cv1 with its dual screens. Is there anyway of knowing if dual 780s would work. If they don't then I might wait for the next gen graphics cards before upgrading.

http://forums.eagle.ru/showthread.php?t=148218&page=2&highlight=Oculus+rift+view+washed

I press Right Ctrl and Pause to measure frame rate and it shows in the rift. How are you measuring it? If it's via a 3rd party app it might be showing the FPS of the image on your monitor and giving 75 instead of 150.

Vicx, You are correct my issues were frame rate related. I was seeing over 75fps in the headset using the frame rate counter. That is what confused me. I actually needed 150fps. The counter is counting frames per eye so I need 75x2 for smooth judder free tracking.

Anything below 150 causes judder for me. It seems the FPS counter is counting each frame rendered which is 2x the rift refresh rate. (Right Ctrl - Pause)

My judder problems are caused by frame rate. I have confirmed it after some testing. Using the FPS counter display anything below 150 is a juddery mess. Given the rifts refresh rate is 75 it seems that the counter is counting frames rendered per eye (75x2). It does not appear asynchronous time warp is implemented in the beta yet. Worst performance is at airports. Once I get into the sticks and back to 150 all is good. Hopefully further optimisation and time warp implementation will help things. I'm using a gtx780 OC edition but will need a new graphics card. That frame rate requirement needs to jump to 180 in a few months!

Yes but only when within view of the positional camera. If I move outside its range I have silky smooth orientation tracking but of course no positional. Could you test this on your system and see if the results are the same? Seems to happen irrespective of frame rate for me but need to do more testing in that regard. On other news the colour saturation issue has been fixed and is coming in a future patch.

Great news! The colour saturation issue has been solved and will be released in a future patch.

I have very bad judder still as well but only when the dk2 is within view of the camera. If I move out of range I have silky smooth head tracking (but then of course no positional tracking). Not sure if it is related to frame rate. I'll lower graphics settings to check (gtx 780). Could others with high frame rates and judder test this camera theory and let me know what they find please.

Let's hope they decide to fix it sooner rather than later. I haven't 'flown' any simulator without the rift in a long time. I have xplane 10 and purchased all 3rd party helicopters. There's no sign of rift support coming to that platform - I haven't loaded it up since the early days of dk1! Just can't get any enjoyment from using a monitor with a flight sim now.

Id personally prefer to wait for a fix from the devs. It's a beta so I don't want to start editing files plus with the amount of attempts it takes to get into a mission it's hardly worth the hassle.

I don't think we'll see any oculus update for a while. I'll be pleasently surprised if they do fix it soon. It's ominous that the dk2 crash thread hasn't been marked as reported yet.

I have 356.04. Still has the washed out look and crashes constantly on mission load screen. I manged two flights in about 30 attempts.

I tried the nvidia gameworks vr drivers yesterday. They made no difference.

EGT is not modelled correctly since day1. It has probably been the single biggest complaint since the Huey was released.

High power setting at low speed and a strong tail or side wind.

Shadows are the least of our worries in the rift with 1.5!

You don't have to load 0.7 if you don't want too. We are running a BETA compiled against runtime .7. If you want to participate constructively in the beta process and provide feedback to the Devs so the software can progress then you need to be on .7. If you think you can get better results with .6 and just want to fly then go ahead. If you do use .6 then don't report bugs about 1.5 as it only confuses the issue.

Have you ticked auto detect rift in options

Do you find when you get into a mission it still crashes on exit or does it exit normally? I posted the crash log for a sucessful mission that crashed on exit in the bug thread. It may be useful for others to do the same as it will give them something to compare too and may help narrow down the issue.

Joebloggs you asked about .7 runtime in the crash reporting thread. Here is where it says it http://forums.eagle.ru/showthread.php?p=2487386#post2487386