Jump to content

ZaltysZ

Members
  • Posts

    942
  • Joined

  • Last visited

Everything posted by ZaltysZ

  1. If you press F key while in hover, autopilot will try to maintain altitude which has been designed by F key. It will do that by varying collective by itself in interval of 20%. If you move the collective to much, those 20% might be not enough and aircraft will begin climbing or descending. Basically you have to coarsely set collective to maintain hover and autopilot will continue doing that by fine adjustements of collective.
  2. It is on the collective and you can't click with mouse on it. Map to joystick or use keyboard.
  3. It is so cool. Than you very much. It is very distinctive style; reminds me times (198x in Soviet Union), when there were automates, which accepted coins and allowed to buy New Years themed posters. I hope you will make a tradition of such skins. Happy New Year. :yay:
  4. Data link is only reliable on servers in which no more than 4 Ka-50 fly for one side; and this is true only if correct ID is chosen. Visual identification must be used if you see contact over horizon, but not in ABRIS, and current locations of all friendlies are unknown.
  5. Press CTRL+ENTER, move the stick so, that its symbol would be at point where lines crosses, press T. Now you should be able to take off and hover. "T" doesn't center the trim, it trims instead.
  6. That message of EKRAN is a bit confusing. It will show every time icing is detected, no matter in what position deicing switches are. It should be taken as "Warning: icing detected" and not as "Warning: don't forget to turn deicing". Power required for hover depends on mass and altitude. Hovering isn't hard on engines as climbing or accelerating. You can check that by looking at RPM and EGT.
  7. Deicing system of Ka-50 is based on hot air flow, so I think it is more effective when engines are working at higher power settings and producing hotter gases. Avoiding prolonged descents and long hovers is good idea in cold weather.
  8. Press BACKSPACE (Drop target) before selecting point and erasing it.
  9. Missile goes where your laser points to. If you move target designator while missile is in flight, it will change direction. So, yes, you need to wait for hit before changing target.
  10. Aiming circle is lying, unless fire control computer knows the range to target. In other words, you need to measure range with laser to hit accurately with rockets. There are 2 ways to do that: 1) Auto track mode on: lock target with Shkval. 2) Manual mode: move aircraft in such position that aiming circle is over target, press Auto Lock button to measure range; See English manual 2-101, switch #11.
  11. I think it is related to FFB thing; maybe there is problem with mapping virtual to physical center. Seek attention from ED. Meanwhile, don't use reset button, retrim to neutral manually. After all, Ka-50 doesn't have such button in reality.
  12. Doesn't it return to neutral position only or doesn't react to trimmer reset at all? It might be joystick problem. My X52 frequently shifts center of Y axis and I have to reset it by unplugging cable.
  13. Press Ctrl+Enter, check if cyclic symbol is in neutral position (where lines cross) after trimmer reset. Also check if AP channels are on, and Flight Director is off.
  14. Yes. Reset timmer, slow down to zero speed and turn hover mode on. There is 2 modes of altitude hold (switch near AP channel buttons): barometric and radar. Radar mode is good for terrain following, but bad for hovering over a place, which isn't parallel to horizon. Ka-50 will be unsteady, if you try to hover over something like steep slope of mountain with radar altitude mode on, because little drift will induce change in altitude (from ground) and Ka-50 will try to compensate and sometimes to overcompensate...
  15. If you are using any video/audio codec packs, try running the game with them uninstalled.
  16. When you start in the air (like in instant action), your Ka-50 is trimmed for forward flight. Retrim for hover before turning hover mode on.
  17. See here: http://forums.eagle.ru/showpost.php?p=585199&postcount=6
  18. I think the problem is not rendering, but increase in calculations, particularly AI pathfinding, sensors and ballistics.
  19. It is good you haven't tried to play BS on something like Asus EEE PC, because I hardly dare to imagine what "equal hell of stutters" you would requested, if you have tried. :D
  20. Just don't forget that it is bad for brains when changing pictures take whole field of view. :smartass: Keep a good distance from screen.
  21. As far as I know, game uses OpenGL for menu, editor and other GUI in 2D world.
  22. Have you updated game list inside TIR software?
  23. I think it is problem with MFD of X52 Pro: MFD service hangs and DCS crashes. There is workaround: http://forums.eagle.ru/showpost.php?p=584373&postcount=20 Please, don't delete, just rename the file or move it somewhere else, in case you needed it in future.
  24. If you activated DCS before CPU upgrade, when you will have to reactivate it.
×
×
  • Create New...