Jump to content

Tholozor

Members
  • Posts

    2086
  • Joined

  • Last visited

Everything posted by Tholozor

  1. The codes on the AI page would be the codes to interrogate other aircraft. The codes on the XP page would be the codes to respond to interrogations. None of this is really modeled in depth yet, but in a more simulated environment, you could interrogate the airspace in front of you to locate a specific aircraft on a specific code. Let's say you're looking for an aircraft squawking 2286. You can set the interrogator to challenge that Mode 3 code and look for the response. Right now, as far as IFF is concerned, Mode 4 is the only thing that matters. Mode 3 can be set for LotATC/SRS, but it doesn't affect anything in-game.
  2. The interrogator can challenge in all modes; the codes for each mode can be set independently between the interrogator and transponder (i.e. you can challenge specific codes with the interrogator without having to change your transponder). You can see IFF reply information on the AZ/EL page with what mode it's replying to (AFAIK the only ones implemented at the moment are Mode 4 and PPLI responses).
  3. IFF on the UFC, then ON/OFF to enable the CIT. Subsequent presses of the IFF button will toggle between the airborne interrogator (AI) and transponder (XP) menus. On the XP menu, colonizing the Mode 3 option will allow you to input your 4-digit squawk code.
  4. This has been discussed before. The harpoon has the correct warhead, it's the ships that have too much health/armor/lack of modular damage models.
  5. The Hornet's waypoints go from 0-59. Also, waypoint 59 now automatically populates with the mission's Bullseye position, so 58 may be a better choice.
  6. It's a little closer to ~8.2nm (~50,000 ft).
  7. The HMD symbology will always be rendered at the center of the screen, so you may have to adjust your default head position closer to the HUD. Adjust your view to the position you want, and it can be saved with RAlt + Num0.
  8. Are you talking about the relative position of the display to your eye in VR, or just the position of the display on the screen?
  9. The caution and advisory line will always be on the left DDI when all screens are on, this cannot be altered. The left DDI is not intended to be used for critical-information pages such as the SA page specifically because of that. In A/A, it is intended to use the left DDI for the AZ/EL display, and the radar format on the right DDI (the sensor control switch logic supports this). Personally I just put the SA on the MPCD and look down when I need it. If the fight ends up at close range, I should be more worried about what's outside the canopy than being heads-down.
  10. The reason this happens is that the physical throttles in the aircraft have a physical stop that engages with weight-off-wheels that keeps them at flight idle, and it retracts with weight-on-wheels to permit ground idle. As far as the sim is concerned, if the digital command input of the player's throttle has not made any adjustments when the WonW sensor retracts the flight idle stop, the throttle will maintain it's position until an update is received, hence the need for a slight 'pump' to refresh the input.
  11. I've noticed it as well, it also seems to go well beyond the command authority range for the servo.
  12. IIRC you can use HACQ/LACQ/9X through the HUD by disabling the automatic blanking on the HMD page at PB12 (BLNK).
  13. @MTSection You can switch between DDM and DMS from the HSI -> DATA -> A/C submenu with the PB labeled LATLN, which will switch between DCML and SEC for DDM and DMS, respectively. Precise can be toggled on the HSI -> DATA -> WYPT submenu with the PB labeled PRECISE along the bottom row.
  14. Rear seat can technically look "higher" than the front seat. Since it sits further back, less look-up is required to look at a target. Ofc this is a little more applicable in regards to a turn-fight. It's also possible the mission parameters only required one HMD, or maybe it's easier to have the WSO control targeting and let the pilot focus on piloting.
  15. I believe it only happens with Selective Jettison, since Emergency Jettison commands the BRU in the wing pylon to release.
  16. If you drop the missile, it's possible it could be recovered and studied/reverse-engineered. Firing it off deprives/reduces the possibility of anyone from being able to recover sensitive materials.
  17. MSI trackfile memory mechanics aren't implemented at the moment, so it's still tied to the aging setting.
  18. Selecting STRF guns mode for air-to-ground automatically places the radar into AGR mode.
  19. Basically yes, the bird slicers forward of the canopy are the IFF antennas for the CIT.
  20. 82P is correct as-per documentation I've seen, 141 was likely a placeholder.
  21. Works fine on my end (at least this method, which again, is not fully correct per the NATOPS): - Create TGT designation at desired location. - HSI -> UDPT -> DSG -> ACPT - A/C position is set to TGT position.
  22. You can already do INS position updates in the 18, but they don't work quite according to documentation. The UPDT option is available on the HSI on the top row only if the position-keeping mode is not POS/AINS.
×
×
  • Create New...