Jump to content

Rokkett

Members
  • Posts

    61
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Rokkett

  1. You left out the most important one: wing sweep - use bomb mode or a manual sweep angle of your choice to prevent the wings from auto-sweeping. This prevents pitching of the nose up and down that occurs with the variable sweep. Also, don't focus on the basket. I like to watch the refuelling pod, but people have different frames of reference to assist with lining up the basket and then maintaining contact.
  2. If you're flying current DCS stable/open beta then, yes, you will have the most current mission files. All the triggers in R2M3 do work, BUT you do have to follow instructions closely. Also, the Hinds are difficult to locate - they spawn in around the new WP 1 that Jester creates for you, but it's dark and they fly low enough that you may not pick them up on radar. Purists may not like it, but "labels on" in this case will help give you a tally.
  3. Are you playing the most up-to-date mission file, and if so, where exactly in the mission are you getting stuck?
  4. Just re-flew Mission 4: Shock and Awe and it worked fine for me. After AAR, WP 3 was about 120 miles away. Upon arrival at WP 3, I received vectors to land at Incirlik for a Mission Complete.
  5. You can use the Jester wheel to command Jester to give you control of either chaff or flares. This can be cumbersome to use in the heat of battle, but you can bind keys to the relevant command to make it easier. Personally, I use VoiceAttack with Bailey's profile, then you can just say: "Jester, give me chaff" or "Jester, give me flares" Works pretty well for me.
  6. Hmm not sure what has happened to your mission file, but my mission file shows Lead 2 to also have (<current> -3) and (<current> -4) as per Rick_NSX. Also, the vector zones can be a bit tricky to find if your position is a bit off when you RTB, and may require you to hunt around a bit by flying around the base. You could try enlarging the vector zones if you are comfortable doing that in ME. Anyway, here is my copy of Reforger II Mission 3 if you like. ReforgerII_m3_the raid.miz
  7. For those not comfortable playing around with the Mission Editor, Reforger II Mission 2 can be downloaded here... ReforgerII_m2_proportional response.miz
  8. Thanks, IronMike! Have updated the Reforger II -Mission 5 file above to resolve a trigger clash that prevented Uzi group from forming up as briefed if the player taxied too soon at the start of the mission.
  9. See this thread. It contains (unofficial) fixes for Reforger II: Missions 2, 3, 4 and 5.
  10. I have made a workaround which will enable you to play and successfully complete Reforger 1: Mission 5. Download here. Let me know if you find any other bugs. F-14B_Campaign_Mission5.miz
  11. It's actually Mission 5 - I have found a workaround which will enable you to play and successfully complete Reforger 1: Mission 5. Download here. Let me know if you find any other bugs. F-14B_Campaign_Mission5.miz
  12. Whilst awaiting the official fixes to the Reforger II campaign, for those that are interested, attached is my fix for Mission 5: Chem Strike. Let me know if you find any other bugs. Good news is that the final two missions, 6 and 7, do not seem to have any mission-breaking bugs and can be completed as is. Edit (16/10/23): Tweaks to resolve a trigger clash that prevented Uzi group from forming up as briefed. ReforgerII_m5_chlorine.miz
  13. Just to clarify, you do not need to destroy both vehicles. You only need to destroy the technical to progress the mission. Cheers.
  14. I think I have managed to find and iron out the biggest mission-breaking bugs in Mission 4: Shock and Awe, and was able to complete it successfully. Amended .miz file is attached below. If anyone finds any other bugs, I can take another look. ReforgerII_m4_shock and awe.miz
  15. I think this was discussed here:
  16. Hi Sandman, Am enjoying your campaign! However, having a (small) issue with the mission results. Mission 6,7,8,9,11 - fly the mission per the brief, mission objective achieved (as far as I can tell), get the order to RTB, fly home, case 3 landing, park up, shutdown, listen to the end music, quit out to summary page: 50 points, mission drawn. What did I miss to not achieve mission completion? Mission 10 - fly per the brief, strikers drop their weapons, egress, get an option to chase down enemy AWACs; sounds like fun - shoot down enemy AWACs, fly the 250nm home on max conserve, land, shutdown, music etc, quit. Mission Failure (!!!) Why? Easy enough to skip re-doing the missions (they are fairly long, after all), but would be good to know why I am not getting mission complete. Cheers.
  17. This thread shows what u want, plus some other good tips:
  18. Since the last 3 or so updates, I too have experienced the sim freezing/hanging, with sounds continuing to play in the background. Have to ctrl/alt/del to exit and restart. These hangs are reproducible and occur at the same point in the mission. My hangs appear to be related to the F-14AI. If I remove the F-14AI from the mission or simply replace them with an alternative aircraft, then the mission plays out as intended. This is my workaround, but hardly a solution. I have no mods.
  19. From a few updates back: SetCommand for Jester: arg 10015 - tune AN/ARC-182 to a selected channel with the value 0.XX where XX is the two-digit channel number
  20. I too can confirm game freeze/hang enroute to WP 1. Moreover, if I simply replace the F-14 AI flights with another AI aircraft (F/A-18C lot 20 in my case), then the mission plays out as intended (even if I'm flying the F-14). The game freeze definitely seems to be related to an issue with F-14 AI.
  21. Panel discussion here with 3 Tomcat crew members (2 US, 1 Iranian) involved in some of the shootdowns mentioned above:
  22. On the flip side, even if you could simply swap out the unit, you would be swapping out a unit integral to the proper running of the mission. Depending on the complexity of the mission, there would be no guarantees that any number of triggers and/or scripts would not be broken. You'd potentially be spending more time trying to figure out how to get the triggers working properly again (something the mission designer has probably spent countless hours doing), instead of flying something that you can, in fact, already fly.
×
×
  • Create New...