RealDCSpilot

I would wait:

@DmitriKozlowsky I'm not able to comprehend your reports of the new Gaz's behaviour on your end. The way you describe it actually sounds more like the old FM version. Please have a look at this: This video is made with probably the best current available input hardware for helicopters and shows that the new FM works pretty well compared to the previous state. You can clearly see that the weight is(!) hanging on the main rotor now and it's not(!) rolling like an airplane like before. I suspect something is heavily wrong on your end. I recommend resetting all your axis curves to linear and please check your hardware for faulty inputs. I also recommend disabling the trim option for pedals in special settings, better get used to hold the pedals in place because this could get confusing pretty quick with the abstraction of spring centered trimming logic.

Unfortunately i can. This problem is growing since the update with the F-15E. Right now it takes about 50 minutes on a busy server like 4YA, if i'm switching to another aircraft or to the F10 map the FPS drop heavily and never recover. I can also try to force it to happen earlier with switching to the latest SteamVR beta. After 25-30 minutes SteamVR stalls heavily and loses connection to the frame renderer, sometimes it's able to come back, sometimes it never recovers. Somehow DCS seems trigger something unusual after a certain amount of time. @BIGNEWY This might be connected to the Android VR headset PCVR connection. Most of us with Quest HMDs or Pico 4 use Virtual Desktop for the wireless connection. So if it's not reproducible with "any" HMD, please focus on a testing scenario with SteamVR (running OpenXR), Virtual Desktop and a standalone VR HMD.

I guess most of us are happy that those times are gone, together with the Quadcopter/UFO flight model. I would recommend doing a file check/repair and a revision of all your control options. Check the special settings for the new trim options and use RCTRL+Enter to check what your axis inputs are doing. I would also recommend resetting any curves on stick, throttle and pedals. Start with a clean linear setting and check if your devices do anything wonky on the axis display when sitting in the cockpit. Don't forget that you have to use the correct starting trim position on the cyclic now (bit left and aft)... On my end everything works as expected with the latest update, it's a good, believable helicopter module for DCS now. I hope they keep finetuning the flight model to give the real Gazelle the respect it deserves.

It's also clickable in the upper area of the canopy.

@jef32 Simply adapt to the situation, there is no reliable auto-hover functionality at the moment. Switch to hit-and-run tactics like in the Mi-24. Fly towards the target area in the co-pilot seat, pick a target with the Viviane or periscope, keep measuring the distance with the laser. If you reach 4300 meters fire the HOT3 and slowly break away while keeping the sight ground locked on target until the missile hits. Then dive and get out of the danger zone, rinse and repeat. The benefit is that you are no stationary target anymore, AAA and tanks with sniper missiles will have a much harder time to hit you.

Pretty good amount of fixes with the latest update!

Should be fixed now.

It's fixed now with the latest update. You have to use the individual FFB toggle setting in special options!

Oh, no. I have two rules: no Apple or Facebook hardware in my house! And the Vision Pro is definitely over-priced and overhyped. The only good thing about it, is the impulses it will give for other manufacturers. I'm basically waiting for the Index 2 as my next headset. Looking back, the Index was the only headset since 2016, that really brought new ideas and innovative solutions into the market when it was released.

Guy Godin from Virtual Desktop already announced that he will make VD for the Vision Pro. So it will support SteamVR and DCS sometime in the future.

@DmitriKozlowsky Have you already tried the usual trouble shooting procedures? DCS repair and cleanup? Renaming (deactivating) the Savegame folder? It's pretty obvious that others don't have the problems you have. So it must be something local on your end. Maybe a video would help understanding what is going on, with the axis input indicator display visible. The only current bugs i've seen at the moment are: - FFB trimming totally unusable - weird dynamic torque limiting on the collective - auto hover mode not working - CTDs when a HOT3 impacts on certain AA units Nevertheless, it's already useable, just keep moving, don't try to hover and disable the magnetic brake and never trim.

@Jekel Sorry for the late reply, didn't see it. I used Absima 135mm dampers: https://www.wirelessmadness.com/absima--1-8-off-road-aluminium-dampers-135mm-pack-of-2-suspensions-abs2330009 As far as i remember, i used 2000cps damper oil to make them smooth enough. However, they were only necessary because of the weight of the grip.

I only would upgrade to 64GB RAM. After that you will probably fine for a long time when all those features are fully implemented: Vulkan, DLSS, Multi-Threading.

Hehe yes. I'm currently using Mi-24 hit and run tactics. Fly towards the target, check range finder for 4300 meters, fire HOT3 and keeping the target in the sights until the torpedo crawls into it's target. Then break away...

Not on Win11 and a Intel CPU with P and E-cores. Learned it the hard way. Win11 seems to have the much better CPU scheduling ability.

That was all wrong in the first place. The whole FM wasn't even helicopter-like. Be patient, wait for the fix.

With FFB stick for trimming and DCS helicopters, don't use curves on stick axis. Keep them 100% linear. The current bug on the Gazelle is something different, it kinda multiplies the axis offset everytime.

That's good to hear. I also had the CTD occasionally on hitting Shilkas. It's hard to reproduce, but will happen eventually during a longer session.

Hi, i need to change the laser code with bindable buttons. Thanks!

I hope this is the right image and makes it more obvious: .50 vs 20mm

I remember this being fixed a while ago, but with the release of the new helicopter flight model, it came back.

Maybe the best IRL demonstration, but only one guy in the cockpit and of course - no weapons loadout. Can't tell how much fuel... it's hard to see. Use the mouse to look around, it's a 360° video. You can clearly see the moment where he tries to find the trim position for lift off (left and aft) and does force trim to center the cyclic to that position. Also very good to see is pedal input and cyclic movements needed to have stable behaviour while hovering and maneuvering near the ground.

@Bio Okay, VRAM allocation shows full usage all the time. It's already maxed out, but this is showing allocation only. There is an option in Afterburner to set VRAM usage per process to see the real values like in this older post of mine: It basically shows that the F10 map needed almost an extra of 1GB VRAM to be rendered. I guess what's happening on your end is Windows going into memory sharing mode and never gets out again. It means that ressources are constantly swapped from RAM into VRAM and back at a certain point, when the limit is reached. This stresses the system on CPU and all data paths (BUS) very much. To get a bit deeper you should try to test a simple empty mission, like those hot start instant missions to see if you can start at a point where VRAM isn't used to the max. And also use the Afterburner option for VRAM usage per process. @Whiskey11 Yeah, that's strange with your GPU... But first, you should take TacView out of the equation. Just to clarify, i don't have that problem at all.