Jump to content

f1rst

Members
  • Posts

    348
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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?
  2. 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".
  3. He doesn't light the cans even if I'm flying at 1.4M and tell him to increase speed for 200 IAKTS.
  4. So he keeps afterburner running when you jump into RIO seat for you?
  5. 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.
  6. 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.
  7. 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.
  8. In addition I've noticed that it doesn't depend on FOV but it depends rather on camera position.
  9. 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.
  10. Hello. There is still the bug with rotor blades artifacts at the edge of the screen.
  11. Could FCR be rotated to the left\right side, or it's fixed in front position?
  12. And what about the case when you are performing defensive maneuver?
  13. 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.
  14. 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.
×
×
  • Create New...