ChillNG

Just tested and all ok. No one else has reported it so I'm assuming there must be an error in your radio settings. The new radios can cause issues, so use the old UHF radio if needed.

Have just tested the mission myself and everything worked as it should, box was in the right place and bombs were a direct hit. Stuff like this won't be anything caused by the mission itself, there's no way for the mission setting/triggers to interfere with aircraft systems like this. I'm guessing you did something wrong, but I'm not clear on what yet, as from what you've said you sound like you've covered all bases. My hunch would be an INS issue. I checked the TGP coords shown on the TGP screen, they are correct for the low blow BTW. Did you fly this pre or post latest update? Latest update has the new fuse setting included so CBUs, not sure if this will have any bearing but worth checking if you're trying again.

Campaign Updates 05/06/24 FIWOS: Missions 1, 7, 9, 10, 11 - updated fuses on CBUs.

Working on the final mission now, campaign should be shipped off to ED end of June/early July. Release likely in next few months after

Ha ha brilliant. That's the dynamic nature of the campaign, love these war stories!

No LOWOS is almost done

Yes it will .

Yeah I know., it's a tricky one. I'm not expecting high sales overall for that reason, but I promise the campaign won't disappoint if you decide to go for it.

Thanks, yeah it is a bit of a leap of faith, but it's a risk in prepared to take. I already had a ton of work put into the campaign before things blew up so thought what the hell, hope for the best and push on.

The official announcement of the the Falklands '14 campaign for DCS World, in development now for the AV-8B Night Attack and South Atlantic map. In 2014, a rejuvenated Argentine military launches a surprise attack on the Falklands, swiftly capturing the islands and avenging their defeat in the 1982 Falklands War. Emboldened by significant Chinese support, Argentina digs in and prepares to defend against the inevitable British attempt to re-take the islands. Outnumbered, outgunned and over 8,000 miles from home, the British task force and it's handful of Harrier pilots faces a seemingly insurmountable challenge to take the Falklands back. Falklands '14 will offer the definitive DCS: AV-8B experience. The campaign will feature detailed naval operations from HMS Invincible; including an interactive crew chief, fleet air traffic control, and departure and arrival procedures. Inspired by events of the 1982 Falklands conflict, the Falklands '14 campaign will push virtual Harrier pilots to the limits through a thrilling and intense set of missions. Falklands '14 is in active development now and is due for completion in the first half of 2025.

Thanks very much! On the home stretch now for LOWOS, hopefully will be completed soon.

Your attack looked fine to me. Don't think wind is a factor, it's not hindered anyone up to now and only around 8 knots. Issue is definitely the new fuses introduced, see the pics below. Old BA for CBU-87 was 1500 ft, the fuse now defaults BA to 300 ft. I dropped a pair of 87s, releasing at the same point you did, one set for 300 ft (new default), other set for 1500 ft (old default). See how one frag pattern goes long and one is on target. I'm updating all CBU missions in the campaign to accommodate new fuse settings.

Might be related to this? Check you BA setting, could be the new fuses need updating as well. EDIT - just done a few checks, the default CBU fuse setting has a very low burst height, I will update ASAP, although it is still pretty accurate, just little spread on the bomblets.

No idea on real life, but at the moment in DCS the CCIP indicates where the first hit of the cluster will be, the chain of munitions then extends forwards from that point. Bogey Dope does a great example on this video at approx 34 mins, might help you get your eye in.

Thanks for the update, sounds like a bizarre viper bug must be blocking DCS detecting the radio frequency when you turn up the volume, very strange but glad you figured it out. Appreciate you picking up the other campaigns, thanks for the support!

Hi, no I don't believe it's bugged, no other reports of issues and I have just tested with no problems. Must be an issue on your end, from experience most likely culprits are: - A mod causing some sort of conflict, if you have any installed I recommend removing them and trying again. - Another user recently had an issue with the DCS 'press spacebar command' not working because they had recently set up some DCS general controls (the ones for UI layer/general not aircraft specific ones) that were using the spacebar, this was causing a conflict. - It is possible to accidentally cancel the spacebar command by pressing backspace, but it's unlikely you did this every time. - Assuming you don't have easy comms enabled if you're this this far into the campaign, but worth double checking. Hope some of that helps, if not send a track and I'll run it my end to see if I can see anything wrong.

Campaign Updates 22/05/24 Operation Cerberus North: Mission 16 Part 3 - Stopped Mi-24 shooting at player with AT weapons. FIWOS: Mission 8 - Minor fixes to SAM behaviors.

Hi, thanks for the feedback, much appreciated! The cold start time is always a tricky one when doing TOTs, if you allow for an extra 15-20 mins those that do want to do the full startup then it will likely be a frustratingly long wait for those that like to do a more truncated cold start and get in the air faster (who i suspect are in the majority), hard one to call but something to think about it. The wingman issues are seem to be dis-proportionally affecting you from what I've seen and heard. This is what is known to the campaign devs as the 'stop follow bug', where DCS seems to almost skip/stutter past a flag that will release the wingman from the follow command. It's not totally uncommon but it seems unusual that you saw it so much, especially with your system specs, we tend to see it on weaker systems when the CPU gets heavily loaded. ED says it's isolated the issue so fingers crossed that is correct and it disappears soon.

Lol well thanks...I think . Difficulty level is always a hard one to judge when it has to meet the abilities/wants of every player, that's why I put the immortal option in for FIWOS, no shame in using it IMO. Missions were thoroughly tested of course, difficulty was judged as appropriate by the testers who played it but I'm always happy to reflect on any additional feedback given. Just a pointer on the last mission, the SAMs that threaten the strikers can be found and taken out before they arrive so the mission can be less pressured if you have managed to do this. What you've described is the worst case scenario in a quite dynamic mission where things change depending on your choices/performance earlier on. But thanks for the continued support and I hope you enjoy LOWOS when it is complete.

Yeah that's right, Reflected has been pushing ED really hard on this one. We believe its an issue with multicore when the CPU gets heavily loaded and it can cause the game logic to skip a beat, in which case to can miss the command to stop the AI from following the player. Last I heard the issue has been isolated so can now hopefully be fixed.

Ok thanks, I'll check that out.

Thanks, I'll take a look. Might be the rare but annoying core issue that prevents the AI from stopping the follow task.

Thanks, glad you enjoyed! Hope you enjoy Cerberus North even more . Definitely plan to return to the A10 at some point. Nothing planned yet but it's definitely on my future plans.

You need to go to main power first on the battery switch, then open the radio menu and make sure you select the F10 menu option, not the F5 ATC option. This is a common mistake, the campaign uses the F10 custom menu for all comms, the default F5,F2 etc menus are not used. Hope that helps!

Just go to be careful about what you're hitting in the background, try and avoid the buildings/vehicles and hit just the troops. If troops are on buildings then they're fair game but surrounding buildings should be avoided.