Badger633

Glad you got it sorted. Enjoy the rest of the campaign

Hi Just flew the mission 11 in the current open beta and all worked out fine. The Migs attacked as scripted. I Have not checked in MT yet. You should have the whereabouts of your set of MIgs as you are told they are out of Bandar-e-Jask which is your way point 8 and also your bulls. They will also be shown on your SA page if set up correctly. Make sure your radar is set to HI as well. Stay roughly in the area where you have taken out the sub and then head towards them, probably on a bearing in the 350's. If you move too far away from them to the south they could decide not to bother as this is how DCS's AI react sometimes if you stray too far away even though they are down to attack. Hope this helps. As I have said have not tried in MT version yet. Let me know if you still have a problem.

Hi No I had fixed this once. It could be this latest update has broken it again. Are you playing this in open beta and if so are you using the MT version. Also are you running any mods. If you have Tacview, a file of one of your flights would be useful. Thanks for the heads up. EDIT 17 April 23 : Have just flown the mission in the normal version ( not EZ A2A or Increased difficulty) in the current open beta. All worked as it should so cannot repeat this end. Not tried in MT yet. Are you sure you that all four bandits were killed? The radio messages will confirm this.

Hi Are you setting the e fuse to instantaneous?

Hi Will take a look. Are you in current open beta and in MT. Also are you running any mods? A Tacview of your flight would be great if you have one. Thanks

13 APRIL 23: Mission 4: MIG call off fixed. Missions 1 to 13: Mission briefs updated including Introduction. Missions 6,8,10,13: Dark kneeboards added to night missions.

13 APRIL 23: Mission 1 to 15: Mission briefs updated including Introduction. Missions 5,7,9,13 & 15: Dark kneeboards added to night missions.

13 APRIL 23: Mission 1 & 6: Typos corrected, zones adjusted, safety helo added, fail images added, mission briefs updated. Mission 2: Infantry movement fixed, mission brief updated. Mission 3 & 5: Typos corrected, zones adjusted, WP1 moved, safety helo added, press to remove coords added, fail images added, mission briefs updated. Mission 4: Text adjusted, zones adjusted, WP1 moved, safety helo added, fail images added, mission brief updated. Mission 7: Safety helo added, press to remove coords added, fail images added mission brief updated. Mission 8: Safety helo added, JTAC radio note added, press to remove coords added, fail images added, mission briefs updated. Mission 9: TGP changed to ATFLIR, supply lorry added to mortar group, kneeboard updated, fail images added, safety helo added, mission brief updated. Mission 10: TGP changed to ATFLIR, press to remove coords added, safety helo added, fail images added, mission brief and kneeboard updated. Missions 6 and 10: Dark kneeboards added to night missions.

No problem, glad you got it sorted. Thanks for the kind words. Enjoy the rest of the campaign.

Hi The carrier has turned course to help with the crosswinds. The carrier is moving forward at 10 kts at a bearing of 329 degrees. The runway being on a diagonal to the carrier course is at 318 degrees. The wind of 35kts is blowing in the direction of 138. So exactly down the line of the runway. Trouble is you are always going to get a slight crosswind component caused by the movement of the carrier along its course which is different from the runway. Truth is it s just one hell of a night!

Enjoy the rest of the campaign

Yes to be honest I don’t understand it either. Once you’re past the SAMs it’s normally plain sailing.

If it’s triple A then keep jinking. Triple A normally aims where it thinks you will be From your current vector.

Hi, thanks for the kind words. Let me know any glitches you had and I will fix them. When first complete the campaign works fine but as DCS is updated glitches appear which need fixing, so a heads up is really useful. Hope you enjoy Rise of the Persian Lion 2, this will take things further again, so strap in

No problem happy to help. No not designed specifically for ACLS, manual is a challenge and character building You might be right about the winds I don't know for sure. It could be a bug. As I say I will give it a go myself and see how I get on. Still worth putting out there on the forum though as it may be a bug.

Hi The truth is I never use ACLS for landing always fly in manually using ICLS. To confirm the fact as to whether the jet catches a wire is not a thing controlled by the mission editor. All that has to be done in the editor is set up the ACLS and Link 4 systems which has been done correctly on all the missions. Probably not the case but is your jet within weight limits for the trap? Also are you running any mods at all. ( These can have very strange effects.) Are you using Stable, Open beta or Open beta MT? If the above is not the case it is worth raising query on the forum as a possible bug. I will give it a try myself and see how things work out. Badger633

