Badger633

UPDATE: Have found a work round and have issued to ED. Will be in next update.

Just put this on the forum.

(Tuesday 10th October 2024) Currently there is a bug which has impacted the 'End Mission' button in mission 4. When you have completed the mission the 'End Mission' button does not work normally so you cannot save your progress. This has worked for years until recently. I am unable to effect a work round and have submitted the issue to ED. Hope they get it fixed as soon as possible. In the meantime would suggest what you do is complete Mission 4 and then simply skip to mission 5. Apologies but outside my control. Will update this thread when fixed. Thanks Badger633

Hey @BuzzLine No specialised scripting used in the mission only standard mission editor. Just checked and yes get same result with the end button not functioning after the first set of L 39's are created. Going to pass this on to ED as a possible bug. Thanks

@Tr33Top Just flew mission 3 with easy A2A refuel all good.

Hi @NightRider87 @silverdevil I have seen this before, unfortunately it is not related to the mission more a DCS bug or corruption of the log. Not that good with logs so best thing to do is report it on the forum under DCS bugs and add your log. Sorry couldn’t be of more help but outside the control of the campaign scripting. Let me know if @NightRider87cannot post onto the Badger633 section of the forums under campaigns.

Hi @Tr33Top Ok , that may explain things. Originally when the campaign was first made coordinates were displayed for a period and then disappeared. Then there was a facility to recall them using F10 for another couple of minutes. As this put a time pressure on pilots especially in VR, I changed the missions so that the coordinates would remain until you pressed the space bar. So the recall was no longer needed. Unfortunately checking through the brief I did not omit the sentence mentioning a recall facility. Thanks for bringing this to my attention and will update the briefs for next update. So does this then explain your issue? Keep the coords up until you have finished with them then press space bar. Hope this helps.

@Tr33Top OK send through the track. don’t think you have to recall coords, they should stay on screen until you press space bar.

Hi @Tr33Top Just flew mission 3 ( not the simple version) and had no problems this end. The F10 functioned correctly. If you are still having trouble could you send me a Track of your mission so I can see why you are not getting the F10 function. Are you on the simple A2A version? ( Make sure, if you leave the tanker early, to abort the refuel as you will not get the radio menu until you do this.) Hope this helps.

All Missions: Old F18 models replaced.

· Missions 8 all variants: 410 unreliable landing fixed. Old F18 models replaced. · All other missions: Old F18 models replaced.

· Missions 4 & 6 all variants: 420 adjusted for A2A bug fix. · Missions 2: Unexpected attack new AI behaviour fixed. · Missions 8 all variants: 420 missing his target fixed. 420 adjusted for A2A bug fix. Timings adjusted and AAA adjusted.

· Printable mission brief updated for missions 12. · Mission 12: Brief updated, SEAD fail fixed. · Mission 9: Voice conflict fixed. Fail sense improved. Route and timings improved, engagement with Migs fixed. · Mission 4: Voice conflict resolved. Early success fixed. Matrix crash fixed in Ace.

Hi @Tr33Top Just to check, assume you are aware there are three different bindings to call up the radio menu? One for on the ground, one for radio 1 and one for radio 2. If this is not the issue i will check it this end.

@Talvid Glad you got it sorted. Yeah this latest mission update definitely falls under the category of designing in more mission flexibility to allow for the different ways different pilots approach the same mission.

Hey @Talvid, I believe you. As you know it is a timing issue, the way DCS works looking for 4 bombs within zone is to look for 4 bombs in the air at one time. Have realised this does not work if the bombs are well spaced so have changed the way success is detected in this mission. Update is with ED and will be in next update. Trouble is ED has increased time between updates which does not help us getting missions fixed for you guys.

@Talvid the fix with ed in next update should work with both options.

@Biggles81 This is mission 11

Hi @Turboboy997 They have 2 R-27R semi active missiles and 4 R-60M missiles. You can select from Rookie to Ace at start of mission, what level are you playing at? As instructed make sure you get well to port to give you plenty of space between you and the Migs and also the SAM sites. Make sure you have turned head on to them early enough do not let them catch you from the side. Make sure you engage Matrix early enough also. Have a look at Flying Kennys fly through.

@Talvid Thanks, the dam thing happened to me once. Was it on ACE this happened. One other person has had this issue on landing, i will check both of these out. @Talvid EDIT: Just checked it out , found the issues fixed them and updated will be in next update. Thanks for the heads up.

@Razor18 At least 45 degrees of bank and keep within 3 miles of WP. This is flying Kenny with Mission 11. You can see his orbit at about time 39:00

HI @Z0mb13 @Razor18 Looked at the tracks, thanks both. @Z0mb13 your right Matrix was refusing to engage, got to be recent DCS updates. Have finally managed to fix it and get him to reliably attack. Will be in next update. @Razor18 Looking at your track it looks like you did not keep to a tight orbit waiting for the SAMs to clear as instructed and started to approach the target. This meant Matrix was to close to get his weapons away and had to come back round which then destroyed the expected flight patterns. Can you try it again but this time keep to the holding orbit until instructed. You might want to wait for the update now I have fixed the issue above raised by Z0mbi13.

Hi @Talvid We have set up a small tolerance zone around the target. What you are seeing is the target exploding as the bomb enters the tolerance zone slightly before the bomb hits. The reason we design this in is from time to time there are bomb inaccuracy especially with AI. This device ensures the mission does not stall if there are slight inaccuracies in the bomb trajectory.

@Talvid Hi, difficult to see exactly what you mean. Can you give a bit more detail. Thanks.

Thanks @Z0mb13 I will have a look when i get back to my rig, and promise won’t laugh.