All Activity

I have the DOF H3. I would say the benefit of the 3rd sensor is quite apparent when flying helis or when you are taxing on the ground. Also dogfights in WWII you often use the rudder actively. Not so much in air in a modern jet maybe. So go for 3. Wrgt the seat I purchased this as part of the package. Tweaking SRS (the software controlling the motion rig) takes some time. There are some examples to be found, but I wish there was more profiles examples shared. The biggest challenge for me has been the motion compensation setup. Without this things become very strange in VR. I got it to work fine earlier, but with a newer version I'm still pondering on the configuration.

@baltic_dragon Just wanted to push this one again.

It says the same for me: in 2D I’m ‘GPU bound’, but in VR I’m ‘CPU bound rendering thread’ with some dips to ‘CPU bound main thread’ on unoptimised sections of maps for example. My hope is that Vulkan will fix this, so that we are GPU bound even in VR.

I will take a closer look at this, have a nice day

Has there been any word by Aerges if they will add the Corail pod to the official module? I would love to have it in MP!

Hello, unfortunatelly, it is likelly using reshade shader will not be enough. I tried to make Reshade SMAA technique working for quadview by sending to it resolution and depth buffer of the current quad views, but finally it was not reliable. So I assume it will be the same for SSAO... One problem may be DCS not sending the "good" depth buffer (that is the one for the involved quad view) to the shader, but I believe DCS devs may have fix it. So issue may be deeper in their algorithm. In theory it should be possible to replace "in game" shader by a fixed version, but I do not have the skills to fix an SSAO shader... The only thing you can do is using a VREM technique to change color/brightness of Inner view, but it is likely the needed color change will not be constant.

Yes, i left SSAO and lens effects enabled because i don't want to loose the bright glare of the sunlight and the much better cockpit lighting. I barely notice the foveated rectangle though, i can only see it when i want because - well, it moves with my eyes... I also didn't really look into the quad view tweaking options yet, there might be more potential tuning available. @VirusAM All the needed DLSS files in their latest version are now implemented in the Nvidia driver (since March or so?). So you don't need a swapper tool or to download these files. You can simply switch them on globally for your system with the Nvidia app or (the method that i prefer)-> use a current version of NvidiaProfileInspector. For me the fork https://github.com/xHybred/NvidiaProfileInspectorRevamped works best. It has all the important functionalities sorted and decluttered in the list. Simply set DLSS to run on the latest version (310.3), preset "K" (until a new version comes out) and in your game select "performance mode". What this does is switching to the new AI upscaler model that basically delivers the picture quality from "quality mode" of the former upscaler model but with a huge fps boost. And the settings persist after each driver update which i do with NVcleanstall. Which is my main performance optimization step for my system (forget all the "tweaking guides" that are mostly outdated or placebo). This tool recompiles the Nvidia driver with only the features you choose and you can get rid of a lot bloatware. Simply tick the boxes for driver, HD audio, PhysX (and DLISR maybe) and you are done. The only caveat with DLSS are some artifacts in certain situations but i care more about the huge fps gains.

Hey QCumber I am using 1920x1080 in the DCS meny system page, is that reolution you were thinking of? Is there a better option?

I'm glad you all like it! I already have a script that lets warships (Arleigh Burke–class, Ticonderoga–class) launch Tomahawk cruise missiles! Link: https://forum.dcs.world/topic/374049-automated-cruise-missile-strike-script-v1 HAVE FUN! The Scud-missile version is expected to be added in the next few days!

