Panzerlang

Not just for input, according to the video.

1. Why Reflex Would Benefit DCS World Complex Input Processing: DCS involves precise control inputs from peripherals like HOTAS setups, rudder pedals, and VR hand tracking. Reducing input-to-display latency would make these controls feel more responsive. VR Gaming: Many DCS players use VR headsets, where input latency and frame timing are critical for an immersive and smooth experience. Reflex could enhance VR gameplay by reducing motion-to-photon latency. High Visual Demand: DCS is a CPU and GPU-intensive simulator. By optimizing the rendering pipeline with Reflex, you could experience smoother interactions, even under heavy system load. 2. How Reflex Works in This Context Minimizes Latency: Reflex reduces the time between input (e.g., moving your joystick) and seeing the result on the screen. This is especially valuable in combat scenarios where rapid reactions are key. Balances CPU and GPU Load: DCS can bottleneck on either the CPU or GPU, depending on settings. Reflex ensures the GPU doesn't queue up excessive frames, keeping the system responsive. Improves Frame Timing: By reducing latency and synchronizing frame generation with input, Reflex could help mitigate microstuttering, enhancing the fluidity of the simulation. 3. Current Limitations Not Currently Supported: Reflex is not yet available in DCS. NVIDIA Reflex requires integration by the game developers, and Eagle Dynamics (the developers of DCS) haven't announced plans to implement it. Complexity of DCS: The sheer complexity of DCS’s rendering engine and physics might make Reflex integration a challenging task for developers. 4. Alternatives for Latency Optimization While waiting for Reflex, you can reduce latency and stuttering in DCS with these steps: Use DLSS or FSR: If your GPU supports DLSS, enabling it can help improve performance and reduce input lag by lowering rendering loads. Enable G-Sync or FreeSync: This can help smooth out frame delivery, reducing perceived latency. Lower Latency Settings: Enable NVIDIA’s Low Latency Mode in the NVIDIA Control Panel. Optimize Settings: Fine-tune in-game settings to balance CPU and GPU load, particularly in VR or high-resolution setups. Update Peripherals: High-quality, low-latency input devices (HOTAS, pedals, etc.) can make a noticeable difference. Conclusion If NVIDIA Reflex were integrated into DCS, it could provide a huge boost in responsiveness and smoothness, particularly for VR and competitive gameplay. For now, leveraging tools like DLSS, Low Latency Mode, and careful hardware optimization can help you achieve a similar effect. Let’s hope Eagle Dynamics considers Reflex integration in future updates—it could be a game-changer!

The video mentions the CPU render-queue. What's the betting this might explain a lot about micro-stuttering? Maybe Reflex might be a big help. 1. Why Reflex Would Benefit DCS World Complex Input Processing: DCS involves precise control inputs from peripherals like HOTAS setups, rudder pedals, and VR hand tracking. Reducing input-to-display latency would make these controls feel more responsive. VR Gaming: Many DCS players use VR headsets, where input latency and frame timing are critical for an immersive and smooth experience. Reflex could enhance VR gameplay by reducing motion-to-photon latency. High Visual Demand: DCS is a CPU and GPU-intensive simulator. By optimizing the rendering pipeline with Reflex, you could experience smoother interactions, even under heavy system load. 2. How Reflex Works in This Context Minimizes Latency: Reflex reduces the time between input (e.g., moving your joystick) and seeing the result on the screen. This is especially valuable in combat scenarios where rapid reactions are key. Balances CPU and GPU Load: DCS can bottleneck on either the CPU or GPU, depending on settings. Reflex ensures the GPU doesn't queue up excessive frames, keeping the system responsive. Improves Frame Timing: By reducing latency and synchronizing frame generation with input, Reflex could help mitigate microstuttering, enhancing the fluidity of the simulation. 3. Current Limitations Not Currently Supported: Reflex is not yet available in DCS. NVIDIA Reflex requires integration by the game developers, and Eagle Dynamics (the developers of DCS) haven't announced plans to implement it. Complexity of DCS: The sheer complexity of DCS’s rendering engine and physics might make Reflex integration a challenging task for developers. 4. Alternatives for Latency Optimization While waiting for Reflex, you can reduce latency and stuttering in DCS with these steps: Use DLSS or FSR: If your GPU supports DLSS, enabling it can help improve performance and reduce input lag by lowering rendering loads. Enable G-Sync or FreeSync: This can help smooth out frame delivery, reducing perceived latency. Lower Latency Settings: Enable NVIDIA’s Low Latency Mode in the NVIDIA Control Panel. Optimize Settings: Fine-tune in-game settings to balance CPU and GPU load, particularly in VR or high-resolution setups. Update Peripherals: High-quality, low-latency input devices (HOTAS, pedals, etc.) can make a noticeable difference. Conclusion If NVIDIA Reflex were integrated into DCS, it could provide a huge boost in responsiveness and smoothness, particularly for VR and competitive gameplay. For now, leveraging tools like DLSS, Low Latency Mode, and careful hardware optimization can help you achieve a similar effect. Let’s hope Eagle Dynamics considers Reflex integration in future updates—it could be a game-changer!

