Badger633

Hi Like I say if you have Tacview and send me a file I can advise. ( Would recommend everybody has Tacview, its free and a great analysis tool. Unfortunately DCS tracks do not work well.) Are you sure you have the coords down exactly? Also make sure you do not drop too early you need to clear the mountain before you make the drop. I will also do a run through check my end. Hope this helps

Hi Are you running any mods? Are you openbeta or stable versions? Has this happened more than once or did you just try this once? Do you have Tacview? If so a Tacview file of the flight would be helpful to identify where an issue may have occurred. The low level fail should only occur up until you start to rise to go over the mountain to release your JDAMs. This was a recent fly through. EDIT 280523: Checked out why you had a height failure. Did not anticipate someone would be taking out the planes in the airfield with gun. This impacted a key trigger. Have now updated the mission which will be in next update so such an event will not occur in the future.

Hi Obviously the campaign normally works and has done since it was published. Firstly are you running any mods as these have very strange effects on DCS and the operation of the AI. Also are you in open beta or the stable version. (DCS fixes take longer to reach stable version.) I have seen this strange AI behaviour once or twice in the past. It is not related to this particular mission or campaign. (It is not controlled by the campaign scripting). It is a DCS bug. You should report as such to ED under the bugs section so it can be fixed. If you observe from the rear he will pass to the right as you are not there. What should happen is when you are there the AI adjusts its path to suit. Normally this odd bug shouldn’t be a problem as your wing is slow to join for the plug and takes quite a time to refuel. You will have completed before your wing and be waiting to the right of the tanker out of the way. In the meantime until this bug is fixed as set out in the brief you do not have to fully refuel but just top up as required. So if you are happy you have enough fuel you can simply refuel for a few seconds and then cancel the refuel and wait to the right of the tanker for your wing as normal procedure. The reason refuelling has been added on some missions even though you may have sufficient fuel is that your AI wing may not. Your wing man has the task of catching you up for joins and keeping in formation. Depending on how you fly the mission he can quickly run out of fuel. If he does, and sometimes he will, then you will lose him and this will break the mission. So the refuels are more for him than you. Unfortunately DCS does not allow us in the editor to give selected AI unlimited fuel at this time but we have requested this. Hope this helps.

Hi A few videos here. The last one managed to release at 13000 feet. So release high, or medium and jink make sure to bang out those flares or even very low and fast using gun. ( It is a house full of armament) Was it this one Good luck, can be done. Lookin For Trouble | DCS F/A-18C Hornet | Serpent's Head Part 2 Campaign Mission 3 | 4K 60FPS! - YouTube

Glad you got it sorted. Enjoy the campaign

It shouldn’t, but could be, DCS AI can react in unexpected ways to changes. If your on stable then that could be the issue. DLC campaigns are written and tested in the Open Beta version. This version gets all the latest updates first and also our Campaign fixes. Stable doesn’t get these until sometimes months later. So it could be a DCS change has impacted the way AI reacts which they have fixed in open beta but not yet in stable. It’s hard to know. As I run only in openbeta, all I can say is that at this end running in open beta with no mods and running the campaign as intended it all works. If you want to change to openbeta there are videos out there showing you how to do it. If you’re still green, as you say, I strongly advise you to get Tacview. It will allow you to analyse what happened in a flight so you can learn much quicker. Also great for me as I can check exactly what happened. The DCS track system unfortunately is not reliable. Hope this helps.

Hi Do you have Tacview. A Tacview file of the mission would be really helpful in finding what the issue might be. It’s free and worth getting as it will help your flying no end. Are you using stable or open beta? Are you running any mods, you should not be running any with all DLC campaigns as they can cause these problems. How many times have you tried, does it keep happening. Are you flying at 300kts to allow Sting to format with you before they break. I will check it this end and update here. EDIT: 14/5/23: Just flew the mission in open beta using the MT version. Sting did as they are supposed to and carried out the ground attack. So couldn’t reproduce this end.

Thanks Rinze, you’re right that is a great video I often send the link out to fellow pilots. The Hornet radar can be effective if used correctly. Also the head mounted display with the 9xs is deadly. I fly in VR a 100% and find when in close quarters having the SA page open at say 10 miles is excellent for knowing where all the bandits are. Danos you should find that video and some practice with the radar should help. Also remember to go to expanded view (EXP button bottom left) when changing targets in TWS. I have purposely given four 120s so you can use sacrificial missiles to make your enemy start defensive moves which will put you at an advantage.

Sorry you’re absolutely right, just trying to help out another fellow pilot and got my wired crossed.

Just checked out the normal version of Mission 1 using Openbeta with no mods. All works well. I have sent you a PM with Tacview and some advice. Hope this helps.

