Badger633

@rob10 Hi, took a look, think i found the problem, there was a break in logic which meant that when you get a 2nd fail the dam would explode but then it thought you had killed them and gave a pass, which was not the case so the end mission count down was already started, meantime success voice was in play until the countdown ended the mission. Anyway! Fixed it just got to check but will be in next update. Thanks for the heads up.

@rob10 Yes please a Tacview will be useful. It could be a timing / logic issue or maybe a unit still alive which later died which shouldn’t happen. I will take a look. Thanks for the heads up.

@Razor18 Thanks will take a look at the Tacview. If I am right, the conversation on left and right all comes after the trigger activated by you telling Matrix to engage. It would probably have made more sense if you got further away to the port and gave Matrix the command to engage earlier. That dialogue then takes place as they are still in the distance and approaching and clearly identifiable. Matrix has been scripted to attack the group he indicates but this is DCS AI and I suppose like in real life things don’t turn out as planned, “the confusion of war” I will check out the track thanks. This engagement can be bit manic but normally works out. Just so you know in all engagements your wing is only scripted to engage certain aircraft you will always have to kill some of them. This to prevent the player being able to sit back and let the wing kill them all. EDIT: Looking at the track, yes, you kept heading back west far too long and carried on going west even when you eventually gave matrix the engage instruction. As you were very late turning you were at a disadvantage as the Mig was already lining up on you. Suggest turn 90 degrees port straight away to get distance and height don't head west you are going to engage the Migs then 180 degree turn on Migs and engage Matrix so he can start lining up early. Voice overs should make sense then also. Hope this helps.

Thanks @rob10 What should happen is if you miss first time you get another chance for a second go, if that one is missed you get the fail. Did that happen or did fail after first miss? Have you a track? I will have a look.

@Razor18 Didn't you realise that ED has employed the new 'Green' porous bunkers. The 'IFA RDR' warning on the HSI is to tell you the GPS is not available for the 'In Flight Alignment' system you have switched to. This is because you are in the bunker and assume the satellites cannot see you. Move outside the bunker and message goes, just tried it.

Sorry @Razor18 i have confused things by using the word Auto. What i meant was to use CCIP but set up the bombs so they drop one after each other automatically at 500 feet intervals with one press and hold. Yes the drop line is distorted probably the wind component. You have to get in a position where your impact cross is going up the runway even though its off to your side. This is flying Kenny running through the mission.

@Razor18 I've come up with a cunning solution how to check the bombs which will not fail if flown as you did. Will be in next update.

@Razor18 Yes barometric, Try to get up to 2000 baro, set bombs to drop every 500 feet , should work fine. I am putting feelers out to see if there is clever script to sense the bomb explosion locations otherwise might just check first bomb release location not ideal but you wouldn't have had a problem then. Thanks for the heads up.

@Razor18 Thanks for the track. The reason you got the fail is that the trigger is looking for 4 bombs in the air within the zone. Unfortunately it's the only way we can check you have got all 4 bombs within the zone. You were down at 1,400 feet and because you manually released the bombs the first hit before you released the last. If you release at the 2000 feet, called in the mission, and automated the bomb drop you will get all four in the air in the runway zone which will not then fail. It's the only way I can check the release accuracy. Will research see if there is another option or maybe only check position of first bomb. Good accurate drop though

@Razor18 yes agreed and that's what I'll do . cheers. Will look at Mission 4.

@Razor18 I will check out mission 5. You wouldn't happen to have a track or a Tacview of the flight? The trigger is definitely only if Ford is below 40 so could be a bug. Regarding using the TACAN distance never used this as a trigger before. However that will be exactly the same as using moving zone. If i set the zone at 7Nm radius you will get the trigger when Ford is 7Nm from the Carrier as measured using TACAN but not distance from WP0. Think in mission 5 I set moving zone at 8Nm to allow for start up so you would be approx 7 nm from WP0. In hindsight think i will just set zone to 7NM so at least on the TACAN you would be exactly 7Nm when you get the voice.

