Vladinsky

You don't seem to be disputing anything I've actually claimed. I agree with all of your points. It does appear that way, it's exciting to see DCS helicopters get the attention they deserve.

While instant trim is listed as FFB Friendly, it is functionally the same as Default trim in the Mi-8, UH-1H, Ka-50 and Mi-24. ED changing the name of it seems to have caused a great deal of the confusion.

That would help. The FLIR is an easy way to tell roughly how well aligned your HDU is. After boresighting, the FLIR video in NVS NORM should line up closely with the view directly in front of you on the ramp.

I can kind of replicate this but I have to deliberately boresight the HDU completely wrong. Is your FLIR aligned correctly when this is happening?

While gyroscopic precessing is something to be considered, it's not the dominant force at play, the phase lag is highly dependent on many other factors. Which you'll have to ask someone with a lot more knowledge than me about unfortunately. It's rarely exactly 90 degrees though. You can see on the in game Hind model that the swashplate acts on the blade roughly 35 degrees ahead due to the pitch horn being offset forward in the rotation. On the Ka50 it looks to be around 50-60 degrees. The Apache appears to be around 40-45 degrees. TL;DR Rotors are magic.

I have this too with a 5900X, it is not present on the previous release build 2.5.6.59625.1 though.

I saw a significant VR performance increase going from my 4690K(4.2GHz) to a 10600K, not so much in terms of maximum framerate but reduced stuttering and increased lows. Unfortunately no frametime numbers due to the OTT overlay not working. However, the YAAB: Yet Another Arma Benchmark saw an 85% performance increase. This is with a 2080Super, 3600MHz CL16 and after overclocking, 4.9GHz all core/4.8GHz cache.

Make sure the physical center of the axis is actually seen as the center in the axis tuning in game, it might be as simple as recalibrating or adding a bit of a deadzone.

I've had no issues fitting DT770 and HD25 headphones over the headband, though the HD25s are a bit easier to put on and take off.

On your DCS account profile page, bottom left under ED miles/personal info. Oops, missed the second half. If you just want to read it they're all posted here https://forums.eagle.ru/showthread.php?t=151478

As a module in DCS without multicrew I imagine you would just cram everything you need onto your joystick/collective regardless of where it's actually located in the cockpit. My transducer requires about 2lbs for maximum input, which is about the same force required to actuate the trim switch on the Lynx cyclic I use as a joystick, I think it would work ok. As for why they did it, literally no idea. But if I were to speculate, perhaps the collective was too crowded with switches already, or perhaps it made more sense to disconnect the copilot stick rather than installing a separate sensor control grip due to space restrictions. You can get them but they'll be very costly if you're buying them new from lets say, OTTO. You can however find good deals on ebay from time to time, search for otto pushbutton or otto switch. Typically the sellers are located in north america so you might get hit with import tax too.

Going from a 4 way switch to a force transducer for sensor control is the joystick equivalent of going from a monitor to VR, that's how big the difference is. It's specially noticeable in the Ka50, zero curves or saturation required. As for having it on the cyclic, that's only an issue if there's very little resistance/no force trim system. The OH-58D takes it a step further and gives you the option to disengage the copilot cyclic from the control system. The copilot cyclic is also the only one with a transducer. Its location instead holds the force trim release switch on the pilot side.

If the reason for not adding an absolute axis option is realism then buttons and the unrealistic TDC slew should be removed.

It's trying to fly through the point in space defined by the waypoint, since the lowest you can place waypoints is 98 feet AGL that puts the waypoint elevation at ~177 feet, and as such it will fly through the point 98 feet above the target, exactly as it has been instructed. If you edit the waypoint to correspond to the ground, 79 feet in this case, it hits dead on.

No problem, you can disable exported displays in the cockpit by commenting out "render_purpose.GENERAL," on line 81 in "Scripts\Aircrafts\_Common\Cockpit\ViewportHandling.lua". This will fail integrity check though. You should be able to find the name of the viewport for any module by going to the module folder\Cockpit\device name\init file. In some like the F18 they're in DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts. You can even add it if it's not natively exportable. For example if I wanted to export the mirage RWR I would go to "DCS World\Mods\aircraft\M-2000C\Cockpit\RWR\RWR_init.lua. Check if the dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") line is present, if it isn't, add it. Then add the line try_find_assigned_viewport("Viewport_Name")It doesn't seem to matter where exactly you put them. I'm not sure how to add new ones for FC3 aircraft but they should output the F15 radar display to the LEFT_MFCD and the flanker/mig 29 HDD to the RIGHT_MFCD by default.