Rocky49

It's great that they updated the terrain and airports BUT it is totally unplayable now for VR Worst hit to my frame rates since I was running a GTX 295!!! I think it is a combination of the new Oculus 1.10 runtime and the Nvidia drivers? The ASW function of Oculus is totally screwed up in DCS.

I don't believe you can

skate kinda noob question but does it matter which cntrl I use ie my keyboard has a left and right cntrl

I don't seem to be able to turn ASW functions on or off using Cntrl plus 1,2,3, and 4 number pad. Num lock is on, however using the various commands like Cntrl + numpad 1 has no effect on framerates running oculus 1.10.0

I too have always had low frame rates with this mission

totally agree that if you are prone to motion sickness you must take the time to gradually increase exposure, however, one must also remember that some people never get over their quezzyness

Oculus responded with basically, too bad but Windows 7 will not be supported for this

thanks for the info, because of the ease in the way my system updated to 1.8, I was not sure it had in fact updated, but it did, without any issues :)

where do you look to find your current version of oculus runtime?

so, no update this Friday?

this will be a huge step forward!!:thumbup:

careful with the oculus toolkit...there were some serious issues reported with version 1.7 don't know if problem was addressed by oculus

Excellent find!!! Fixed this issue for me as well.

If the developer of a product tells you that you should not use certain products on their devise, why do you think you should experiment with using them?

yup it seems impossible to only use small inputs, the slightest touch of rudder pedal results in a full deflection to the direction of rudder input. really unusable at this point

having same issue, Warthog joystick, usually it happens in P-51, canopy slowly rolls open, flaps go down one notch.

Well there is a lot to love with the cv1 if you have the horsepower to use it. I suspect your 2500 chip is just not cutting it. I f you look at my specs I have pretty new gear, only 16 months old. VR is tasking for state of the art equipment so if your gear is a few generations old, you can have issues. I can run DCS at 90 FPS with some tweaking but still can read most of the gauges with just a glance, If I need to really have a close look, I just use zoom function. BTW I usually wear glasses to use my monitor, but not necessary with my rift

I do have it enabled

mounted my Crosswinds on that plate. Had to drill my own holes though

Neil For me it was a trip back in time putting on the Rift. Got all the same feel to flying that a got as a new PPL, PLUS, don't have to wear glasses! Who knew it was a time machine :megalol:

Me too.

I re-installed my sensor and started a A10 mission. Initial position is still too close to the HUD and again to the right of center. Also slightly too high. Tried to save the position but it did not save, again using RALT and 0. Am I the only person experiencing this? Other that the A10 and F86 all the other modules Huey, Gazelle, Mi8, L39, Black Shark, M2000, P51, and Dora seem to be Okay, or at least workable.

I will re-run the setup in my rift to see if that helps. I will also check the mapping on my other modules ie F86, Huey, etc to see if it is different. Thanks for the replies :thumbup:

HWY Ed my sensor is directly in front of me about 1 meter away. Have not had any instances of sensor problems. I flew for about 2.5 hrs today A10 still opens with my face right up against the HUD. I back it of to back of the seat with right shift and ctrl and the / in number keypad. I have not had any success in saving to this position by using right alt and 0 number pad. Any idea why it does not save?

Sounds like you need to make sure you are in full screen. If the view in your monitor is not "stretched" to fill the Monitor screen you need to press left alt and enter. Now your mouse will work.