winz

The same. This is the second mission in a row I cannot complete, because of some core DCS bug. Some months ago there was question-form about the decreasing interest in custom campaigns - this is the main reason for me. If I have limited gaming time, then dedicating 2.5h to something that I have past experience of being broken more often than functioning is hard, becasue it is not fun. Don't take me wrong, I know that this is something very much out your control, and you work very hard to maneuver around the issues. It's also frustrating for me, because I see the effort that went into this campaign, and it is trully great when it works. And I want more of these narrated campaigns... it is just hard for me to buy them, when I know how temperamental DCS core functionality is...

Same for me, I didn't do the AAR skip. But after Spartans drop their ordnance I don't get the CSAR call. Hats off to campaign creators for fighting this sisyphus battle with bugs ...

For me it happens when I manage to reach WP1 before Smoke takes-off. As it looks like the follow order is given at WP1, if smoke is still on deck, the command will not register. So if it it looks like you will reach WP1 before Smoke launches, take the scenic route to WP1

DCS World Theme Randomizer This is a small app that I wrote. It selects a random module theme, from installed modules, and then runs DCS, adding little bit of variety to the DCS 'menu experience' It also allows you to select which modules should be used for the random selection. The app can be downloaded from gitlab: https://gitlab.com/winzarten/dcsworldthemerandomizer/-/releases Instruction and Source Code is also available there https://gitlab.com/winzarten/dcsworldthemerandomizer

I've finished another lengthy, busy, mission without any issues. It really looks like clean-up solved it.

I was also able to complete a mission, after clearing the metashaders and fxo folders, without a crash.. so it could be quite possible fixed by that. Also thanks for the assist

I was in Harrier, but Tomcats where present in the mission. SP, Marianas Map.

I'm also having crashes with the latest beta patch, with similar stacktrace. Previously the game was rock-solid for me, no crashes for few months. First two flights with the new patch - both crashed. dcs.log-20230725-161339.zip dcs.log-20230725-155344.zip

I'm also struggled a little bit with mission 12. The way I feel it, playing cat and mouse with MANPADs is not really fun. Getting into their WEZ on purpose and hopping flares and maneuvering will work, is just something that imho doesn't work in a sim like DCS. If Davy was more pro-active in spotting those threats before they fire, then maybe. But if you have to react to a missile being fired on you, that means you messed up somewhere, and you're more-or-less rolling dices. Very quickly, I, the player, start to game the mission. Learning the threats, working around them, or even changing the mission load-out, and destroying them. Threats I would have no idea exists if I didn't play the mission two time before. This quickly takes the fun out of flying those missions. And TBH, I feel for the four man team on the ground, but no sane ROE would allow A-10s below a hard decks if manpads are expected to be in the area. I enjoy the campaign overall a lot, and is great to fly A-10 outside of the typical COIN missions.

I've completed that mission recently (like last week), and had no problem communicating with the convoy. The "only" thing that is broken is the in-sim communications on UHF and VHF-AM radio. Custom communication works.

I've tried to merge mustang changes with the latest OB state. I've managed to do it for some changes, but some are beyond my shader knowledge, so the result is a subset of the original changes. It should contain the atmospheric, cloud and dust changes. I'm also uplading another file that might be of use to someone, it is an extraction from the VR Shader Mods from Kegetys, and its purpose is to disable bloom, which can get annoying (atleast for me), especially during night missions. DisableBloom.zip Mustang Shader Edits.zip

Looks like I've found a workaround. Using the DCS ATC in addition to the scripted dialogs (manually dialing Nellis ATC, requesting startup-taxi-takeoff) fixes the issue. So..yeah.. not a mission error, but a change in AI taxi logic. But alteast I can continue in this amazing champaign

One the lates beta (2.7.9.18080), on Mission 13, I start the mission normaly, start-up, taxi at the given time, my wingman is following me as usuall. Everything looks fine until the moment I take-off. My wingman gets stuck on the the Rwy threshold, refusing to line-up, behaving like the runway was occupied. I tried to replay Mission 3, to see if it just a random mission behaviour, but the same thing happened there, the AI refused to takeoff. It looks like another issue with AI taxi and take-off behavior got introduced in the latest patch, rather in a single mission bug. But as It is the place I experienced it, I'm reporting it here. I'm attaching the screenshot of the stuck wingman

Yep, the mission is broken. Your wingman spawns at different location than is shown in mission planner and get blocked by a tanker truck. As is it the first AI to taxi the rest of AI waits until it moves beyond the conflicting taxiways... so he effectively blocks all AI. I was able to fix it by editing the starting possitions in the missions, but the file is too large to upload here. Even with the mission working I had to skip it, because (mission spoiler)

This looks like to be fixed in the last beta patch. I was able to replay the mission twice without any issues. :)