f1rst

So he enables afterburner only if the 'afterburner gate' feature is disabled and it is very inconvenient. Especially in cases when I have gained speed of 1.6M and I need to jump into RIO's seat to take radar control and Iceman burns all gained speed by not using the afterburners even I command him to increase speed by 200 knots. Can you fix that please?

I believe the format of this timer have a wrong format. It looks like it's supposed to be something like this "28:06" but not "28:6".

He doesn't light the cans even if I'm flying at 1.4M and tell him to increase speed for 200 IAKTS.

So he keeps afterburner running when you jump into RIO seat for you?

I wonder whether you have changed your plans on it? It would be really useful feature for many users I believe. I also wonder if it's possible to configure Iceman to not to disable afterburner after I jumped into RIO cockpit? It's really important when you have spent a lot of time and fuel to reach 1.6M speed and Iceman just burn this speed when I jump on RIO seat since he doesn't use afterburner.

Now I understand how it works, thank you for the explanation. As I understand there is no magnetic course any more as it was before. I wonder why the Heatblur didn't mention about that in the F-14 guide.

In old videos and docs, there was 'MC' field that showed a magnetic course of locked target. Now we have 'RT' field and no 'MC' field any more. What that 'RT' means and how can I know a magnetic course of a tracked target since there is no corresponding field any more.

In addition I've noticed that it doesn't depend on FOV but it depends rather on camera position.

I'm sorry for the long reply. Didn't have a time( Here are two screenshots: the first one is my in-game view settings and the second one is the graphics settings. I'm sorry it's all in russian. I don't know how to change the language settings without reinstalling the client. My system configuration is: GeForece 2060RTX(with the latest driver), Intel Core i5-9600KF, 32Gb RAM. For reproducing the bug: set the same VOF value as on the screenshot and move the camera in the same position. Then when you are in a cruise flight you can see some ugly blinking of the main rotor blades. I don't use a Track IR or any other system that allows to control the in-game camera by head so I always watch the blinking. I think you could make it better. Thank you for the feedback and I'd be glad to provide you any additional information you need.

Hello. There is still the bug with rotor blades artifacts at the edge of the screen.

Could FCR be rotated to the left\right side, or it's fixed in front position?

And what about the case when you are performing defensive maneuver?

In addition: there is a FMC button that disables autopilot channels in key binding menu. So Apache does have autopilot stabilization system. And after pressing that button Apache behavior becomes the way I want it to be. Helicopter becomes agile and I can use force trim. But this is not a solution because I got FMC error after that and I don't know the way I can enable it again.

If the only thing it does is force trim it looks strange then. When I'm not doing trim while the flight parameters are changing (speed, torque, etc.) it's flying straight, but if only I used trim D\Down the helicopter starts rolling or something else. It looks like Mi-24 behavior when I disengaging its autopilot. I also can give as an example the Huey. It has the similar option "force trim" but it feels defenetly like a force trim. None of thoughts are left that Huey has something like stabilization system. But with Apache I have such a feeling.

Ok I agree the word "autopilot" doesn't fit this feature that we have after pressing R\Up trim. It enables some kind of stabilization that is good in cruise flying but it's not such good when I'm maneuvering in trees. In that case I prefer better to use D\Down trim mode so it allows me to feel the helicopter better, and it makes the life easier on low alt maneuvering.

R/Up engages the autopilot which I would like it to be turned off. I thought there is a trim mode in Apache like a flight director mode on Ka-50.

Hi there. I have just flown the Appache. It's great! But there is a thing that bothers me. When I use trim "D / down" mode(I may be wrong with its name since I've translated the name from russian) it doesn't hold the cyclic as force trim mode does. So I understand that such a behaviour should be with this mode of trimming, but it would be great if you would do such an option in menu that allows the virtual cyclic to stay in that position that I left it after trimming. It would be less realistic but it would be great option for those pilots who have a more or less simple joysticks.

Which patch? I'd like to buy this module on this sale, but I won't do it with such a problem(

Свет от осветительных приборов в кабине слишком яркий.

Летаю на Ка-50 ещё со времён её выхода. Джойстик Х-52. Режим триммирования ставил "с возвратом в центр" и вертолёт управлялся вполне предсказуемо: нажал кнопку триммера, выставил углы тангажа, крена, отпустил кнопку и вертолёт старается удержать заданные значения. На днях прикупил VKB Gladiator NXT, снял пружины, поставил режим триммирование "джойстик без пружин", дабы почувствовать себя настоящим вертолётчиком, и к моему удивлению Ка-50 стал себя вести не так как вёл себя до этого. Вместо того, что бы удерживать заданные углы тангажа, АП как будто "подбрасывает" нос вертолёта на 3-5 градусов по тангажу, после того как я отпускаю кнопку триммирования. На Ми-8 и Ми-24 всё супер. Такое неожиданное поведение только на Ка-50. Может кто нибудь объяснить мне причины такого поведения и как вообще летать на Ка-50 без пружин? Реплей с демо-полётом прилагается. ka-50_trim.trk

Hi guys. I'm considering to buy VKB nxt premium, so I wonder whether it is possible to bind its mini stick for view control and thus make camera rotation smoother than if the view control was bind on joystick's hat. I don't have a TrackIr device, so this is important to me.

А у Петровича будет функция типа "Возврат к сопровождению предыдущей цели"? На данный момент после того, как я нажал S, район цели приходится выискивать заново и это не очень удобно не имея TrackIr. На данный момент, как вариант можно закрывать прицельный комплекс клавишей О, но в таком случае приходится слышать постоянный, монотонный, звук оповещающий о оптимальных параметрах пуска ПТУР.

По нажатию на S он "отпускает" цель и при повторном заходе приходится искать её заново.

Если после того, как Петрович захватил цель выключить прибор наведения(клавиша 'О') звук оповещающий о оптимальных параметрах пуска не пропадает. Прошу прощения если было, вроде просмотрел несколько последних страниц не нашёл.