Lixma 06

You need to get into a hover by yourself and trim it, make sure you're not in Director Mode (so you can't see = = on the HUD) and then engage auto-hover. It's not a miracle worker, though. If you're poorly trimmed and drifting when you engage hover the autopilot will try its best but you'll likely carry on drifting into a tree.

There's a load of twisty knobs in the Mi-8 that are just crying out for axis control (e.g. gunsight range, brightness). Also there are many 3-position switches (e.g. landing/nav lights) but no 'rotary' command option in the controls.

This video shows the moment the accident happened. I turned on the control helper to better see what's going on. Just after you gain forward speed it shows a large uncorrected cyclic input to the right which rolls you into the ground. I also tried taking control just after you switched off auto-hover but everything worked OK. So the problem is/was an unwanted cyclic input to the right. Looks like a control input issue - maybe a conflict?

I remember a bug from the BS-1 days where if you had a racing wheel/pedals attached then the trimmer wouldn't work properly. Check if your'e not unwittingly resetting the trim as you exit hover mode, maybe with a duplicated control.

When will the T-Rudder Pedals be back in stock?

He can shift to the right OK but the range of movement to the left is only an inch or so; not great when trying to find somewhere to land. The co-pilot does not have this restriction when leaning to the right. Is this limit on the pilot intentional or is there a file I could edit to fix it?

Mirrors can cause it too.

If it's any consolation (it isn't) I get the same thing in IL-2 while DCS is fine. :joystick:

Get a chiclet one - when you're flying it's a thousand times easier to hit a control, enter chat, or shitpost without accidentally hitting adjacent keys.

Beyond approximately 2km from the player the MiG-25 (both variants) turns completely white.

Yes - but the impact is practically nil. I don't know; it sounds like a scripting job although you might be able to do it using multiple 'Layers' via the GUI.

I've been unable to split an axis in two it but there is a rough and ready workaround if you're using TARGET. https://forums.eagle.ru/showpost.php?p=3347787&postcount=2

....

As Gandhi once famously said.... Absolutely.

Possibly related but I've noticed that taking off from and zooming around Senaki and Kutaisi is much heavier on the PC than most other areas - not sure why.

Few things that jump out - FXAA blurs the entire screen - sounds like that would make things worse. Also check you have textures set to 'High' in the options, and lastly many (perhaps all) cockpits are being tweaked for compatibility with the new deferred rendering.

https://forums.eagle.ru/showthread.php?t=61701 7 years

This looks like missing textures - are you using a MOD cockpit?

I'd kill for individual module volume faders. It's a pain in the backside when you jump into a new aircraft and have to reach for the volume knob, mentioning no names

Try raising the gear while you're sat on the runway - it's fun when you do it on purpose :music_whistling:

OFF FLAT: Structures Only FLAT: Structures & Trees DEFAULT: Structures Only DEFAULT: Structures & Trees Forests with shadows enabled are still very FPS hungry, but turning all shadows off makes things look a bit flat. A 'Structures Only' option (buildings, pylons, lamp posts etc) would be a good compromise.