Pyrocumulous

Neither ICLS nor Link 4 are enabled in the final Offensive Counter Attack mission of the Hornet's built-in campaign Taskforce Challenger. The problem appears to be a pair of "Fire at Point" tasks in the advanced waypoint actions for CVN-74 John C Stennis. When I move these below the Activate ICLS, Activate Link 4, and Activate ALCS, all works as briefed.

Eight JSAWs or JDAMs fired in ripple from max range and there shouldn't be any hardly any helicopters left, you just got to beat feet back to the carrier. Wingman never seems to make it though, even if you load him with JSAWs as well. I think maybe load up the wingman for CAP, and you take the AG weapons. Otherwise, you only have 2 sidewinders and an ARAAM so you can only reasonably fight off the first pair of MiGs. Problem for me is that the carrier doesn't have the ILS turned on, which wouldn't be a problem for a decent naval pilot, but that's not me.

I concur, this was a most excellent campaign! I was concerned after reading all the complains of the Sabre module being "abandonware," but each Hunters mission ran perfectly. It's great to see older campaigns continuing to see love and attention well after they have been released. I especially enjoyed the numerous surprises that got thrown my way; and not just the expected MiG ambush either. It really is a shame that Korea has been mostly ignored in the DCS world, the topography of this map makes it so much more interesting to fly than the Channel. The Sabre creates some interesting problems for the pilot, it's a go-fast-in-straight lines kind of plane and has pretty rudimentary weapons (dumb bombs, rockets, and practically dumb A/A missiles). Fortunately the enemy MiGs have very similar capabilities, so the encounters in Hunters can be pretty challenging. Not a campaign issue, but I do wish the AI wingmen were programmed such that we could better take advantage of them in combat; any dogfight quickly becomes a furball with every pilot on their own. The only disappointment for me was that the mission that was hinted at from the beginning, and I expected to be the most challenging, was actually the easiest of the entire campaign.

I am actually looking for the templates for F86's pylons and tanks template, which do not appear to have been officially released.

Are these PSD files still available somewhere?

That sounds correct, the others seem to match the F10, but time consuming to fly by each NDB to verify. Anyway, thanks for the campaign.

Is there a list or map of NDB frequencies in the briefing docs? Can't seem to locate one, but I may be missing something obvious. For example the NDB for K-55 / Batumi is 430khz on the F10 Caucasus map, but it actually transmits (as briefed) at 630khz. Really enjoying the campaign, although I'm sure Rooster squadron prefer it if I could successfully put bombs on target!

Since it apparently is not working in DCS 2.7.18.30765 Stable, does anyone know if Epsom is working in DCS 2.8.1.34667.2 Open Beta? Would like to be sure before I purchase it.

Thanks for the tips, I was going at 15-20° in missions 8 and 9, but ED folks pointed out that was causing the engine degradation issues that I was blaming on overcooling. I’ll work on picking up the pace with oil dilution, thanks for all your work!

In recent Open Beta builds (2.8.1.34437 - 2.8.1.34667.2), I have been observing the opposite issue, where in the blue AI does not orbit Biggens Hill waiting for the squadron and player to join up. Turban Red takes off 3 minutes into mission, followed quickly by Gimlet Blue-1-2, Gimlet Blue-1-3, and Turban Red4; they circle Biggens Hill twice and then head for France. Gimlet Red waits for space-bar signal, then taxis and departs Biggens Hill. This is usually about 11 minutes into the mission for me, as it takes about that long to get the engine oil to 40 degrees. Player and all remaining blue AI depart Biggens Hill in a long line with a heading of 150 degrees, no orbiting. Turban Red, Gimlet Blue-1-2, Gimlet Blue-1-3, and Turban Red4 arrive at Abbeville 39 minutes into mission, just as the Bostons cross the French coastline at Somme Bay. Turban Red, Gimlet Blue-1-2, Gimlet Blue-1-3, and Turban Red4 depart Abbeville to RTB at 43 minutes into mission, just as Gimlet Red, player, and remaining blue AI arrive at Abbeville. Red AI bandits begin circling Abbeville, and blue AI all RTB at 44 minutes. This isn't specific to Sortie 9 (and likely not this campaign, but I didn't test others). This results in a long line of blue AI crossing the channel rather than in formation. However, this is a great way to shoot down a whole pile of defenseless red bandits as they slowly orbit Abbeville! Playing stable version or rolling back to DCS 2.7.18.30765 Stable or 2.8.0.33006 Open Beta resolves this behavior. Unfortunately, doing so discards the recent Spitfire and Beware Beware Beware updates in 2.8.1.34437 Open Beta and the blue AI may get stuck on the taxiway. This does not appear to be a Beware bug, but I don't know enough about the mission mechanics to make an intelligent bug report to ED. TacView screenshot below is 39 minutes into Beware Beware Beware mission 9 on DCS World 2.8.1.34667.2 Open Beta.

appreciate your efforts, the Spitfire is a gem to fly, and having two Reflected campaigns is the cherry on top!

No, I didn't clean the spark plugs, in fact, I was not aware that was possible. I do not see any mention in the Flight Manual or Chuck's Guide, and I am unable to locate a proper keybinding to accomplish that. How do I do it? I generally let the engine oil warm to 20 degrees prior to taxiing, but even waiting until 15 degrees in Beware Beware Beware sortie 6 means you leave too late to catch up to the AI squadron before they reach France. Reflying that mission, the engine survives if I warm it all the way to 20 degrees and maintain +7 boost and 2650rpm.

