fixed for next update Mission 4 Report Bug

[Gunnar81]

Hey BD and others. I had a strange bug in mission 4, took off got all the prompts to engage mortar and truck position. Slammed a CBU right on it took everything out, made double sure there were no unit left alive and wingman says no joy he's engaging with GBU's. There is nothing to engage to he performed endless circles over the target and I had to quit the mission.

I am going to try it again soon to see if it was something on my end? But I have no mods and run in MT preview. I will post my results on my next attempt.

 

*Worked when I played again tonight. The only thing that may have caused an issue was calling no joy a couple times when I couldnt find the target my first go at it.*

Edited July 18, 2024 by Gunnar81

[Speedy_]

I've tried 3 different time, and every single time my wingman calls no joy.

It looks like even though we hit the trucks, the last truck gets destroyed only after whatever damage check is done script wise.

I had to replay the mission a 4th time and let my wingman do the initial run.

[wpsaturn]

Mission 4 Report Bug

After attack complete Mortar, can not Report to Morpheus.

Set Easy Comm OFF, Player and Wingman same bug.

I can't see any messege & voice.

Edited July 19, 2024 by wpsaturn

[CypherBlue]

Same issue here, if I drop on the Mortar site with a CBU, I destroy the site but wingman after a time calls no joy and he doesn't attack the other target just stays orbiting endlessly 

[baltic_dragon]

Thanks guys, it seems to affect some people while for others it works fine. I'll try to build in some additional safeguards to make sure the mission moves forward even if you don't kill everything. Will keep you posted. 

[Jakes]

I tested this one now. No issues here....mission ran flawlessly for me.
Only advice I can give here is that If you have ANY mod that is NOT purchased from the DCS Store, it will probably cause issues.
Make sure to remove any and all mods before flying campaigns. (Check out OVGME, I use it daily and it works well).
Also try disabling TacView under special options...can cause issues, usually performance, but that can lead to bugs if your cores are overloaded/too busy and it misses a trigger point due to that.
If removing all mods still does not fix the issue, take the following steps:
1)Delete fxo and metashaders folders in you saved games. Can get gummed up with old files.
2) Rename you DCS Saved Games folder, run DCS and let it create a new one. Then just copy the Config folder from the old to the new so you don't lose your bindings at least. Copy the logbook.lua from the old MissionEditor folder into the new so that you can keep your campaign and pilot progress.
3) Do a full deep repair of DCS to clear up any unwanted stuff in your main game folder.

[Viking 1-1]

I had similar issues.

I managed to destroy the mortar site, then the technicals started moving. We commenced a attack but from there on the mission is stuck. Wingman calls "rifle" but does never tell if he shacked or not. From there on he is just circling around and nothing ever happens.

I circled for about 15 minutes, then quit the mission

[Viking 1-1]

Exactly same issue as already posted in the "other M4 thread"

[Milker]

Hi!

Just a quick note. I reproduced this feature when i changed CBU spin RPM from 1000 to 1500 and because of the dispersion the two trucks were burning and only after a minute or two they got "killed"... maybe this was the problem! Pointing the TGP between the two trucks might help!

Cheers

[asut]

Same issue here, and in Mission 5 too!

18 hours ago, Viking 1-1 said:

I had similar issues.

I managed to destroy the mortar site, then the technicals started moving. We commenced a attack but from there on the mission is stuck. Wingman calls "rifle" but does never tell if he shacked or not. From there on he is just circling around and nothing ever happens.

I circled for about 15 minutes, then quit the mission

 

[baltic_dragon]

I know, but neither me nor my testers can reproduce this at this stage... I have no idea how to fix this as it works fine for most people. I'll think about it some more and also merge the threads. 

[asut]

It was my fault, I had easy communication turned on in the dcs settings. I've now completed the fourth mission.

[jeffmaysefaith79]

It seems after an update alot of peoples DCS defaulted to easy comms on

 

[CH4Pz]

On 7/29/2024 at 12:31 AM, jeffmaysefaith79 said:

It seems after an update alot of peoples DCS defaulted to easy comms on

 

Just had the same issue, came here to report it, but then after reading, i restarted the sim and realized i too had easy comms enabled !! Yet to retest, but i think this may be the culprit @baltic_dragon , as Jeff mentioned, maybe the update (or cuz of launcher) it has been enabled.

[baltic_dragon]

I am almost certain this is because of the launcher. Might talk to ED about this!

[CH4Pz]

So i just tried again, no joy. First when i got into dcs, i checked easy comm., which had re-enabled itself (after i disabled it last night), so obviously disabled that again (along with the launcher), but when i hit the truck still wasn't recognized, even though everyone was dead, got no joy call, wingman froze etc, so once i quit, i check easy comms again, and was still disabled, so not sure whats happening now.

I Then tried again, but let 2 hit the mortars, which progressed the mission, but then i only scored 65 points at the end, as i missed the technical an wasnt cleared to hit anything else, i also didnt receive the end of mission briefing, so not sure if something went wrong?   ...so perhaps the workaround for now is get 2 to hit the mortars.

 

[Furiz]

Just happened to me too, used CBU to blew up the mortars and trucks, destroyed them but my wingman calls no joy and circles endlessly.

[CH4Pz]

16 hours ago, Furiz said:

Just happened to me too, used CBU to blew up the mortars and trucks, destroyed them but my wingman calls no joy and circles endlessly.

Did you check easy comms were off? it wasnt a fix for me, but several did get through by disabling it. Just be aware, the launcher seems to re-enable it every launch (ive now disabled the launcher altogether personally)

[Furiz]

1 hour ago, CH4Pz said:

Did you check easy comms were off? it wasnt a fix for me, but several did get through by disabling it. Just be aware, the launcher seems to re-enable it every launch (ive now disabled the launcher altogether personally)

After I wrote my post I noticed easy comms mentioned in the thread, so I went to check it out and it was enabled. I never have it enabled so I didn't even think of that, mst be that the game enabled it somehow with latest updates. Anyways gonna try the mission again later.

Thanks

[baltic_dragon]

@Furiz let us know how it worked. I think that the launcher forces Easy Comms everytime it is used. 

[Choffix]

Hey guys, I have the same issue. Attacked the target, both trucks blew up roughly 30 seconds after CBU impact, mortars and infantry are dead as can be, but a bit later wingman calls no joy, attempts to attack but doesn't release his GBUs.

Easy comms are off, checked it right after the mission.

Edited August 15, 2024 by Choffix

[baltic_dragon]

I think I know what may be happening there - I'll try to add some more time between the attack and detecting if the target was destroyed. Wingman still sees the burning truck thinking it is alive, but then when he attempts to engage it, the truck blows up so he cannot attack - which causes the mission to stall. Thanks for the report!

[Gilligan]

any headway on this? I am also experiencing this mission stall.

[baltic_dragon]

I'll try to build in a safeguard that will make the mission progress even if one of the targets is destroyed. This must be linked to the damage model somehow, and it happens to some people while things work OK for others. Sorry for the trouble guys.

[Gilligan]

Appreciate your diligence. I was able to get passed this last night - I took two CBU-103's and dumped both over the mortar site. Both CBU's hit the target area and the second CBU killed both trucks after the first damaged them. This seems to have worked to ensure that the trucks were dead before the wingman BDA, and the mission progressed.