I decided to continue and sent my Log for comparison. I have i9-12900K 3.20 GHz Comparison of the Two DCS Log Files I've analyzed the provided log file (dcs.log from August 25, 2025) and compared it to your previous log (dcs.20250821-202548.log from August 21, 2025). The comparison focuses on key differences in system configuration, warnings, execution flow, and outcomes. This helps explain why the previous setup experienced crashes while the new one appears stable. I'll structure this as a table for clarity, followed by an explanation. Aspect Previous Log (Aug 21, i9-12900KF) New Log STONE SKY (Aug 25, i9-12900K) Implications Installation Path & Version D:\DCS World\bin\DCS.exe (Stable, MT version 2.9.19.13478) G:\DCS World OpenBeta\bin-mt\DCS.exe (OpenBeta, MT version 2.9.19.13478) Minor difference; OpenBeta may have slight patches, but same build number. No impact on crashes. Windows Build NT 10.0.26100 (Possibly Insider/preview build) NT 10.0.19045 (Stable release build) Preview builds can introduce instabilities; stable build is less prone to OS-level issues. CPU Model & Config Intel i9-12900KF: 16 cores, 24 threads (hybrid: 8 P-cores/16 threads + 8 E-cores/8 threads). Efficiency classes: Mixed (class 1: cores 0-15; class 0: 16-23). Performance classes: Varied (class 3: 12-15; class 2: 0-11; class 1: 16-19; class 0: 20-23). Affinity: All cores used, IO on E-cores (16-23). Intel i9-12900K: 8 cores, 16 threads (appears to be only P-cores active). Efficiency classes: Uniform (all class 0). Performance classes: Varied but simplified (class 1: 8-11; class 0: 0-7,12-15). Affinity: Common cores {4-7,12-15}; Render on {8-11,0-3}; No IO cores listed, no unavailable cores. Key difference: E-cores seem disabled in BIOS on the new setup (reducing to 8 cores/16 threads). This eliminates hybrid CPU issues. Hybrid setups often cause DCS instability in multi-threaded (MT) mode. RAM 32 GB (32556 MB) 64 GB (65303 MB) More RAM in new setup reduces memory pressure, but unlikely the primary crash cause. CPU Warnings Explicit warning: "CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores)". No such warning. Core parking (Windows power-saving feature) on hybrid CPUs leads to desyncs and crashes in DCS MT, especially in CPU-intensive modules like AH-64D. Disabling E-cores prevents this by avoiding mixed core types. Scripting Errors Present (e.g., "No preset named 'MDRN_B_A_PGM_HTP'" in HeavyMetalCore for B-52H/B-1B). Identical errors present. These are benign vanilla DCS issues; not causing crashes. Mods & Plugins Loads mods like Currenthill Assets Pack (replaces units); same plugins start/end. Identical mod loading (e.g., Currenthill Assets Pack). No difference; mods aren't the culprit. Audio Devices 4 devices (Headphones, Speakers, Digital Output, Monitor). 4 devices (Digital Output, Monitor, Oculus Virtual Audio, HD Audio 2nd output). Slight variation, but no errors in either; irrelevant to crashes. Execution Flow Loads modules, but crashes during simulation (ACCESS_VIOLATION in AH64D.dll during ExternalFM sensor/timing calls). Ends with crash dump. Loads modules, initializes Syria terrain, handles object position errors (non-fatal), then normal shutdown. No crash; log closes cleanly. Previous crash tied to AH-64D FM/sensors under hybrid CPU load. New log shows stable run, likely due to uniform cores. Timing & Outcome Starts ~17:56 UTC, crashes ~20:25 (long session?). CTD to desktop. Starts 14:21 UTC, normal exit ~14:31 (short test?). Successful shutdown. New setup avoids the violation, confirming hardware config fix. Explanation and Insights Root Cause Resolution: The previous crash was an ACCESS_VIOLATION in the AH-64D module, triggered by core parking on a hybrid Intel 12th-gen CPU (P-cores for performance, E-cores for efficiency). DCS MT is sensitive to this, as it assigns tasks (e.g., IO to E-cores), leading to memory access issues during high-load operations like flight model (ExternalFM) or sensor processing. In the new log, E-cores are disabled (evident from reduced core/thread count and uniform efficiency class), eliminating the parking warning and crash. This is a common fix for DCS on 12th/13th-gen Intel CPUs, as hybrid architectures can cause stuttering or CTDs in VR/multi-threaded scenarios. Why It Works Now: With only P-cores active, DCS runs on consistent high-performance threads, avoiding desyncs. The increased RAM and stable Windows build may help marginally, but the CPU change is the key. Recommendations: If this is the "other comp" without crashes, replicate the setup on the first PC by disabling E-cores in BIOS (under CPU settings, set E-core count to 0). Alternatively, use tools like Process Lasso to force affinity to P-cores only. Test in a mission with AH-64D to confirm. If mods like Currenthill are still suspect, remove them temporarily. It's still not certain, sir! I hope you will continue your investigation and find the cause. We should probably wait for the new distribution of tasks for cores in the AH-64D mod. I don't remember exactly, but I did some kind of processor setup in the BIOS after assembling the PC. Probably this issue also requires study, judging by the comparison table of our processors