Attached is a track of the Spitfire engine degrading and failing at around +4 boost, 2200rpm while crossing the Channel at 20,000' with +1 degree surface temperature. This is with DCS 2.8.1.34667.1 Open Beta in Beware Beware Beware sortie #6. I don't know much about historic accuracy of the thermostats in these planes, but if they behaved like it's modeled, the war would have had a different outcome. https://drive.google.com/file/d/1plguA4p1LcXSquDVHZbm6z6uGsITS1kd/view?usp=share_link

Just a reminder that the Spit is still over-cooling.

Super minor, but the mission briefing screenshot is from some other mission for an aircraft with a HUD. The Press Photos mission that is just before this one doesn't appear to have all 4 members of the flight (Correction: it works properly if player takes off 3rd rather than 2nd; I incorrectly understood that I was flying as #2 based on the briefing). Both are minor issues; but did enjoy having some very different missions for a change of pace, thank you! Also forced me to improve my formation flying skills, which isn't always easy the way the AI moves! DCS World (stable) 2.7.18.30765

Still not fixed.

Can confirm that the issue does not occur in DCS 2.7.18.30765 (Stable branch). The final 6 deaths on the attached screen are all crashes, two of which were right on runway 30 as I was on final approach. Until ED fixes the AI, best to stick to 2.7 stable for single-player campaigns.

AI has not been fixed in 2.8 Beta; 2.7 stable is the place to be for single player at this time. I actually am not seeing any appreciable difference in VR performance (with OpenXR) between DCS 2.8.0.32235.1 Open Beta and DCS 2.7.18.30765, but I'm CPU bound most of the time.

I don't usually take a close look at the debriefing, but it was missing my one confirmed kill so I looked closer. The inaccurate totals of kills are one thing (math is hard!), but it appears that the blue AI is are killing each other, a lot in Sortie 3. or perhaps this is just AI crashing into each other? This is with DCS 2.8.0.32235.1 Open Beta (in which the blue AI departs just fine in Sortie 3 for some reason).

Thanks, reverting to 2.7.18.30765 Open Beta solved bug #1 for me.

On DCS World 2.8 beta, I can't get the AI to take off in Sortie 2. I've tried passing the line, taking off and landing multiple times, and waiting in line for up to 40 minutes without success. Unrelated, but I'm also having trouble getting the comms menu to activate when in the air since the 2.8 upgrade and starting Beware Beware. Comms menu works in the air for instant action still, so I think maybe a setting (easy radio?) is getting forced?

Without a DCS World benchmark, the reviewers will never include it in their test suite. We have to wait for early adopters or base our conclusions on synthetic benchmarks. Firestrike is probably representative, and the Guru3D benchmarking does seem to indicate that RTX 4090 is a monster DirectX 11. Possibly a 70% improvement over RTX 3090ti. However there are some warning signs on other DirectX 11 titles as noted in this PC World review; that appears to be partially due to CPU bottlenecking, which is a very real concern in DCS in VR, even with the Ryzen 5800x3d.

In VR anyway, the advantage in performance from foveated rendering could make the difference between an otherwise superior Radeon GPU compared to a Geforce GPU at the same price (e.g. 7900XT vs RTX 4080. At least in my Reverb G2, the resolution outside the sweetspot is mostly wasted to my eyes. I only have a 6800xt currently, so I can't compare.

Sample size of only one, but I was able to complete Jagdflieger: Mission 2 on DCS 2.7.17.29493 Open Beta and made it to the debrief screen. So, maybe whatever was broken is fixed in the latest DCS build? I was unable to find keyword "break" in this particular MIZ. Debrief.log was 22 megabytes this time.

Here is a dcs.log and debrief.log from last night (DCS 2.7.17.29140 Open Beta). This is following completion of a @Reflectedmission (Bf 109 K-4 Jagdflieger: Mission 2) in Steam VR, land, shutdown aircraft and then quit. I am greeted by this error when I should be at the debriefing screen: "can not open debriefing file." Click okay, and the next prompt is "Your progress will be lost. Are you sure you want to quit?" If I click No, it just leaves me in the hanger that should have the debriefing screen in it, but with no way to exit or do anything. If I end the mission early (shot down, crash, or otherwise), it debriefs fine. The end of the dcs.log says: 2022-09-06 10:23:48.278 ERROR Gui: ERROR loading debrief.log: constant table overflow stack traceback: [C]: ? [C]: in function 'loadfile' [string "./MissionEditor/modules/me_debriefing.lua"]:437: in function 'load' [string "./MissionEditor/modules/me_debriefing.lua"]:402: in function 'show' [string "./MissionEditor/MissionEditor.lua"]:699: in function 'openReturnScreen' [string "./MissionEditor/MissionEditor.lua"]:717: in function <[string "./MissionEditor/MissionEditor.lua"]:711> The debrief.log is 35 megabytes (!), which is way bigger than allowed to attach so here is a Google Drive link: https://drive.google.com/drive/folders/17LISQ9XJWb3KnixPQ_YCwKCVO-YIYhx6?usp=sharing Hardware: Ryzen 5800x3D in Asus Pro WS X570-ACE motherboard, 64gb ECC DDR4 @ 2800mt/s, Radeon 6800XT, game on PCIe4 NVME, HP Reverb G2 in Steam VR. If time allows, I'll try on DCS 2.7.17.29493 and an older version as well this evening.