Pyrocumulous

Page 428 (July 2023 version): image shows BI 0.020 on the CMDS program, but diagram shows 0.2 seconds for burst interval

I've only completed the first four missions, but so far, by the time the rest of my flight gets done with the tanker, it's already push time. For some reason the wingman takes forever to take on fuel, despite only needing a couple thousand pounds (internal, no external tanks). I timed fuel transfer time on Mission 4 and it took 7.5 minutes for Colt 1-2 from contact to disconnect, 1.5 minutes for Colt 1-3, 6.5 minutes for Colt 1-4 by which time we were already past push time so I do not have time to top off my jet. By comparison, testing with a mission where all four jets start with 5000 pounds of internal fuel and no external tanks, each takes about 45-50 seconds from contact to disconnect (4.5 minutes for all three AI jets to fuel and disconnect). I'm giving flight the Hit the Tanker order pretty quickly after departing Nellis, and they aren't wasting any time getting to the Shell tanker or hooking up, just seems to take forever to fill once there. I'm a pretty incompetent with the F16 doing AAR, but even I can bobble around and get a couple thousand pounds in a couple of minutes. What's going wrong here?

M02 is bogging down very hard for me for about a minute at the beginning with single-digit FPS, but it recovers and plays fine 60-120fps, depending on all the usual factors. This is with 7950X3D with 64gb RAM and a RTX 4090. I didn't notice any serious performance issues on the next several missions. Version is DCS World 2.9.8.1214.1 (MT) in late 2024.

I was able to get ATC to work by manually setting the frequencies in mission editor (Sainte Croix ATC = 118.75).

Beautiful. Just need actual constellation locations now... that should be easy, right?

Ooof! That was a whole lot of unnecessary stress trying to limp home a non-broken aircraft

Odd. The crew chief says "Sir, I found crack on the manifold pressure gauge line. I patched it up, but keep an eye on it. I'll have it replaced tonight." Then, both times I flew, at the point in the mission while over Paris when Cobweb and Caboose split up, manifold pressure drops to about 15-20 depending on altitude.

Is there supposed to be some sort of F10 radio interaction when If there is, it didn't appear as an option in the two times that I flew Mission 8.

A niche issue, but if you spend a lot of time in DCS World virtual reality, the screen mirroring could prove to be a problem for burn-in on a primary OLED monitor. There are a variety of ways to solve this, such as manually turning down the brightness on the primary monitor. Just wanted to share the solution that I adopted in case it was useful to anyone else: Use Multiscreen Blank to dim all monitors (doesn't affect VR) using command line triggered by Voice Attack or a similar solution. One has to dim, rather than fully toggle the monitors off or else focus is lost on DCS World when the mouse is clicked in VR. However, 99% dim is essentially fully turning a screen off without the focus issue. The command to run would be something like: C:\Program Files\Nookkin\MultiscreenBlank2\MultiscreenBlank2.exe /toggledim99 all then repeat that command to undim the monitors. Example Voice Attack commands attached. VR_Blank_Monitor-VoiceAttack_Profile.vap

Thanks for this @gonvise. Seems to be working alright for me with OpenXR Toolkit and PimaxXR with my Pimax Crystal as long as I have it set to Preset, but the center of my gaze is rendering very low resolution at 1x resolution. Eye tracking is definitely working. Ideas?

Looks like the crowd got a little wild and tried to park a bus in a hanger. Thanks for the great campaign, a fun twist for a jet that hasn't gotten much attention.

I used AIM-9s for one of the Mig-21s (after the flares were expended) and the IL-76, but had to hit the IL with guns to finish it off. With just one remaining escort, I headed north at full speed, keeping it just under mach 1 for stability. Once I got down to the surface, the remaining escort crashed into terrain. I repeated the mission a second time, and exactly the same thing occurred: it seems that the AI Mig-21s can not stay stable in a supersonic NOE chase in the current version. (F86 / DCS 2.9.5.55918 MT)

F86 Mission 11 (or 17, depending on counting) works great, but for some reason DCS 2.9.5.55918 MT

Here is a kneeboard with the IAS in knots for those flying Mission 10 in the F86. Drop it in \Saved Games\DCS\Kneeboard\F-86F Sabre and then remove it after the mission is complete. You can scale it way down and reposition it while remaining legible, ideal for VR.

The SU-25s in this mission (M6 / F86) seem to have an issue with running into the terrain. In three attempts I can barely, if it all, squeeze off a burst from the cannons before all three run into the terrain. I suspect this is due to the AI evasion logic changing. Not a problem, as it helps inflate my ego to scramble and destroy three SU-25s within a minute of the merge, but I'm really not particularly skilled Tacview-20240622-185640-DCS-F86 MR campaign 6.zip.acmi

Just flew Mission 4 on DCS 2.9.5.55918, and I actually got the

is this campaign still unplayable or has this been resolved? I don't see any Charnwood entries in the changelog, but perhaps an update to Normandy 2 improved the situation?

In the mission 10 (and 12) briefing (in game and in doc) it says: but briefing materials and mission loadout have M64 bombs rather than drop tanks. DCS 2.9.4.53990

In the mission 9 briefing (in game and in doc) it says: but it appears that this was actually intended for mission 5. DCS 2.9.4.53990

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.