Gotta love AI. " what is 1:1 ram timing and can it reduce stutter? ChatGPT said: ChatGPT What is 1:1 RAM Timing? 1:1 RAM timing refers to synchronizing the RAM speed (memory clock) with the memory controller's frequency or the Infinity Fabric (on AMD systems). In simpler terms: RAM clock: The actual speed at which your memory operates. Controller clock: The speed at which the CPU's memory controller operates. 1:1 ratio: When these two operate at the same effective frequency, it reduces latency and ensures more efficient data transfer between the CPU and RAM. 1:1 RAM Timing in Practice On AMD Ryzen systems, the term often refers to setting the RAM speed (DDR frequency) to match the Infinity Fabric Clock (FCLK). For example: DDR4-3200 RAM operates at 1600 MHz (half the DDR speed). To achieve 1:1, the FCLK should also run at 1600 MHz. On Intel systems, it might mean aligning the memory clock with the CPU's uncore clock for optimal performance. Can 1:1 Timing Reduce Stutter? Yes, in certain scenarios, 1:1 RAM timing can help reduce stuttering, especially in games or applications that are heavily dependent on memory performance. Here's why: Reduced Latency: Synchronizing RAM and CPU clocks minimizes the delays caused by mismatched frequencies. Smoother Data Flow: A 1:1 ratio ensures the CPU and RAM communicate efficiently, preventing bottlenecks that can cause stuttering. Improved System Stability: Running at a 1:1 ratio is often more stable compared to overclocking the RAM beyond what the memory controller can handle efficiently. When Will You Notice an Improvement? Gaming: Memory-sensitive games (e.g., open-world or simulation games like DCS World or Cyberpunk 2077) may see reduced frame stuttering. Productivity: Tasks involving large datasets, like rendering or simulations, can benefit from lower latency. System Bottlenecks: If your system previously had mismatched clocks (e.g., high RAM speed with a lower Infinity Fabric clock), 1:1 timing can smooth performance. How to Achieve 1:1 Timing? AMD Systems: Access BIOS/UEFI settings. Set the RAM clock and FCLK to the same value. For example: DDR4-3200 → FCLK at 1600 MHz. DDR5 (if supported) → Follow similar principles with its scaling. Test stability using tools like MemTest86 or Prime95. Intel Systems: Adjust the DRAM multiplier and memory controller frequency in BIOS. Balance RAM speeds with CPU's memory controller capabilities. Key Considerations CPU and RAM Limits: Not all CPUs and RAM can achieve high frequencies in 1:1 mode. Test stability carefully. Real-World Gains: The benefits might be minor in systems that are not memory-bound. Overclocking vs. Stability: Pushing RAM or FCLK too far can result in crashes or instability, negating any performance gains. If you’re experiencing stutter, aligning RAM timings and ensuring a 1:1 ratio can be a good step in your optimization process! 4o You said: gigabyte z790 mobo, 13900k cpu and 6400 ram, can i do it with these? ChatGPT said: ChatGPT With a Gigabyte Z790 motherboard, an Intel Core i9-13900K, and 6400 MHz RAM, achieving a 1:1 ratio (synchronized RAM and memory controller clock speeds) is unlikely due to the architecture of Intel's 13th Gen CPUs. Here's why and what you can do: 1. Intel's Memory Controller Design Intel's 13th Gen CPUs (like the 13900K) use a Gear Mode system to manage memory: Gear 1: Memory controller runs at the same speed as the RAM (1:1 ratio). Gear 2: Memory controller runs at half the speed of the RAM (2:1 ratio). Gear 4: Memory controller runs at one-fourth the speed of the RAM (4:1 ratio). With high-speed RAM like DDR5-6400, the memory controller defaults to Gear 2 for stability, meaning the controller runs at 3200 MHz while your RAM runs at 6400 MHz (effective). This is necessary because running the memory controller at 6400 MHz is beyond its capability. 2. Can You Force a 1:1 Ratio? For DDR5-6400 RAM, a Gear 1 (1:1) ratio is not feasible. The memory controller can't handle such a high speed without instability, even on high-end CPUs like the 13900K. Lowering the RAM frequency to a range like DDR5-4800 or DDR5-5200 might allow for Gear 1 operation, but this defeats the purpose of using high-speed RAM. 3. What Can You Do Instead? While you can't achieve a 1:1 ratio at DDR5-6400 speeds, you can optimize your setup for the best performance: Enable XMP/EXPO Profiles XMP (Extreme Memory Profile) ensures your RAM runs at its advertised speed (e.g., 6400 MHz) with optimal timings. Access the BIOS and enable the appropriate XMP profile for your RAM. Optimize Gear 2 Performance Gear 2 is designed for high-speed DDR5 and works efficiently on Intel 13th Gen CPUs. Stutter is unlikely with this configuration. Adjust Sub-Timings and Latency Fine-tune RAM timings in the BIOS for lower latency. Tools like MemTest86 can help you test stability after adjustments. Test Stability Use benchmarks like AIDA64 or Cinebench to ensure the system runs stable at your desired settings. Balance Performance If you're concerned about stuttering or latency, consider slightly lowering the RAM frequency (e.g., DDR5-6000 or DDR5-5600) while tightening timings. This can yield a better balance of latency and speed. Conclusion With a Z790 motherboard, 13900K CPU, and DDR5-6400 RAM: Achieving a 1:1 ratio is not possible at 6400 MHz due to Intel’s Gear Mode limitations. Gear 2 mode is perfectly optimized for DDR5-6400 and should provide excellent performance with minimal stuttering. For the best results, enable XMP and, if desired, fine-tune RAM timings or frequencies for reduced latency. This setup is high-end, and you should enjoy excellent gaming and productivity performance even without a 1:1 RAM timing. 4o The video talks about the CPU render-queue. What's the betting this might be a significant cause of micro-stutter?!

