Jump to content

jeff64

Members
  • Posts

    21
  • Joined

  • Last visited

  1. Not certain of my answer, but I think the missile needs to be active before switching target (ie : tracking the target himself). So before switching target, the hud indication needs to be "TTI" (Time to Impact) and not "ACT" (time to active).
  2. I don't find trapping harder, but scoring is. With alerax lso or airboss, I managed an OK or (OK) about 90% of the time. On about 20 traps on the SC, I only managed to get 1 (OK), and all others were below average ---. I am reassuring myself watching the scores of the AI. Even them are generally getting a below average ! But this below average grading is maybe in relation with the EG sensitivity reported. I noticed too that I receive plenty of EG comments, even if I don't pull back the throttle TL or IW.
  3. hello just bought this shapeways extension, but I must admit : I don't know how or where install it. anyone have done it and can provide some explanations or pictures ? thank you
  4. Yes because in the real aircraft, it is an autocentered axis, like a rudder. As long as you are in the positive range, it will send the input. If you return the axis to the center, the input will stop.
  5. thanks thought this was HILOK poll.
  6. I can not find the official poll you are talking about. Where is it ?
  7. Hello all. Yesterday, on the "Hornet over PG" DCE campaign, I managed to infiltrate myself in enemy territory, avoided SA2 and Hawks, launched my JSOW's from 34.000 fts, just to watch them explode in the reliefs surrounding Lar Airbase. So, how do you do your mission planning to take those iranian rocks into account ? I think the solution is to set an angle for impact in the Jsow Mission page, but how to calculate the best angle to shoot at the max range but be able to clear all the mountains ? Thank you
  8. Unrealistic. A menu in the mission planning to set ALE47 programs and JDAM PP's is planned.
  9. Hello Don't know if it is a bug or normal comportment, but : when having selected from the store page a JDAM (J84 in the instance), the FLIR does not take the slave to the WPDSG function. If I switch from J84 to 82LG, it slaves to the waypoint. If I switch back to the J84, it goes back in "Boresight" function (looking straight forward the aircraft).
  10. the board is not for telling the pilot his aircraft's weight, but for confirming the data given to the deck crew for setting up the catapult is still correct. So you have to know your weight before seeing it on the board.
  11. it only means you have engaged the autopilot in barometric altitude (balt) mode. but if you are not under autopilot at this moment : it is a bug indeed;
  12. slaving the TGP to the WPT is only possible in the Open Beta since the last update.
  13. as far as I understand the logic, the elevation recorded for the target point is the waypoint passage elevation for your flying waypoint in the editor. Ex : gruond elevation is sea level (0 fts). You put a waypoint in the editor. Default altitude is 6.000ish feet, or 2.000 meters. In the hornet, the waypoint altitude is 2.000 meters, and your TGP will search an invisible point at 2.000 mrs in the air, above your target. Correction : In the hornet, select your waypoint. On the HSI, select Data, then UFC. Change Elev point to the Target Altitude. And your TGP will slave correctly.
×
×
  • Create New...