icecold951

AI wingmen, when told to execute mission objectives, return to WP 1 first, regardless of where the objectives are. This makes wingmen pretty useless unless you release them by WP 1. It did not do this before the update. If you released a wingman, he went for the first objective marked WP.

It may be a one off error, or something that is triggered by a condition within the scenario, but not a trigger. The mission before and after doesn't do this. The two F14s take off fine. But the parked aircraft, including AI wingman just sit there for several minutes, not taxiing for takeoff. Eventually they take off. There are no triggers that should do this, particularly regarding a wingman. 1.trk

Mission breaking. AI wingmen now return to WP 1, starting the whole cycle of WPs from 1. Now any mission in which you have an order "Wingman, execute mission and rejoin" is broken by this bug. They will always return to WP 1. I even tried creating a change WP trigger action and it didn't fix it. How did this not get seen in beta? Specifically WP1 was always Push, 2, ingress, with the designated target via WP2. And though WP1 has no objective, they returned to WP 1. 1.miz

Could you maybe make the helos bullet proof for a short bit when they open fire? The ground fire is way to accurate and then one of the helos aborts due to damage. The other just keeps orbiting the waypoint waiting for him. The only solution to to prekill the target and that breaks the intent of the mission.

Yeah. Why couldn't they give us some moon light to see them by? I am aiming at the labels set to minimum on that one. Such a simple fix.

Unfortunately I get it twice at the same spot, heading in to intercept the helos. I may just skip it this time. It worked fine pre DCS update. No mods installed.

What he said. After radio check in last night I went ahead and taxied. Then blade started.

Okay...on 3rd attempt went fine. I don't know why it had problems before. Maybe beaming the plane so didn't pick up on radar, though I am sure I was within visual range a couple times. Was driving me nuts. Was fun with Knight. Go away! You're crazy. "I'll shoot you"

Is there something wrong with the AWACS guidance to Marauder? I've used Rock many times, including the first intercept of this mission. But fallowing him to find Marauder, nothing is there. In my first attempt I stumbled on him one, by accident, just before it was to late and mission failure.

Yes. I'm in knight on pri. I watched a YouTube video, and I guess an F10 menu item is supposed to appear. It never did in 3 tries. My guess is multiple aspects for the trigger and one of them isn't being met. But he is right there 0.1nm off my wing and nothing. I'm circling wp1, and even extend and return right to it. I even tested trying to ensure I arrived first. Oh, I did get the initial check in. With me saying I'll do 360 for blade. But after that, nothing.

I got to agree it is mission specific. No other mission I have seen does this, and it appears very predictable. It behaves like an unhandled exception. I know nothing about mission 6, as for me that one refused to advance beyond circling to let blade rejoin. I ended up skipping it after 3 tries. But theory about cause that stands out in 8. Red is smoking. Planes eventually despawn after parking. If the smoking trigger is still active at that point, it may trigger an unhandled exception. It can be tested by triggering a smoking plane that immediately lands. I don't know how to trigger smoking, or I could test it myself.

Get to waypoint one and lazy circle to let Blade rejoin. He gets to 0.1nm, but no option to report in. We are joined up. Twice now this has happened. Mission won't continue

Unfortunately I can't help you with that yet, I think I am starting six shortly. FYI, you posted into my comment, not a general post of your own. So the odds of this being seen are low. I will say I have seen other reports of mission crashes.

As far as older missions, not all appear to be affected. Possibly ones created further back for some reason get affected. It could even be related to certain maps. DS20 is affected by the bug, with so far no fixing it. Meanwhile DB19 remains unaffected. Both were created pre update, though DS20 is six months older at least. DS20.miz DB19.miz

This may get merged into another section, but creating it to be visible to the devs. Through testing, I have determined that the crazy afterburner climbs to 10k are related to the weather preset system. It is most obvious in missions made post public update. Any mission with rain appears to trigger the bug. Take the rain away, and the bug goes away. Missions pre update, with limited testing so far, seem affected no matter what. But probably the cause is related. Uploading the relevant mission and tracks. Also including a youtube video of my experiment process in this. Forgive the video quality, as I am not a youtube content creator and my software doesn't record DCS well. It still shows the relevant information. MW03.miz MW03 Raining.miz 03 working.trk 03 10k feet climb AB.trk

My assessment appears correct. Creating a post for the devs in the Bug section. Not a Raven One DF Bug. Cause is weather related. Probably will get merged into this one. But wish it to be fully visible and noticed, including tracks, miz files, and a youtube video of the process.

My assessment appears correct. Creating a post for the devs. Probably will get merged into this one. But wish it to be fully visible and noticed, including tracks, miz files, and a youtube video of the process.

I've already suggested he do so and posted a link to that discussion on YouTube. Shortly I go home and can directly test my suspensions. I at least seem to have it narrowed down to a working mission as the basis for one bugged. That narrows the search for a cause.

I've seen this pre update in my last campaign I had made. But in that case, it was during takeoff and settling in on initial leg on a carefully planned route. I have not seen it yet, but no currently made mission involves a strike flight returning. Have you tested an older mission to see if you get the same results? I'll try and look at this myself after I test my current afterburner crazy bug. I may have that answer today.

Flying KENNY from a YouTube channel is reporting he saw exactly this himself in tacview involving DF M05, and possibly other missions. He may directly report it himself here. Video involving the chat. Video not related to the event, just where we discussed it

Flying KENNY from a YouTube channel is reporting he saw exactly this himself in tacview involving DF M05, and possibly other missions. He may directly report it himself here. Video involving the chat. Video not related to the event, just where we discussed it

If anyone is paying attention, I may have an answer to this. In a new post in bugs I ran into this bug in a new mission. The file, MW04 was a modified mission of the previous. Suddenly afterburner crazy climb. I have to examine it, but I am currently working on the theory it may be related to weather preset. It is the number 1 change. And it just so happens that like DF Mission 01, it is storming. Which is why I am mentioning it here. If anyone can possibly check their own and report AI behavior in M01 and others, observe weather patterns between missions. I don't believe it is simple storm behavior causes it. As another mission affected has no weather at all. Assuming M03 of mine still works right, but 4 is broken, I may have something to disect for a possible cause. And the weather stands out rather nicely.

I just created a new post involving it happening to a new created mission. Tomorrow I plan to closely examine the previous mission that I modified to do mission 04, ensure it wasn't in that one. If not, I'll examine the changes made, starting with weather. If I can get someone with Raven One DF to examine the first mission and see if it happens, that will answer a lot. So far no one has responded.

This is a track of my previously reported afterburner climbs to 10k feet. In this track and mission file, the flight leader, Diamond 1-1 Raider, is an AI flight lead. He burns to 10, before returning to the assigned WP1 altitude of 6k. This is a completely new mission post the update of DCS. MW04.miz 2.trk

I'd recommend finishing within the update. If the update breaks them like it did mine, better before all that work. I got four campaigns possibly ruined. As for the takeoff, I usually have the initial leg slow to help trailing planes catch up. In any event, the leader never climbs like that. And it certainly didn't when I made it. ED really needs to convince it to update the missions, after a DCS update. And then I found the bug existing within a paid for campaign Raven One DF. I'm in their forum page desperately trying to get someone to see if they get the same results on their own, and tell me one way or another. No one else so far seems to report it. But unless you pay attention, you may not notice it. But two completely different computers with fresh DCS installs show this. I've even posted videos of that mission.