Hi In this instance you will have to get both aircraft. Part of it a DCS issue in that you cannot designate an AI for both ground attack, which he has just done, and air attack. Sometimes he may help. Even though not designated but it is a bit in the lap of the gods, so assume you have to take out both. Trick is get the first one with your 120 then go defensive looking for the second with your HMD and 9x’s you shouldn’t have too much of a problem, as you can fire at almost 90 degrees. Hope this helps Badger633

Hi, thanks for the kind words. Yes I think there is a current DCS issue regarding visibility in VR. I have found that the carrier runway and the laser guide doesn't appear as early as it did before at night. I will have to check if it is only a VR multi thread issue as I have noticed it in MT so far, will have to check. If you are noting a change with visibility in VR check if in normal VR and MT and make a report on the forum for ED. They are looking for these sorts of reports now. Will check out and correct the brief, thanks for the heads up. If you enjoyed this campaign, and haven't already, you might want to continue Fords exploits in the follow up campaign Serpent's Head 2 available in the e shop. Cheers Badger633 EDIT 26 March 23: In game brief to bomb the blocks corrected and issued in User files.

Hi Glad you enjoyed the campaign Not sure what I set the Migs at but it is always a difficult one, as pilot experience varies so much. The ideal for a player is to overcome the challenge but only just. In this mission as agreed on the radio. Concentrate on the left mig. After take out the one on the right if you get a chance but concentrate on being defensive. Not sure what happened with the ACLS but sounds like a DCS thing.

Thanks for the kind words. Been doing a lot of improvements to the existing suite of campaigns. The last lot due in the next update. Also big improvements to the free original Serpent’s Head Campaign in the user files. Now with human voices and many other improvements. Yet to start the new campaign but have done a lot of thinking. Ford will probably be moving to the Med on the Syria map. Which may start with problems along the Greek and Turkish Cypriot no go border.

Hi Wiggo Thanks for the kind words. When using the ATFLIR with IR Mavericks you need to : 1 Get a point track with the ATFLIR on the moving vehicle. 2 Make your Maverick IR screen active and then uncage. The Maverick will then look at the current ATFIR point track location. Then if the target has a good IR profile and at the right distance the Maverick should lock on. 3 If it does not lock on then quickly cage and then uncage. Repeat this until you get a lock. The ATFLIR does not send moving information to the Maverick only the point where the vehicle is at each time you uncage the Maverick. This is true of both TGPs. This is not the easiest thing to do and can also be hampered by other IR sources such as road lights. The better method when using IR Mavericks on a moving vehicle is as follows. 1 Use your Radar in GMT mode. The moving vehicle will be easily located, then lock the radar on the vehicle. This radar lock is much more reliable than the ATFLIR which has a habit of being distracted by street lights. 2 Once you have a lock then as above make the Maverick screen active and cage and uncage until you have a definite lock, closed cross hairs. I have a video tutorial showing me using this last technique. Warning the extract is taken from the last mission of Rise of the Persian Lion 2. Hope this helps Badger633

Glad you enjoyed the campaign. You will find the next two campaigns also include an eze air refuel as well. Badger634

Hi Yes there is a sparkle and it is visible with your gogs. If you played in MT I am not surprised it was not visible. MT has a lot of issues at the moment. Try it in normal and you should see it. To be honest I have only tried it viewing it with the gogs as after that it is quite clear where it is especially with all the aaa coming up. I will check it myself as it will need reporting to ED. If you find the same you should report it as well. Glad you enjoyed the campaign

Hi Yes, you are going too close to the SA10,( In fact it is the SA10 which is shooting down your missiles if you look at your Track), As set out in the in game brief: "Keep your distance from the deadly SAM SA10 system using the long reach capability of your AGM154C JSOW’s. DO NOT GO CLOSER THAN 40 MILES. To keep clear Overlord will suggest you be above Angels 30, you may really need to be closer to Angels 40 before making your run in and turning away straight after delivery. You must stay in the area at a safe distance until it is confirmed all your targets are destroyed. " Try again but keep outside of 40 miles, much closer and the SAM site will go into red alert. Hope this helps Badger633

Yes, will have to play in normal OB until ED fixes the fog. It’s a problem generally not just this mission.