FragBum

Cool welcome to VR :thumbup: <edit> Oh and the Gazelle rocks in VR. :D

Maybe but there is another thread here and the guy had issues with VR using onboard graphics for monitor and a graphics card for VR. I cant test as I don't have on board graphics support with my CPU.

I'm pretty sure that the monitor needs to be also plugged into the same graphics card! You could try a converter cable for you desk monitor.

You might need to dial some of the settings down until your frame rates improve constant 45FPS is fine. Your CPU might also bottle neck performance, also DCS doesn't multithread very well currently I have 5930 i& 6 core @ 4.7Ghz 64GB RAM and 1080Ti. PD+1.2 I currently run MSAA @ 4 now that's about the only difference to these settings and I get a constant 45FPS with occasional drop frame. DCS Settings here Also the different maps effect CPU/GPU utilisation. Maps in order of performance CPU/GPU utilisation. NTTR Lowest/Fastest Caucasus Normandy PG Highest/Slowest

To be honest Damcopter I haven't seen your case (cases) for the so flawed FM, other then a vague "it's bad". Care to elaborate? :D

Hi Damcopter, I'm keen to know as I am building up a VR Sim Pit for Helo 's so far it seems to work for Mi-8 and Huey as well as Ka-50 and Gazelle. Of course the Gazelle is light kinda like an R44 and a bit and with more lift?. :D For me maybe some saturation but no Expo for X and Y (Cyclic) as the Gazelle has a very centric cyclic action perhaps some curvature and only for the Gazelle.

@Damcopter. I have found that the input controls has a significant affect on how the Gazelle "Feels" in DCS. I especially find the cyclic input to be critical for the Gazelle. Question is does the amount of cyclic in this basic maneuver seem about right for the Gazelle? Keen to know if it's close, or not.

I find for DCS my Rift does not need to be like an Alien face hugging creature attached to my face. :D

Out of left field try the NTTR map I find it the cleanest clearest and sharpest map in Rift VR, the PG map looks out of focus and blurry compared to the NTTR map. The NTTR map is also the best performance wise of all the maps by a large margin. The other thing is getting the HMD set up correctly height and angle of the HMD are vital for best resolution adjust so that the whole image is in focus and you have minimal colour fringing top and bottom, go over the set up a few times to get overall image quality as best as possible. This also changes as the face interface piece ages and no longer holds the HMD at the same distance as it used to, they are fairly cheap to replace on the Rift. Also clean the lenses regularly it's amazing just how much gunk accumulates on the lenses from when your eyes blink. Also don't fixate on the screen door effect that can cause problems with some practice you wont even notice it.

How about cattle with AI rather then just cows, that way we could round them up and heard them using the Gazelle of maybe the Mi-8 for the dinosaurs. :D :music_whistling:

Just a thought "these days" does that imply you used to be okay hovering? If so and your not using a Force Feedback joystick check that for what ever reason that the FFB option under Gazelle settings is not ticked. This option can become enabled "randomly" during a DCS update and has caused many people to have problems flying the Gazelle. As Gizzy indicates small movements of cyclic is all that is required indeed I use only a few mm movement* for most of my flying it really is more like "using the force" compared to other choppers. *Most of the time in flight and hover the animation of the cyclic in the cockpit hardly moves and I really do throw the Gazelle around.

Just an observation with the latest updates to 2.5 I get about 8~8.5GB VRAM usage. Usage in earlier 2.5.x versions was up around 10~10.5GB however I don't notice any difference. As far as I can tell stutters occur when the GPU hits 100% usage every time and repeatable, so I back settings off until I have an average 65~75% GPU usage (also 12~14% CPU usage) this GPU usage varies depending on map and activity however by lowering settings for me with a 1080Ti and Rift that's usually dropping the PD to 1.1~1.2 and MSAA at 2 or 4 depending on which map I fly. I find that with PD at 1.2 and MSAA @ 4 is about the sweet spot for NTTR and if I were to fly in other maps then I will get the occasional stutter which can usually be minimised by either dropping PD to 1.1 or MASS to 2 although I don't really bother as it's only an occasional stutter say on PG or Normandy maps and very occasional in Caucasus. Before the implementation of deferred shading I could happily get 90FPS in Rift on NTTR with my 980Ti however that is now 45FPS but solid with the 1080Ti. This indicates that it's more the GPU power of the 1080Ti being taxed. YMMV. :thumbup:

Check out the BU0836 Here Pots and encoders also here but what you have seems okay. Or even this one here

Do you mean stuff like this? But it is a lots of fun, short vidio here. :D I normally fly with AP system off. Nice write up by the way. :thumbup:

Auto Hover? Works fine although it's easier to manually hover more stable than in Auto Hover mode.

Indeed, just need to develop some skills,.. :D:thumbup:

Do your self a favor and get pedals at the very least, also collective and cyclic and VR if you don't already have. :D

If I had to choose only one. It would be the Gazelle yep thats the one. The Gazelle :thumbup:

Hardest anything that does not have a rotor on top, although I have managed to land the YAK. :thumbup: Out of the heli 's the KA 50 presents some difficulty and only because of the lack of near field vision from the cock pit in the KA 50 otherwise all heli 's are easy to land. :D

IIRC in the days before VR, the numeric keypad should allow you to look around.

But then it wouldn't be a UH-1H it would be a UH-1N or Bell 212, right? :thumbup: More helicopters is always better. Right? :D

Sure that is on of my regular servers very experienced at crashing on that one. :thumbup::D Do you have TeamSpeak?

I found that in my case the logitech 3D pro controller actually had a built in dead zone, which makes sense for a joystick with a mechanical center detent. However since changing to a Leo Bodnar USB interface I have no dead spot just smooth cyclic input. The choice of saturation is I guess a personal one as well as in the case of the Gazelle the use of curvature which only makes sense given that the Gazelle cyclic is totally centric I.E. no shift for change in CG. It's just with a joystick you have such a short throw reducing saturation can help. I used to fly the Gazelle with a joystick no saturation it's doable but a tad uncomfortable on the wrist. More on Gazelle and joystick controller here. Interestingly with a home built cyclic and collective and applying some curves the feel as in sensitivity of the cyclic is about that of an R44. More on that build here and soon I'll add the anti torque pedals I'm working on. :thumbup: As for the collective it seems fairly analogue to me I.E. not a stepped response perhaps it's the resolution of the A to D converter in your controller or something? As I said curvature does not make sense for the Huey and Mi8 and KA50 as their CG shifts the balance point and you need to react accordingly by shifting the position of the cyclic depending on load out fuel and the manoeuvre your doing. However saturation may help for an individual, after all no helicopter in DCS actually has a joystick for flight control right? :joystick:

Just updated to 2.5.3.21444 and it seems great so far in Rift VrR and NTTR. :thumbup:

Just an observation I tried the PG map last night and it's performance still seems very sluggish with Rift VR, also the detail and visible range and just clarity seem somewhat poorer than NTTR (which BTW is still the best map VR performance wise!) Okay with PG loaded basic free flight mission I had 11GB RAM used with a further 21GB assigned to pagefile with some 300MB actually committed and 52GB RAM available. (Yes I do have 64GB of RAM)