Pyrocumulous

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.

DCS 2.7.17.29140 Open Beta, haven't attempted it with any other versions recently. I have been able to complete this mission previously (on prior versions), but trying to take out more bombers on this play through results in (I think) excessive debrief log.

When I successfully complete a certain mission (Bf 109 K-4 Jagdflieger Campaign by Reflected Simulations: Mission 2 @Reflected) in 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 debrief.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 I suspect it's just too big a log file due to the amount of activity in this mission. 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. dcs.log

These charts compare performance running the same 11 minute segment of The Big Show mission 9 (huge bomber squadron, bombing, and then enemy intercepts show up). Identical everything, but with Ryzen 3900X in the first pair of fpsVR charts, and Ryzen 5800x3D in the second set. Other hardware: Asus Pro WS X570-ACE motherboard, 64 gb unbuffered ECC DDR4 @ 2800 CL20 (SK Hynix C-die), Radeon 6800XT reference, game on PCIe 4 NVME, Reverb G2. No upscaling or reprojection: just native resolution. Notice how the frametime curve moved way to the left? Except for when all 80 bombers are dropping bombs, it's now GPU limited. The GPU is nearly always running at full tilt rather than waiting on the CPU. The improved smoothness is unreal, this upgrade far exceeded my expectations.

Fixed it for me. Upgraded CPU, and apparently that resulted in my BIOS time drifting 12 minutes.

DCS World in VR needs (1) high single-thread speed, and (2) it hits the memory hard with lots of calls. For #1, the fastest single threaded processor is what you want. For #2, you want the fastest memory you can get. For Ryzen this has meant matching memory speed to the infinity fabric speed (e.g. 3600 Mt/s, and infinity fabric at 1800 Mhz) and then picking the lowest CAS latency. For Intel, this has meant the memory with the quickest first-word latency. However, 3D V-Cache kind of changed the rules with criteria #2. Now, you can get a Ryzen 5800x3D with lots of cache, and it doesn't really need fast memory because DCS World is hammering the (much faster) cache rather than the memory. To your question, probably the best canned benchmark is MS Flight Simulator. To answer your deeper question, the Zen 4 3D v-cache CPUs are likely going to be the amazing for driving VR in DCS World. I am skeptical that either the new non-vcache Zen 4 or Rocket Lake CPUs will actually out perform the current Ryzen 5800x3D in DCS. The other challenge with buying Zen 4 now is that DDR5 is in the early days, so the latency is still relatively high, which is going to hurt in DCS. For GPU, 3D Mark Firestrike is a good benchmark for DirectX 11. In VR, only the nVidia cards support foveated rendering, which is a pretty significant advantage. I am currently on Radeon, but plan to switch solely for that functionality for this next generation.

Wow, turning off Wake Turbulence makes a huge difference in performance in missions with large bomber formations, such as #5 that became a slideshow. My Ryzen 3900X can actually keep VR frametimes under control now. My performance in gunning bombers is now substantially better too now that I can get in close without getting tossed

I see Night Vision Goggles in the controls for the Spitfire, but nothing happens when I select that. The manual makes no indication of these existing, so I assume is just an oversight in the keybinds?

I have the same issue, but was able to solve it by rolling back to 2.7.11.21408.1 Open Beta. After doing so, I tested by upgrading back to 2.7.11.22041 Open Beta and the bug returned; then rolled back to 2.7.11.21408.1 Open Beta and I'm happily flying again. To roll your install back, from command prompt: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin>DCS_Updater.exe update 2.7.11.21408.1@openbeta