Can haz NVidia Reflex pls? "As of January 2025, NVIDIA Reflex is not officially supported in DCS World. NVIDIA Reflex is a technology designed to reduce system latency in games, primarily benefiting fast-paced, competitive titles. While DCS World has integrated technologies like NVIDIA DLSS to enhance performance and visual quality, NVIDIA Reflex has not been implemented in the simulator."

SteamVR is an app provided by Steam, it's not Steam itself. You fire up SteamVR and then run DCS from it's own launcher.

My FFBeast has been completed and will be shipped on Monday. Thanks for the videos.

Yeah, I tried all the known settings. Back to the latest Pimax Play and its own software, all good again. PD down to 1.0, DLSS back on and looking peachy with stutter/jerk noticeable only if I look for it. I've also bumped some other stuff back up with no ill effects (on Caucasus at least). I think the combos of hardware and software are so complex there will never be a perfect setup for everyone across the board, excepting max hardware as being an axiomatically obvious requirement for the best possible foundation upon which to erect the shakey edifice of individual settings. Lol, that was a mouthful.

Absolute clusterfk. Using Revo Uninstaller Pro which removes everything, including registry stuff etc. Removed Pimax Play and installed 1.29. Installed all the MBuccia stuff, used Focus to confirm Quad is working in game, NO frame-capping stuff set up anywhere but in the game can no longer get anything above 60fps and the frame-time window is a constant flow of green spikes. Image quality is trash too. Oh well, hopefully I can get rid of it all with Revo and go back to how it was before without issues.

