Jump to content

buur

Members
  • Posts

    625
  • Joined

  • Last visited

Everything posted by buur

  1. Also remember that DCS checks for inputs only each frame. So it is connected to your actual FPS and you get a kind of minimal input length. If you have 10 FPS your input would be a 0.1 milliseconds press and the trim moves for 0.1 milliseconds. If you have 100 FPS your input would be a 0.01 milliseconds press and your trim moves for 0.01 seconds and is much more sensitive.
  2. look at your first picture. It clearly shows a AV8B without pylons. And this is the picture where the weight stands. So you need a deep look into the document where you get this picture to get an idea what they mentioned with empty weight. With/without pilot? With/without non consumable fuels like hydraulic oils. With/without re-fueling probe and so on ... Why you can't remove the pylons in DCS? Because RAZBAM never saw a picture of an actual Harrier without pylons. So they do not add this feature.
  3. they can be removed IRL, that is the reason that weight and drag index are mentioned in the manuals. Also you must add the weight of the pilot. (~180lb)
  4. In the manual the weight is without pylons, in the game the Harriers has always mounted pylons.
  5. If I had it right in my mind this is possible with MOOSE. Check the documentation for that.
  6. Not able to set the elevation of a waypoint higher than 25.000 in UFC. If try to set over 25k feet UFC ignores input.
  7. where is the second plane when says "ready pre contact"? The answer suggest that he is in the wrong zone. As I remember right, the second plane had to be behind the right wing of the tanker.
  8. Had similar problems but after cleaning my computer they are gone. There were a lot of dust in the coolers. Maybe it helps.
  9. To push this topic here a picture. You see JTAC request IP ADDER but it is not on the MFD.
  10. hm, had the same problem. Should I clean my joystick with alcohol or use the alcohol by myself?
  11. Unfortunately this bug is not solved.
  12. When the AI JTAC plans a attack he chose randomly initial points and very often the initial points are to far away from the target. A good solution to avoid this problem is that we can choose the initial points for the JTAC. So, please give us the possibility to advice initial points to JTACs.
  13. It is a very big improvement that the target advised by JTAC is now marked on the kneeboard map with a red triangle. But if an other JTAC send a new target you have now two or more red triangles on the map. It would be very helpful if only the actual target is on the map or the triangles marked with a number so that we can differ them.
  14. Hi, I have seen that ED has added the Target Point send by JTAC to the kneeboard. Great addition. Now we need also the Initial Points (IPs) which you can set in ME on the Kneeboard. This will help the pilot to understand his Mission given by JTAC.
      • 2
      • Like
  15. Check your Kneeboard. The nine line is nowadays added automatically to the kneeboard.
  16. um es mal so zu sagen: Der JTAC ist nicht gerade der stabilste Teil der Simulation. Kann gut sein das die einfach so verschwinden. Was du machen kannst um die armen JTACs nicht zu verwirren: Überlaste die Jungs nicht mit zu viel Funk. Die sind dann manchmal etwas verwirrt und haben keinen Bock mehr. Gehe die Prozeduren komplett durch. Nicht irgendwo in der Mitte aussteigen. Auch das verwirrt die. Gib jedem JTAC ne eigene Funkfrequenz. Wenn die sich gleichzeitig hören sind die auch verwirrt. Deine Einstellungen sehen richtig aus, daran sollte es eigentlich auch nicht liegen.
  17. First, check your speed. If you got to fast in a dive you loose control. Above Mach 0.9 the plane get unstable. Second, do not pull to much gs. Above 6 Gs you can get problems.
  18. Check Admiral189 mods, both are there.
  19. Also have in mind that a high FPS rate gives you more sensitivity with your controls and make it much easier.
  20. I talked about this thread:
  21. This is a known issue, search the forum for this topic and you will find a thread about it. There wasn't a solution other than a new install of the game as I remember.
  22. @OzCougar check your line 92. You have a capital C where a small one is needed. Always check your log for errors.
×
×
  • Create New...