HI @Razor18 Thanks for the feed back, always welcome. Mission 5 has a series of things it looks for to trigger a success, just checked, one of them is a Fords speed needs to be below 40 knots. So did you only just get off again as you must have dropped below 40 knots or there is a DCS bug.? The Case 3 departure diagrams are taken straight from the DCS supercarrier instructions, page 26. Best let them know. The 7NM is a difficult one to get exact. The reason is the voice is triggered by going outside a moving zone which is set about the Carrier. So as you fly out to what was the 7Nm point, the carrier is still following you and so is the 7Nm boundary but WP 1 is not. You do hit the zone boundary due to the massive speed differences but the exact distance from WP 1 and the Carrier will depend on your time taken to start up and the speed you fly the first leg at so darn nearly impossible to get it spot on unfortunately.

@Razor18 No problem. If you follow the video all should be good.

@Razor18 agreed but the DCS AI is the only one we got to work with.

Hi @Razor18 Thanks for the track. Yeah it shouldn't happen like that, the red arrow on the left totally lost the plot. I know this is DCS AI but when the mission was created all the aircraft kept formation very well. I had worked long and hard to achieve it. I have seen them getting more and more erratic over the last six months of DCS updates. Will have to let ED know. Have you tried more than once as it doesn't happen every time, it's never happened to me. I will fly it through again. EDIT: Just ran it through and it did not happen this end? All reds stayed in formation, allowing for the the DCS AI inaccuracies. As I said try a second time and see if you get the same problem.

Hi @Razor18 Sorry can you explain, I have done a tips video for Mission 2 here.

@f4tca7 To be honest its not normally as frequent as this but DCS over the last few months have done what appears to be a lot of AI changes. So really you shouldn’t have to be jumping through these hoops. You will note in mission 9 next I have split this in to 2 parts so you are not having to replay the ingress.

@f4tca7 Thought it might be the speed. I have adjusted things now so speed shouldn't make any difference in the future. Again in next main update. Not sure about the lazing matter. In the script the JTAC is lazing the convoy with 1688 and will remain doing so. Not sure if the 1688 might be hard wired in the new fuses, could well be wrong on that, but it would explain your issue . To be honest got enough problems keeping the missions working with the DCS updates so don't go looking for other issues.

@f4tca7 are you using automatic start as you appear to be very quick after Dodge? This timing could be part of the problem with your point 1 above.

Hi @f4tca7 Yes I am aware point 2. He is definitely attacking the wrong target. He is down to bomb his own. Same old story I’m afraid as we get updates the AI is acting differently. I have fixed this now so this won’t be an issue in the future and will be in next main update. As to the first point I cannot get it to happen this end. Will look into it. Thanks for the files i will check them out.

Hi @Biggles81 Not sure why your not picking them up. Make sure you are in TWS and PRF in Hi Have you got your SA page up as well as your radar. Also by moving the radar designator around you will see the height zones covered in numbers next to it. You can adjust this by moving the aerial elevation. Will have to try it myself. If I remember the first thing you will see is your deep SEAD flight returning so don’t shoot them down. You should also be picking up the EWS triangles at the top of the radar picking up the migs radar. Hope this helps.

Hi @f4tca7 Checked it out, you are correct. DCS AI updates again . Axe should left area for another air base. The AI is now refusing to land there and instead loitering in the carrier area this having the effect of putting them in a position of attacking the enemy plane. Have fixed it now and it will be in next update. Very frustrating but once again out of my control. Again this mission has worked well over a year. Thanks for the heads up.

@alboon2000 So the problem is the JSOW landing short as you say. Coords and heights are all correct so could be a DCS bug regarding the JSOW flight. I will fly it this end to check, I will let you know.

Hi @alboon2000 The coords are correct. That is where the hanger is, you just cannot see it as it is a hidden object. Could you send me a track or a Tacview file of of your flight to help me identify the problem you are having. Could be dud bomb or a bug with the JSOW flight or maybe something you are doing.

OK @rosty Checked out your track and produced Tacview from it. Your correct you hit the target . The new problem is, (as this mission has worked for years check out Flying Kennys fly-through of the mission in the playlist on my you tube channel), that the AI wing has not done it's job which it has done consistently until now. For some reason it looks as if the bombs have either missed or were dud maybe. This is why their target warehouse was not destroyed, even though you got the message that both were destroyed, as they normally are. I will adjust this mission so that the wing never fails and so preventing this issue in the future. As I say, it worked before so out of my control, you just got to love DCS updates. There is a campaign creators saying 'Never trust an AI to do something that may break a mission' Thanks for the heads up , at least it wasn't you, you hit the target on the head. Will have a fix in the next update.