Jump to content

RAZBAM_ELMO

Members
  • Posts

    2093
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by RAZBAM_ELMO

  1. Right, so what is the issue exactly if you could provide some more detail?
  2. Eventually yes.
  3. TOT is not yet implemented correctly and will be later on.
  4. The ACF will try to correct the stick movement up to a certain point until it disengages. However it will be stuck at the last correction position when it shuts off so if you plan on yanking and banking, make sure to disengage your AFC first before you do that. If you have a stick, I recommend binding the paddle switch.
  5. The new gun restrictions are theat the gun will not fire under 70% at Sea Level, this increases as you increase in barometric altitude.
  6. Note in MP and lengthy SP sessions TACAN is known to just stop working for all aircraft. Follow the bearing in, when you do not have visual on the tanker. Remember you should be in A/A mode.
  7. need to make sure your sensor is in the correct mode i.e TV for DMT, MAP for EHSD, MAv for Maverick, TPOD for welll......you guessed it TPOD
  8. Check your axis controls, you may need to set up a deadzone, I know I had to
  9. ammo is staying as is, sounds will be addressed later
  10. SME said that they never used the Mav-Fs at all because it was not as accurate when combined with LMAVs and the TPOD. As for the gun pod. The ammo pod is correct for the MLU NA Harrier. Our SME has explained that due to more accurate guided weapons being available to the Harrier, they did not continue to use the API rounds and the belt was removed from inventory. Doctrine limits the use of the gunpod to anti personel and light vehicles or structures with the SAPHEI-T. I do agree that a more accurate gun sound is in fact needed. @chief when do you want to meet up and chat? Also editied title to be less derrogatory rather than shut down the thread.
  11. OK, so Im moving this to the Harrier general thread, there is new TPOD logic as well as procedures for dropping JDAMs in the Q4 update which I recommend reading thoroughly. The DMT is NOT used. When using the TPOD SSS depress twice in under .8 seconds to make TPOD HTS mode, it will operate in reverse if it is not because it is not the designated. Go AG mode, master arm on and select the JDAM ( make sure that the DESG on the EHSD is boxed) and make sure you're in AUTO either via the OSBs or via the ACMI panel. Once in TPOD mode, put the TPOD in point track (PT). Laser range then Waypoint Increment (Winc) long ( hold for over .8 seconds) to make the target T0. You should then see the range rings appear on the EHSD as well as the steering cues on the HUD. Release when in range. Also multiple JDAMs are able to be dropped in a single pass by either slewing the TPOD to the next target after following the steps above or creating markpoints and Winc short to cycle target points and release when in range.
  12. So during these you did not have the DESG boxed? Were you using the TPOD or DMT with the DESG boxed? Ill have to look into this further when I can get time on the computer.
  13. TOT is not fully implemented and is going through internal refinement. Marking as FUTURE IMPLEMENTATION and moving to RESOLVED. Please make sure to check previous resolved bugs as TOT was previously mentioned.
  14. As the G4 TPOD is not fully complete all of its features will come at a later stage. However, its orientation is correct as verified by SME. Slant/ plane has been looked at and we have inquired ED to see if modelling it is in fact possible with current engine. Marking as FUTURE IMPLEMENTATION and moving to resolved.
  15. so when you SSS left all works as intended correct? When you press to DCTR button on the EHSD page are you already in DCTR mode?
  16. Im here to talk if you wanna talk man. Sent from my SM-N960F using Tapatalk
  17. Looking into this, may have been misinterpreted by the manual but will confer with the SME.
  18. Thankyou for the report gentlemen. By chance do you have DESG boxed on a waypoint? Are you in NAV mode, AG or does this occur in both?
  19. Marking as USER ERROR and moving to RESOLVED
  20. .log file required then please.
  21. @DanielNL I'll say it again as I have many times before. I need a .trk file inserted into the forums here, not an external link.
  22. Marking AS INTENDED and moving to RESOLVED.
  23. This was noted by the and is an issue we have contacted ED on which will be addressed when we have a better idea of how the FLIR code works and how we can best apply the filter.
  24. @Schmidtfire it working for you at all?
  25. Improved LAR percentage HUD and EHSD behaviour and symbology will be improved at a later date. Marking as FUTURE IMPLEMENTATION and moving to RESOLVED.
×
×
  • Create New...