I'm going to have a go with Pimax 1.29 and MBuccia's stuff and see what happens.

The suckerberg parasite ethos. I'd love to be a fly on the wall when they interview job candidates.

Very weird.

It very clearly did on my setup. I had MBuccia's set up with a very small and easily visible focus window. When I enabled Pimax' Quadviews the focus window was a lot bigger. The Pimax one also ran the game a tiny bit better (less micro-stutter). I assumed this was because the CPU wasn't having to run an external app (native software vs external) but who knows. I certainly would have noticed a 15% degradation in performance! (as mentioned by WipeUout). I'll play around with the settings mentioned above but won't expect anything major, I've previously run the game with potato settings and it made next to no difference. Since then, with all the incremental hardware and Windows tweaking, that's where the difference was slowly made. But, new build so worth a new punt. Game Bar Capture is the only software that has zero noticeable performance impact. Before that I tried NVidia's stuff, Bandicam, FRAPS and OBS, all those hit performance very badly.

Mariannas, absolute stutter/jerk fest, even out to sea and looking at the island from a distance. Look away to sea and it goes smooth. I record live, Game Bar, it records the monitor VR mirror. Pimax Play at native render (1.0), DCS VR PD at 1.5. Settings:

Good post Luc.

I had x4 16GB at 6400, went to x2 32GB at 6400, no discernible difference but at least the Benchmark thing doesn't slate me for not having XMP enabled. Lol. NB: My x4 sticks were rated at 7200, so I could only BOOST, not XMP. For some reason the Benchmark then didn't see them as "Dual Channel" (or even Quad Channel) for some reason. All very confusing. Having learned that lesson I made sure the x2 32GB were rated at 6400, which is generally considered to be the fastest the best motherboard chipsets can commonly handle (without getting into voltage manipulations and similar malarkey). But watch a few expert videos and discover RAM speeds and timings don't really make much difference anyway (within reason).

Sorry dude, age is my only excuse. Video, to give a baseline for my definition of The Stutter. It's hard to visualize each person's experience but here's mine for comparison. In actual fact this run was a fair bit worse than usual, but hey ho, it's in the ballpark of what I generally get. Yes. If Quadviews in Pimax Play is enabled it takes over from MBuccia's one.

Aye carumba, that sounds like a recipe for complete head-fkry. Lol. Get two new SSDs and plug those in after removing the existing ones and do the whole shebang brand new (assuming money's not a consideration). W10 and DCS on separate drives. It's the only way to be sure.

13900k, 4090, 64GB RAM at 6400. Work your way through this lot for fine-tuning that might help:

No. If you set the headset to auto shut down it will of course crash DCS VR. There's a setting in Pimax Play for auto shutdown, mine is set to "10 minutes". In "General" you can set it from "Never" to "1 Hour".

In my case, Pimax Play native OpenXR and Quadviews worked a little better on my old install and just as good on my fresh W11-Pro 24H2 install.

Sorry dude, thought I had. No, I'm using the Pimax Play software now. I did previously have MBucchia's software...turbo on or off, no difference (OpenXR Companion). I've had that cockpit jitter too but it was tied to overall settings (at 120htz it was very obvious). Maybe try the cockpit jpg settings? (250 vs 1040 or something).

I had it for a bit (the NVidia App did it) but I saw no impact from it in the game for good or bad.

Oh, I've completely turned off all anti aliasing without any significant visible difference to image quality but with definitely smoother frames.

Nice. But yes, it's a crying shame that different maps have massively different performance for no apparent reason. Caucasus and Mariannas have very similar building and tree densities, but the latter is a spike & stutter fest. Like an idiot I went and bought every single map, only to find most of them are unplayable in VR. Not impressed with ED on that front, at all. Maybe they should focus on making the latest map useable before pumping out a new one.