Pyrocumulous

No worries there, I feel the collective Creator's pain on that front. Hope to see Storm Front in a surprise drop someday soon! Do you think ED might be open to a third-party campaign testing and verification service as an alternative pathway given their capacity-limits lately?

@CHPL the update apparently resolved the issue, Mission 1 now proceeds perfectly without use of the F10 menu. Thank you! (DCS World 2.9.4.53707 MT)

@CHPL I'm traveling now, but I'll update, fly, and report when I return next week.

Thanks @CHPL. Tried it again, with the same result. This time I used the F10 menu when WOLF 1 hovers at waypoint 2: "Follow WULF 1 and give cover" and received the reply "Sorry, Frank, we have to wait for WOLF-1 – close the Throttle to idle, it saves fuel and its more relaxing." I tried "ABOARD MISSION AND PROCEED TO MISSION 2" and that just ends the mission. There were no other F10 options besides tuning the radio. No mods, in fact this is a fresh Windows and DCS install due to some issues with a previous Pimax install. No worries, I'll move onto the next mission tomorrow, appreciate your work.

Mission 1 worked for me until the first power station (Waypoint 2) inspection. I stayed on station for 1 hour 17 minutes, the first half of which Wolf 1 just hovered in HIGE, then landed and shut down for inspection. I refueled at Batumi, then returned to Waypoint 2 to check on Wolf 1, by which time he had slid all the way to the water's edge. Tried landing, etc, to trigger the next stage, but no luck. Proceeded to Waypoint 3, circled but no trigger, on to Waypoint 4 and the story began to proceed again. Wolf 1 never showed up to trigger a departure, so I eventually departed Waypoint 4, went back to check on him again at Waypoint 2. Still there. Went onto land at Waypoint 5, then back to Batumi without any radio traffic since departing 4. Tacview attached. Tacview-20240407-220038-DCS-WORLDS APART Mission 1.zip.acmi

This isn't an installation issue but seems like the best place to mention it. The instructions when one purchases additional modules still has the pre-unified versions language: Bought products can be downloaded and installed through the DCS World Module Manager (FAQ). If you do not have DCS World installed, you can download the DCS World web-installer by clicking this link. If the product description does not have information about which DCS World version you should install, you need to have the "Open Beta" or the "Stable" version of DCS World installed on your PC. For any questions please read the FAQ.

I've flown Mission 2 three times (all with UH-1H), each time get all the way back to the initial point. I am promised a decontamination shower, I land and nothing happens. I relocated several times to try to get a mission complete trigger, but nothing happens. When I exit the mission, I have 50 points and a draw. DCS 2.9.3.51704

I concur with @escanner, this was a really well done campaign. The diversity of the missions, and the intimacy of the helicopters with the landscape, really felt immersive. So many campaigns it's the same mission ten times. This was not that. At all. Thank you!

I've had Normandy since it was released, but for some reason DCS World (2.9.2.49940 Open Beta MT) is today notifying me that Normandy 2 is available to install. When I click okay and it proceeds with the usual exit and install, it results in an "Unknown module NORMANDY_terrain_new" error. Tested it by flying through Paris at 100 feet, and it's definitely Normandy 2, so not sure what is going on. Log says:

which arguments in SmokeMarker.lua should be edited to reduce volume and/or increase translucence on smoke markers?

would you mind reposting a link to this? Trying to figure out the smokemarker.lua so that it doesn't obscure landing zones completely.

is there a way to adjust the density of marker smoke used to identify LZs? I tried the "chimney smoke" setting, but that has no effect. Just flew Mission 01, and the smoke eliminates visibility of much of the LZ, in fact all of the flat part of Berlin. Totally not important comment on Mission 01 Resupply, Mac mentions that this is the start of the wet season, but November is actually the end of the wet season in the Marianas.

Not sure why, but I keep failing this mission (5x times now) immediately when I eliminate the final vehicle in the northern convoy. The tasking said that "they must not reach the town or they may take hostages," and then the mission failure message is "Now we're going to have hostages!" This occurs even if you eliminate the eastern convoy (which is tasked to Uzi) before attacking the northern convoy. Always when the last northern vehicle is destroyed. DCS 2.9.2.49940 Open Beta un-15-good_evening3.trk

Rotorwash should be the least of your concerns if you lose the main rotor... but nonetheless, just pointing out that it does continue to appear in DCS. See track and photo below. I'm not positive, but I think there is still some lift being generated (in DCS) after the rotor is knocked off, or at least the helicopter doesn't feel like it is accelerating toward earth as quickly as I would expect if the main rotor is lost. Example is UH-1H, I have not tested others. DCS 2.9.2.49940 Open Beta rotorwash.trk

Attaching instructions on replacement of button 15 that Thrustmaster sent me under warranty. Hopefully this helps someone else. The other part that they sent me it was a "good luck" we have no instructions for that one... ugh. 5090099_WarthogThrottle_ExchangeREDButton.pdf