What resolution are you using?

This was difficult for me, I used the Grock AI, if you don't mind. We seem to have a direction where to look for the problem. But I'm not sure. This is the AI's analysis, not mine. Type of Error: ACCESS_VIOLATION (code C0000005). This indicates an attempt to access memory that is either non-existent or protected (e.g., null pointer dereference or data corruption). Crash Location: In the module AH64D.dll (D:\DCS World\Mods\aircraft\AH-64D\bin\AH64D.dll), which is responsible for the AH-64D Apache module. The stack trace shows calls from ExternalFM (external flight model) for AH-64D: ExternalFM::AH64::AH64FM::setImmortal + 0x10EC5 ExternalFM::AH64::AH64FM::getSensorsSystem + 0x29115 ExternalFM::AH64::AH64FM::setImmortal + 0x15D97 Followed by transitions to CockpitBase and World (DCS simulation core). Context: The crash occurred during simulation or loading, likely when DCS was processing cockpit device timers (cockpit::avDevice_BasicTimer::NextEvent) or the event calendar (wSimCalendar::DoActionsUntil). This happened shortly after launch (log starts at 17:56:29 UTC, crash at 20:25:48, though this could be local time; actual launch ~17:56). DCS Version: 2.9.19.13478 (MT - multi-threaded version). This is a relatively recent build (build 376), possibly beta or open beta as of 2025-08-21. System: Windows 10 (NT 10.0.26100), Intel i9-12900KF CPU (16 cores, 24 threads, hybrid with P-cores and E-cores), 32 GB RAM, NVIDIA GPU (based on loaded DLLs like nvwgf2umx.dll). 2. Key Findings from the Log CPU Warning: The most notable line is WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores). This directly points to an issue with core parking—a Windows mechanism that "puts to sleep" inactive cores to save power. On a hybrid CPU (like your i9-12900KF with Performance-cores and Efficiency-cores), this causes instability in multi-threaded applications like DCS. Similar crashes are described in threads such as "DCS World - Force CPU Core Parking" (DCS Forum, 2025) and "DCS 2.9 stuttering with 12/13 gen Intel CPU" (Reddit, 2023). Many users with 12th+ gen Intel CPUs report CTD (crash to desktop) issues with AH-64D due to this. Your log shows the CPU affinity mask using all cores, but with different efficiency classes (P-cores: 0-15, E-cores: 16-23), and DCS assigns IO tasks to E-cores (16-23). This is not a bug in the AH-64D itself but a system incompatibility exacerbated by the module (AH-64D demands significant CPU resources for its flight model and sensors). I hope this helps. Naturally, this should be double-checked.

Try this example: test.miz

RWR issues? It's almost like the closer a radar gets the stronger the signal.

Got it consistently inconstant.

I was wondering if anyone can teach me how to create a mission of a Tu-22M: 1. Take off from Airbase A from a parking spot 2. Attack a ship 3. Land at the same base I have tried but for the life of me, I can't get it to engage the ship. It always seems to not engage the target. It just flies back to base.

Раньте это делалось длинным зажатием команды вниз взаимодействия с ИИ Джорджа. Перечень команд был в виде таблицы в самом конце мануала, в разделе «GERGE» AI. Мануал обновился недавно, под рукой нет. Были большие изменения Джорджа в крайних патчах. В описании этой команды должно быть что-то типа … regenerate target list

Thank you Bankler！ Learned alot！FINALLY！

Same testing parameters, Only difference is 35k ft altitude. All have been done with full fuel & no fuel only to see if how much of a factor weight was and tested over a 40nm span, Which the differences in fuel of that have been incredibly insignificant. "2x PL-5 + 4x SD-10: Max Speed of Mach 1.15 before complete fuel exhaustion" This of them all is the biggest concern with it all, Now let me also say I am not questioning this in a sense of I am right and it is wrong. I just merely don't understand how a loadout similar to; "2x PL-5 + 2x SD-10 + 2x GB-6 SFW" Has a 45% higher drag value, weighs more (I will see exactly how much more later when I am home) and somehow gets closer to its top end much faster than the first loadout. While at the same time only reflecting a 15% difference in its top end.