Hi grmnir Thanks for the kind words, glad you enjoyed it. Hope move on to the Rise of the Persian Lion where 'Fords' story continues.

Thanks for the kind words. Your wing man should be attacking. I will take a look this end to see the issue. If you have Tacview please send me the file it is very useful trying to track down a bug. Also which version of the campaign are you using and are you closed beta or open beta. Finally are you running any mods. This can impact any DLC campaigns in very strange ways. Never use mods with any DLC campaign. A little tip if you have quite large gaps between use, is for you to make your own brief notes of how to use each weapon. In this way your not back to square one if you haven’t played for a good while, a quick scan of your notes and your quickly back in the loop again. I will update this if I find anything. EDIT: Just checked out the normal version of Mission 1 using Openbeta with no mods. All works well. I have sent you a PM with Tacview and some advice. Hope this helps.

Hi As declared on the radio you need to first dispatch the two on the right, your wing man will not attack these. Make sure your radar is setup correctly, you need to be on HI. Set to TWS and lock them and use your 120's. Immediately after go defensive and look for the other two keep situational awareness using your SA page. Make sure you have your HMD on as you can take the others at nearly 90 degrees to your travel using it with your 9x's. Hope this helps.

Hi You do not have to do anything out of the ordinary. Set your JDAMs as normal ensuring the preplanned data for each bomb has been set up at the beginning of the mission as you descend. As you approach low level behind the mountain you pop up over the mountain, just clearing it, so are visible with the targets. Key thing here is do not release too early as you need to get clear of the mountain below you. Should then be a normal release but you are then exposed so are going to have to dive to the right and use the low level hills for cover during your escape, at least until your bombs hit home. Hope this helps.

No problem, glad you got it sorted. Any time.

Hi You cannot communicate with the AWACS in this campaign, there should be no need, all information you need is scripted and given to you by Strike. Regarding the radios are you using the correct press to talk keys for your communications? There is one for COMM1 and another for COMM2. Hope this helps, let me know.

Hi Thanks for the Tacview, could see the issue straight away. If you don't know which version you will probably be on Stable. You have to to select Open beta from the downloads. I have fixed this issue back in January but it may not have filtered to the stable version yet. You can check this by starting the mission where the screen shows you the brief. If you pan down the page to the bottom and just above 'KNOWN THREATS' and below the text above, 'Good Luck enjoy', there will be number. Versions 13 and 14 have the fix but 12 will not. The function of open beta is for people who want the latest updates DCS can offer. The downside is there are obviously a few more bugs as improvements are being issued to the masses for the first time. I, like all campaign creators, work in open beta. There is always a delay between updates being passed from beta to stable which can sometimes be months. I think this is what may have happened here. If your version is 12 or below this is why it is not working correctly. This as a result of a past change to the DCS AI which impacted the mission and the fix has not got to stable yet. Let me know what version you have. If you want the latest of things you can convert to Open beta and there is plenty of guidance on this in the forum.

Does it work correctly with SSA, so the vibrations are sent to the correct motors as with the jet seat?

HI , thanks, let me know, as like to fix any new issues in my campaigns as soon as I can. Would suggest you install Tacview in any event, it is free and a perfect tool for analysing your flight in a way you cannot perceive in ED. It's feed back will definitely improve your flying and combat. Unfortunately DCS tracks do not work very well. Can you confirm are you in open beta or stable versions of DCS, thanks.

Hi Were all four bandits killed? There will be a radio message confirming this. Are you running any mods? If you have Tacview a file of the flight would be really useful in identifying the issue. I will check it out. Thanks

Thanks @ClydeBigBird for your kind words. When creating a campaign I work hard on just the aspects you have mentioned, so it’s great to see they are noticed. Glad you like the @Cathnan idea as I am working on my next campaign which is just that. Thanks @Cathnan

Hi Hippo Just checked through the script. Found a one digit error in the removal of the second set of coords. Corrected this and will be out in next DCS update. Thanks for the heads up Enjoy the rest of the campaign

Hi, to be honest it is best if the space bar isn't tied to the trigger as a lot of campaigns use the space bar in this fashion. I will check out the script to make sure it is as it should be and let you know. Thanks for the heads up

Hi, just checked. Stay over the city. If you look at the brief it shows your rectangular area for the upper air cover supporting Sting. Just noticed that there is a conflict in that the return fail check zone starts at WP2. I will get this reduced in the next update. So in a nutshell carry out your patrol over the city area and all will be well. Thanks for the heads up. Make sure you have traffic off on this one. If you need help on targeting moving vehicles in the dark, did a video on this if you need it. Hope this helps

Glad you got it sorted, enjoy the rest of the campaign.