Hardware list and photos of mine. The Airtac base is ideal for this purpose, but be aware that it took 52 days to arrive at my USA home from China, so plan ahead if you go this route. I haven't added thread locker compound yet, but that's probably a good idea on the top joint. Parts list: Damper, labeled as Matris MB2901x, but it's not a real Matris product. Available for around $48 on Amazon by several third-party sellers. Airtac F-MF25SDB pneumatic air cylinder mounting base, available for around $8 shipped on Aliexpress by the Airtac Pneumatic Store (2) 1/4" x 1/2" bolts (2) 1/4" nuts (4) 1/4 washers M5 x 60mm machine screw (50mm will barely clear if paired with 3/16" nylon spacer) #10 nylon spacer 1/2" length, 1/2" OD #10 aluminum sleeve 1/2" length, 5/16" OD M5 nut (4) M5 washers

I have no knowledge of how any actual TGP behaves. If it has an independent geolocation system that includes X.Y, and Z-axes, and it was able to pass this information back to the HUD, then I would speculate that this would be the correct and expected behavior.

I've had this occur several times in combat: EGI fails and yet the TGP is still able to point the way home and I'll continue to get a diamond on the HUD showing the SPI. See attached track and MIZ as example. After failure of EGI (and most other systems), I put in a flat spin, get as lost as possible, then select the nearest divert airfield on the CDU and the TGP directs me in. DCS 2.9.2.49940 Open Beta MT a10c-egi-fail.trk A10C-egi-fail.miz

I think this is the same issue that I'm seeing in other aircraft when ATC communication or Ground Crew communication interrupts work on the other order; definitely not limited to the AV-8B.

Right, it would never realistically occur like this, but in Operation Agile Spear campaign there is a mission where the CAP is apparently too busy with another priority meanwhile there's like 10 Tu-95 and An-26 aircraft loitering around the airbase.

This could be correct behavior, but it's not clear to me. The DCS manual says "When the MWS has power, it [CMSC] will display ACTIVE and with no power it will display OFF." When the CMSP is set to STBY and the MWS switch is set to ON, the CMSC will display ACTIVE despite being in standby and not being functional. Do we know if CMSC displays OFF or ACTIVE when in standby mode in the real aircraft? Tested in DCS 2.9.2.49940 Open Beta, but this is not new behavior. a10c-mws-active.trk A10C-mws-active.miz

If you issue the Ground Crew a task (e.g. rearm / refuel) and while awaiting a response, you call ATC (e.g. permission to start engine), Ground Crew will no longer do anything and/or ATC will no longer talk to you. Potentially this leaves you stuck in chocks. This carries over to other airbases, so if you lose ATC/Ground Crew communication at airbase 1 and you then you return to airbase 2 to rearm/refuel, you will not be able to do so. This can occur with either ATC or Ground Crew communication in either order. It does not happen if the Ground Crew is simply working on the task, for example is in the middle of refueling when you call ATC. Test mission and a sample track attached. I have noticed similar communication stopping in the middle of missions, that appears to be related to interrupted communication with JTAC or AWACS, but there is always so much going on that it is impossible to determine the cause. DCS 2.9.2.49940 Open Beta A10C-awol-groundcrew.miz ground_crew-atc-awol3.trk

The FXD WNGSPN (in the AAS submenu) maximum is apparently 99 feet. Is there any aerial gunning tricks when the wingspan is bigger (e.g. TU-95) than the funnel can hold? Set it for the distance between engines? fuselage width? I tried setting it for 84 feet, and using the outer engines as funnel-guides, and results were pretty poor. Probably a reflection on me as an aerial gunner, though.

Mission 3 frequencies do not match, and not clear which ones are correct: Briefing: Colt 305mhz Kneeboard page 2 (1Briefing 2png_Page1.png) : Hammer 30.00mhz Mace 40.00mhz Kneeboard page 3 (2M3_Mission Data Cards1 NEWpng_Page1.png) : Hammer 32.50mhz Mace 30.10mhz Kneeboard page 4 (2M3_Mission Data Cards2 NEWpng_Page1.png) : Hammer 30.10mhz Mace 32.50mhz Colt 315mhz note that there is no frequency assigned to JTAC on kneeboards or in briefing QNH in briefing is 29.53 but kneeboard says 29.92. Kneeboard page 3 indicates that arrival airbase is Senaki, but page 4 and map indicates Kobuleti. DCS 2.9.2.49940 Open Beta

I tried both Kutaisi and Senaki again in a variety of locations, without any response from the ground crew, so I rearmed and refueled at Kobuleti three times. I believe I destroyed all armor southwest of the bridges, and dropped a few extra CBUs at the bridges for good measure, for a total of 106 vehicles destroyed. Still scored 90, so thinking maybe the score is set upon the first landing at Kobuleti? Or I may have missed one. Or the wingman needs to survive.