unable to reproduce Stop following command broken

[algherghezghez]

I still have his bug, even with the latest release, smoke at waypoint 4 does not detach to proceed to his task but stays in formation. No mods installed.

I am attaching the track.

Thank you

raven one mission 2 no cut away.trk

[baltic_dragon]

Hi, 

I am unable to replicate this bug, even though I have seen it reported several times. For me it always works, as it does for 3 of my beta testers that checked the mission. It may be linked with the DCS bug about the stop flag not working for some people (I know @Reflected was able to reproduce it) and it has been reported to ED, but the fix is out of our hands; trigger-wise everything is as it should in the mission and, as I say, for me it works every time... 

One other thing that helped some people - to uninstall any unofficial 3rd party mods and run a full repair and then try again. 

[Reflected]

8 hours ago, baltic_dragon said:

Hi, 

I am unable to replicate this bug, even though I have seen it reported several times. For me it always works, as it does for 3 of my beta testers that checked the mission. It may be linked with the DCS bug about the stop flag not working for some people (I know @Reflected was able to reproduce it) and it has been reported to ED, but the fix is out of our hands; trigger-wise everything is as it should in the mission and, as I say, for me it works every time... 

One other thing that helped some people - to uninstall any unofficial 3rd party mods and run a full repair and then try again. 

One more thing: apparently it’s a multithread bug. It should work in ST. 

[baltic_dragon]

Yes, I can confirm - we just tested it with somebody who had this problem but ran the game in MT. In ST the bug disappeared. 

[algherghezghez]

I did a full repair, I have no mods installed abd tried again in ST, the bug for me is still present both in this mission and in ottoman Courier mission 2. I don't know what to try anymore honestly.

[algherghezghez]

Is the infamous stop following comand not working bug being worked on or at least isolated?

This bug is "famous" because some of us are unable to progress in some campaigns (Mainly BD ones) and it only affects a small pool of users appaently.

I have no mods, tried both in ST and MT, and don't know what to do anymore. Do we have any info on this?

[algherghezghez]

I’ve done some more digging, I have this problem mainly in Baltic dragon’s campaigns, and what appears to be not working for me is the ai task push:switch waypoint function 

[baltic_dragon]

This unfortunately is not related to the campaign and has been reported across different campaigns. Do you have lower-end specs of your PC? As these issues are happening much more often with weaker machines. ED is aware and I hope they can find the solution. I tried to solve this on my end with people reporting this bug (I cannot reproduce it) but nothing seems to work, so this is completely out of my hands. This is a problem with the game not registering stop command for a follow task, and thus not commencing the next one (switching waypoint in this case). 

[algherghezghez]

Hopefully they'll fix it.

