Jump to content

Ranger79

Members
  • Posts

    1705
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Ranger79

  1. I recommend waiting for the first CAS request, engage, and when the JTAC announces cleared for other targets call in your flight. Thst should give the F16s enough time to engage, try to keep away from Camp 2. Sent from my SAMSUNG-SM-N910A using Tapatalk
  2. Razor, Ok just tried the mission in latest DCS build 1.5.6.1938, the F-16's did engage the AA threats at CAMP 2. It took them alil to get setup, but they started to engage. Also a tip, have your AI flight anchor at the WP3 Hold Point until you are asked to provide CAS. Of course I got tore up, but my flight made it all the way to the Arty CAS call.
  3. Let me check when I get home, the SEAD portion is not required to complete the mission. Sent from my SAMSUNG-SM-N910A using Tapatalk
  4. Did you get a notification to take out the Arty? Also, ensure you take out the enemies at the base camp and the enemy vehicle reinforcements. Sent from my SAMSUNG-SM-N910A using Tapatalk
  5. They should call when they are cleared to engage, and engage the AA threats unless there is a bug with them holding. They start engaging on Rodeo initiation. Sent from my SAMSUNG-SM-N910A using Tapatalk
  6. Thankd for reporting, can you confirm you are running the latest version of DCS World? Try a manual update under the DCS World menu under your Programs tab. Sent from my SAMSUNG-SM-N910A using Tapatalk
  7. Thanks Badger enjoy! Sent from my SAMSUNG-SM-N910A using Tapatalk
  8. Ensure your DCS World is updated to the current version, try a forced update if it does not auto update. They should be taxing with you. Let me know if that works. Sent from my SAMSUNG-SM-N910A using Tapatalk
  9. Thanks Bart, once 2.5 comes out I will be ensure all missions are operational and updating the supporting documentation to be more print and read friendly.
  10. There is no bug with the factory coordinates, if you are looking through the TGP it is usually masked. Make sure you have the correct prefix. Sent from my SAMSUNG-SM-N910A using Tapatalk
  11. Agreed, ensure you follow orders given in the mission. Sent from my SAMSUNG-SM-N910A using Tapatalk
  12. I would love too but it is not possible with the current DRM protection. Sent from my SAMSUNG-SM-N910A using Tapatalk
  13. Rest in peace Blooze.
  14. Razor I'll check the first 9 line request and if the target explodes prematurely. The GBU12 request is accurate above the cloud deck, I'll check the spelling in the text. Sent from my SAMSUNG-SM-N910A using Tapatalk
  15. Tintifaxl, Spoiler:
  16. I will take a look tonight, thanks for reporting. Sent from my SAMSUNG-SM-N910A using Tapatalk
  17. Thank you will update Sent from my SAMSUNG-SM-N910A using Tapatalk
  18. Good to hear! Thanks for the feedback! Sent from my SAMSUNG-SM-N910A using Tapatalk
  19. It should be fixed in beta, please look at this post https://forums.eagle.ru/showthread.php?t=179251 Sent from my SAMSUNG-SM-N910A using Tapatalk
  20. What version of DCS World 1.5 are you on? There was a bug before Christmas regarding triggers but it was fixed. Also, try to manually update DCS World, sometimes I have to do that to update the DCS. From the video you did everthting right. Sent from my SAMSUNG-SM-N910A using Tapatalk
  21. Make sure you destroy the troops along with the brdm for the ambush to progress the mission. The KA50 is suppose to be in the mission. Sent from my SAMSUNG-SM-N910A using Tapatalk
  22. Guys, I understand your frustration, but this issue is out of my hands. The only thing I can think of is to submit the campaign with Hawg Flight in a HOT start vs COLD start. Sent from my SAMSUNG-SM-N910A using Tapatalk
  23. Mission 9 or 10? Sent from my SAMSUNG-SM-N910A using Tapatalk
  24. Hello, I understand, the issue has been up channeled for resolution, hang in there we will get it fixed. Thanks in advance. Sent from my SAMSUNG-SM-N910A using Tapatalk
×
×
  • Create New...