I don't know if it can be of any help but I noticed that I don't always have this problem. Let me explain better: For example in mission 2 smoke always stops following me and refuels correctly, but never stops following me to take the cutaway (maybe it's a different command). I have the same problem with ottoman courier mission 2, where the wingman doesn't detach to drop his bombs. I could open that mission in mission editor and the problem seems to be the ai task push:switch waypoint function not the stop following command. 

I wouldn't say to have a low end pc, i run everything at max in 4k at 60fps, maybe I am capping the cpu though.

Still thanks for your time, I hope I'll have a chance to play your campaign properly again because they rock.

[baltic_dragon]

Thanks! This is one of those mysterious things in DCS, because the cut away for Smoke before refuel is exactly the same trigger-wise as the one after. For some people it always works (including me), for others it doesn't - and here this is mostly in MT and mostly on lower-end machines but not always. Sometimes third party unofficial mods are to be blamed as well, we've seen that removing them helps (not sure If you have any installed). My advice is to just skip M02 and move on to see how it goes. Thanks!

[algherghezghez]

No no mods. 

I will do what you suggest and skip mission 2. Just an advice though: I have both raven one and raven one dominant fury. Read the first book and almost finished raven one once a few years ago. Would you suggest waiting for your update to raven one dominant fury and play that before replaying raven one or the opposite?

Thanks!

[baltic_dragon]

Chronologically, RO:DF is before Raven One, but I think I would still first fly Raven One after reading the book, and only then move to RO:DF.

[Highwayman-Ed]

On 11/30/2023 at 7:48 PM, algherghezghez said:

No no mods. 

I will do what you suggest and skip mission 2. Just an advice though: I have both raven one and raven one dominant fury. Read the first book and almost finished raven one once a few years ago. Would you suggest waiting for your update to raven one dominant fury and play that before replaying raven one or the opposite?

Thanks!

Something else to check here, we (DCS Players) often don't class VAICOM as a mod, but it does impact how DCS functions to some extent. During some recent testing, we found that players who used the OLD official version of VAICOM in the past, even though they are not using the program any longer were able to resolve their issues by removing this old version of VAICOM, backing up, and then removing their scripts folder in their DCS Saved Games folder, then performing a DCS repair. The new community version of VAICOM does not seem to be causing issues at this point, but I know the migration from the OLD version to the COMMUNITY version has caused issues for some players in the past.

 

Not sure if this applies for you, but it's worth checking!

[Yoda967]

@Reflected has talked about this because it's also happening in his campaigns, as well, so maybe he can chime in with the symptoms he's aware of.

I've noticed it in my mission development, too. What I'm seeing is that once an AI aircraft begins a follow task, it will continue until the aircraft being followed lands or is destroyed. DCS appears to be ignoring the Last Waypoint setting within the Follow command, and it will also not respond to a triggered Switch Waypoint task. 

Switch Waypoint appears to be working prior to any Follow command.

I'll add a track file later today.

[Reflected]

It's an MT thing, the way MT is set up, DCS can miss flags and triggers. It's a massive issue, totally game breaking, and it's been in game for the past 1 year. Keep bombarding ED with track files and hope for the best.

[NineLine]

Does anyone have any tracks of this?

[algherghezghez]

1 hour ago, NineLine said:

Does anyone have any tracks of this?

I provided one here.

 

[Yoda967]

Thanks, algherghezghez and Reflected. I forgot that it was an MT thing and spent the afternoon racking my brain because I couldn't get the mission to fail. Naturally, I wasn't testing in MT (trying to cut a corner).

[NineLine]

Thanks I will take a look very soon.

[algherghezghez]

Any news?

[Lt.Salty]

I'm having the same problem, but it for me, it is not limited to MT but also occurs in ST. Attached is a MT track of Mission 7 of Baltics Raven One campaign where I encountered it numerous times. Furthermore, I also encountered it in other Missions, but to provide a track, this will hopefully do. I would have attached an ST track as well but the 50mb limit prohibits that. 

R1M7 StopFlag Bug MT Version.trk

Upload problem solved.

R1M7 StopFlag Bug ST Version.trk

[algherghezghez]

48 minutes ago, Lt.Salty said:

I'm having the same problem, but it for me, it is not limited to MT but also occurs in ST. Attached is a MT track of Mission 7 of Baltics Raven One campaign where I encountered it numerous times. Furthermore, I also encountered it in other Missions, but to provide a track, this will hopefully do. I would have attached an ST track as well but the 50mb limit prohibits that. 

R1M7 StopFlag Bug MT Version.trk 32.89 MB · 0 downloads

Upload problem solved.

R1M7 StopFlag Bug ST Version.trk 31.32 MB · 0 downloads

I also have it in both mt and st, tried everything without success 

[Lt.Salty]

Are there any news? I recently even upgraded my ram to 64gb 4000mhz in the hope that this would somehow eliminate that bug for me, but no such luck. 

If more tracks are needed I can provide those, also from different missions. 

[NineLine]

I am unable to reproduce using a simple mission, If you can reproduce in a simple mission send me a track. Otherwise @baltic_dragon maybe need to dig into it. Thanks. 

[Lt.Salty]

This is a very strange bug. I just watched the replay of my MT track i posted above, since you couldn't replicate the Bug. Behold, in that replay somehow everything works for me as well. The triggers fire and my wingman engages the target twice after she drops smoke, which is strange because in game it definitely never worked.

But again when I play the mission, instead of just watching the track file, there she just drops smoke and then returns to follow me indefinitely. I recorded an in-flight video to highlight the bug for you and saved the new corresponding track file of that session as well as a Tacview file. I also rewatched the new track file four times and there the triggers worked once and failed the other three times.

Youtube Video of the Bug - the interesting part starts at 17:40. I hope that's enough for documentation purposes.

R1M7 StopFlag Bug MT Version 11.03.24.trk Tacview-20240311-180228-DCS-R1 M07.zip.acmi

 

Edited March 16, 2024 by Lt.Salty