Jump to content

Ready

Members
 View Profile  See their activity

  • Posts

    663

  • Joined

  • Last visited

3 Followers

Personal Information

  • Flight Simulators
    DCS, MSFS, X-Plane.
  • Location
    Netherlands
  • Interests
    Aviation (DCS, GA), Pool (1-pocket), Sailing
  • Website
    https://www.youtube.com/channel/UCm1MRJcn9K-89F6qnK0DVIQ

Recent Profile Visitors

3054 profile views
  1. Ready
    Removing Envelope There are two types of envelope icons in DCS: Envelope Type Source Removal Method Mission message envelope Mission “MESSAGE TO …” triggers disable_messages etc. Multiplayer chat envelope MP chat notifications / message log Must disable chat notifications You still want the restart warnings (mission messages), so we only remove the chat envelope. Remove the Multiplayer Chat Envelope (keep mission/server messages) Try this first: Step 1 – In-game setting Go to Options → Gameplay Disable / uncheck: “Allow Multiplayer Chat” Apply and restart DCS. This removes chat pop-ups and the envelope icon, but you can still see mission messages. If you still want to be able to open chat manually but don’t want pop-ups, use Step 2 instead. Step 2 – Hide Chat Notifications but Keep Chat Available Add this to your autoexec.cfg: chat_window_use_history = false chat_window_show_status = false This stops DCS from showing the envelope or “new chat message” alert. You can still press TAB to open chat when you want it. Step 3 – Fully remove chat but keep mission/server messages If your server sends restart warnings through mission triggers (not chat), use this: disable_multiplayer_chat = true Only use if restart messages come from mission messages, not chat — otherwise you’ll lose them. Quick test to confirm which envelope it is: When the envelope appears, press TAB: If chat opens → It’s the MP chat envelope If nothing opens → It’s the Mission message envelope
  2. Ready
    These I had in the autoexec.cfg: DLSS_Preset = "K" HUD_MFD_after_DLSS = true
  3. Ready
    yup. I sometimes have the weirdest stupidest discussions with it, especially in voice.
  4. Ready
    Well it all started with 'check this dcs file and tell me what i can do to reduce the warnings and errors and optimize dcs overall', while pushing my dcs.log and this lead to a lengthy discussion, as it usually does. I fed it back the stuff I disagreed with or did not really understand and then I received more/better information. We also checked my options.lua, export.lua and some other stuff. ------------------------------------------------------------------------------------------- Saving space I almost had a seizure when I saw the size of the latest update and wanted to install Afghanistan, which did not work. I thought I was okay with a 1TB drive just for my DCS but the past 2 years I just had been piling on mods and maps. I know there is a way to just put maps on other volumes, but did not yet want to get into that. I used Folder Size Explorer and together with ChatGPT ran through sizes of certain folders and components. I have saved quite a bit of space and removed a bunch of warnings and errors from the dcs.log and if I believe ChatGPT I also have a more stable experience (which I still have to properly test but the first experience looks promising. Removing the Envelope in the screen Flying in VR it always bothers me to see the envelope in the screen. I removed it a while back but somehow it appeared again. I hope it is now permanently gone. I added the following to the autoexec.cfg -- === Smart clean cockpit setup === -- Keeps mission/server messages visible but removes clutter like envelope and subtitles. disable_hint_messages = true -- hides tutorial/training hints (like “press space to continue”) disable_player_messages = false -- keep mission / server messages visible disable_messages = false -- KEEP THIS FALSE so you still see restart / mission text options.graphics.radioSubtitles = false -- disables radio text (voice only, cleaner) options.graphics.messagesFontSize = 14 -- smaller message font (optional, adjust for VR visibility)
  5. Ready
    Sweet. Yes I have had many many many instances where ChatGPT was wrong (mostly outside of DCS)and I had to keep on pushing and bringing other stuff in the equation for it to also constantly change its mind on me I believe the same applies to its DCS knowledge, which of course it takes from all sorts of sources. I have tested my setup with every setting/tweak imaginable and found that not all mainstream recommendations work for my setup. So I am happy it spotted a bunch of crap and helped me to get rid of it. Soon I will return to regular testing and see how the changes hold up. Maybe for some I revert back to how it was.
  6. Ready
    Yes I did manually in options.lua
  7. Ready
    Went through the list and just did what was recommended. Also set the FPS restrictions in RTSS. I haven't run any proper tests yet, but so far it feels quite okay. -- Nice — that’s a clean log overall and a great baseline for performance tuning. Here’s a breakdown of what I see and what you can tweak or safely ignore: Summary of key points from your log Category Status / Message Recommendation CPU Ryzen 7 9800X3D, 8 cores, all available (affinity mask 11111111) Perfect — no cores restricted. Keep it this way in Process Lasso. Process Lasso WARNING APP (Main): ProcessLasso is running Fine — DCS detects it. Ensure DCS has “Disallow ProBalance” and “Performance Mode” checked. Hyper-V WARNING EDCORE: hypervisor is active Optional — you can leave it on unless you need the very lowest latency in VR. Graphics settings DLSS Quality (DLSS_PerfQuality = 1), Scaling = 1, AA = DLAA, MSAA = 0, Upscaling = DLSS Correct now — no double-scaling; DLSS handles AA internally. Platform timer 15.6 ms Normal for Windows; you can’t improve this. OpenXR runtime Varjo 4.3.1 + OpenXR Toolkit + XR Frame Tools layers Excellent Varjo-Aero stack; nothing wrong. Missing textures glove_, KevinWakePattern.dds, type.anim Harmless. These are placeholder animation textures missing from core files — won’t affect FPS. DLSS init 832×712 → 1244×1068 and 968×832 → 1452×1244 DLSS upscaling is active per-eye, correct for Varjo Aero quad-views. Driver NVIDIA 571.96 Up-to-date. Recommended optimization checklist Graphics options (already good) ["Upscaling"] = "DLSS", ["Scaling"] = 1, ["AA"] = "DLAA", ["MSAA"] = 0, ["Sharpening"] = 0.3, ["maxFPS"] = 300, -- leave uncapped unless using RTSS frame cap ["water"] = 0, ["clouds"] = 0, -- reduces VR overhead ["terrainTextures"] = "min", -- lightest ["visibRange"] = "High", -- balanced choice You can lower visibRange to Medium or reduce preloadRadius (77200 → ~50000) if frametimes stutter when entering dense maps. Process Lasso Verify the persistent rules for DCS.exe: CPU Affinity: all cores (0–7) CPU Priority: High Disallow ProBalance: Induce Performance Mode: (check “Options → Performance Mode → Manage Performance Mode Processes” to ensure DCS is listed) Power plan: Bitsum Highest Performance (installed) Background apps: Limit Chrome, Discord, Steam, OBS, etc. to cores 0–2 and set priority = Below Normal. RTSS (optional) Use RivaTuner Statistics Server to cap DCS at a multiple of your headset refresh: e.g. Varjo Aero = 90 Hz → cap = 90 fps. This stabilizes frametime spikes better than DCS’s internal maxFPS. DLSS/AA consistency Your log shows DLSS + DLAA = good combo. Don’t change the AA line even if DCS flips it; DLSS internally does the anti-aliasing anyway. Mods / packs You have CurrentHill Assets Pack active; it replaces several units (Mi-28N, T-90). This can generate extra texture loads and RAM use — if you see longer mission loads, try disabling it when testing pure performance. Optional cleanup The repeated “glove” texture errors come from missing cockpit VR hands. You can clean those up by deleting: Saved Games\DCS.openbeta\metashaders2\ Saved Games\DCS.openbeta\fxo\ and letting DCS rebuild them. Overall ✔ DLSS setup = correct ✔ Scaling = fixed (no double render) ✔ Process Lasso = detected and working ✔ Only harmless missing-texture warnings remain Your system is now properly optimized — the next gains come from frame-pacing tuning (RTSS) and background-process isolation, not from DCS settings.
  8. Ready
    Process Lasso - still to check (again..) Process Lasso can help or hurt DCS depending on how it’s configured. Your log shows it’s actively altering DCS’s CPU affinity, which is not ideal for Ryzen 7 9800X3D. Let’s break this down so you can decide exactly what to change. 1. What your log shows process affinity mask: 11111000 unavailable cores: {0,1,2} WARNING APP (Main ProcessLasso is running That means DCS is only allowed to use cores 3 – 7, while cores 0 – 2 are blocked. You’re effectively running DCS on five of the eight cores on your 9800X3D. 2. Why that hurts performance Issue Effect Fewer cores available MT build of DCS can’t fully parallelize terrain, audio, and render threads. Unbalanced CCD usage 9800X3D is single-CCD; limiting cores only restricts Windows’ scheduler. Artificial isolation Process Lasso overrides Windows Game Mode’s thread steering. Confuses GPU driver thread scheduling Nvidia driver sees “reduced CPU group” and sometimes raises render latency. You’ll still run fine, but frametimes and loading are slightly worse, and the CPU graph will look oddly sparse. 3. How to fix Process Lasso for DCS Option A – Completely disable its control Open Process Lasso. Right-click DCS.exe → “Active rules” → Uncheck everything. Also disable any ProBalance or Performance Mode forcing for DCS. In the toolbar: Main → Active Process Rules → Uncheck “Enable default priorities / affinities”. Reboot. Option B – Keep Process Lasso, but free all cores Right-click DCS.exe → CPU Affinity → Always → Select all cores (CPU 0 – 7). Right-click DCS.exe → CPU Priority → Always → High (optional). Right-click DCS.exe → I/O Priority → Normal. Leave ProBalance disabled for DCS. Option C – Use it only to keep background junk quiet If you like its automation, do this instead: Keep DCS unrestrained. Set Explorer.exe, browsers, Discord, etc. to “Below Normal priority”. This protects DCS’s main thread without restricting its cores. 4. Verify it worked After fixing, launch DCS and open a fresh dcs.log. You want to see: process affinity mask: 11111111 unavailable cores: {} That means DCS can use all 8 cores. 5. Best overall setup for your 9800X3D Component Setting Notes Process Lasso Off or DCS = all cores Don’t restrict cores 0–2. Core Isolation (VBS) Your choice (-2 fps vs -1 ms latency) Both fine; keep whichever feels smoother. RTSS limit 89 fps (for 90 Hz Aero) Perfect frametime pacing. Windows Game Mode On Lets scheduler prefer DCS threads. GPU Scheduling On (Windows Graphics Settings) Lowers render-queue latency. Quick takeaway For Ryzen X3D, let Windows handle core scheduling. Process Lasso should never limit DCS’s cores — use it only for background processes. ------------------------------------------------------------------------------ Challenge: I use process lasso to keep dcs away from other stuff ChatGPT zei: Perfect — that’s exactly what Process Lasso is best for … as long as it’s isolating background apps, not throttling DCS itself. Let’s fine-tune it so it protects DCS but never limits it. Goal DCS = full priority, all cores, unrestrained Everything else = lower priority and/or fewer cores Recommended setup for DCS + Process Lasso Free all DCS cores Launch DCS once so it appears in the list. Right-click DCS.exe → CPU Affinity → Always → Select all cores (CPU 0–7). Right-click DCS.exe → CPU Priority → Always → High (optional). Right-click DCS.exe → Induce Performance Mode → Enable. Ensure “Disallow ProBalance restraints” is checked for DCS. → This keeps Process Lasso from trying to “help” it later. Throttle background programs For Chrome, Discord, Steam, OBS, Spotify, etc.: Right-click each → CPU Priority → Always → Below Normal Right-click each → CPU Affinity → Always → Uncheck 2–3 cores (e.g. keep them on 0–2 only, leaving 3–7 free for DCS) Optionally add them to IdleSaver or ProBalance for further trimming. Now DCS always owns the fast cores, while background tasks stay out of its cache lanes. Global settings worth enabling In the toolbar → Options → CPU → Disable Hyper-Threaded core pairs for performance → Off (X3D has no SMT issues, keep all threads active) Game Mode → Enabled (lets Lasso auto-boost your chosen process) ProBalance → Enabled globally but excluded for DCS SmartTrim / IdleSaver → optional for laptop/power saving only Verify in the log After launching DCS: process affinity mask: 11111111 unavailable cores: {} means DCS can use every core. Tip: automatic profile import You can export this as a rules file once and re-import after driver or OS reinstalls: File → Export configuration → Check rules only. Summary table Component Recommended setting Purpose DCS.exe All cores (0–7), High priority, ProBalance off Full CPU access Chrome/Discord/etc. Cores 0–2 only, Below Normal Keep background off fast cores Process Lasso ProBalance On globally, but DCS excluded Auto-balances other apps Game Mode On Windows scheduler assists Hyper-V / VBS Off or your choice Lowers latency
  9. Ready
    Set antialiasing to off Set anisotropy to 16 Set MSAA to 0 Changed frametime limiter from DCS to RTSS (RivaTuner) Graphics settings confirmed From the log block: ['AA'] = 'off'; ['MSAA'] = 0; ['anisotropy'] = 16; ['Upscaling'] = 'DLSS'; ['DLSS_PerfQuality'] = 1; ['Scaling'] = 1; ['Sharpening'] = 0.3; ['maxFPS'] = 300; AA = off → DLAA disabled MSAA = 0 → no double-sampling Scaling = 1 → no double-scaling (perfect) DLSS Quality mode active → DLSS now doing all the anti-aliasing and performance balancing Anisotropy 16 → full texture detail (no performance hit on a 4090) Sharpening 0.3 → fine-tuned for cockpit clarity DLSS initialization lines confirm the correct scaling: DLSS successfully initialized, 832x712 -> 1244x1068 DLSS successfully initialized, 968x832 -> 1452x1244 → That’s DLSS Quality scaling for your Varjo Aero (1244×1068 per eye), exactly as expected. Current state summary Area Status Notes AA / MSAA Off Correct DLSS scaling 1.0 Correct Mods Still duplicating Remove AM2, LLH, SAMSites Shaders Recompiling Normal after cleanup Hypervisor Active Disable for latency & CPU scheduling -> I will keep this on for now. Liveries Corrupted Will fix with repair slow Performance setup Excellent DLSS Quality + 4090 + 16x AF = ideal RTSS Not yet verified Set 90 fps (or 89) for Aero -> I have this changed. ----------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------- Hypervisor / Core Isolation: I have tested before the hypervisor and when I disable core isolation my fps reduces by 2.5. what can be the cause? ChatGPT zei: Excellent observation — and very rare insight. If you’re losing about 2–3 fps when you disable Core Isolation / Memory Integrity (VBS), while most users see the opposite, that tells us something specific about how Windows and your Ryzen 7 9800X3D interact with driver scheduling. Let’s unpack what’s happening. 1. What Core Isolation actually does Core Isolation (aka VBS + HVCI) is part of Windows’ kernel-mode memory protection. When it’s on: Windows runs many drivers and kernel services inside a virtualized container using Microsoft’s Hyper-V hypervisor. It slightly changes how CPU privilege rings and interrupts are handled. It often reduces frame rate by 1–3 %, but in rare cases (certain driver stacks or Process Lasso configurations) it can increase stability and therefore produce a small FPS gain. 2. Why you might see a gain with it enabled Here’s what can explain your observation: Possible cause Why it increases FPS slightly Process Lasso affinity masks + Hyper-V’s virtual scheduler With VBS on, Windows’ hypervisor layer forces a more deterministic scheduler; your Process Lasso affinity (cores 3-7) may line up better with DCS’s render threads under that regime. HPET / timer resolution behavior VBS modifies the system timer routing. On some AMD systems it produces steadier 0.5 ms frame intervals instead of micro-jitter, so the average fps metric rises slightly even if latency worsens. Driver-level optimizations New AMD chipset and NVIDIA drivers detect VBS and use different interrupt steering. If the baseline is a “dirty” OS with many background IRQs, VBS can ironically reduce those. Cache residency / security context VBS enforces stricter page table isolation. Occasionally, this results in fewer cross-core cache invalidations for kernel calls, giving small consistency gains on X3D CPUs with large L3 caches. So: it’s not that VBS is faster—it’s just aligning thread timing in a way your system happens to like. 3. How to confirm what’s really happening You can test scientifically: Disable Process Lasso completely (exit it, not just disable control). Toggle Core Isolation ON vs OFF and reboot each time. Run the same DCS track replay and record: Average FPS 1 % low and 0.1 % low FPS (use CapFrameX or MSI Afterburner) CPU package power and thread utilization (HWInfo64) You’ll likely find: Average FPS might dip slightly with Core Isolation off, but 1 % low frametimes will be smoother (less hitching), and input latency drops by ~1 ms. That’s the trade-off: smoother, more responsive feel vs. slightly higher numeric fps. 4. If you want both worlds You can keep VBS off (for latency) but restore its scheduling stability: Disable Hyper-V (so “hypervisor is active” disappears). In Process Lasso, remove any affinity masks so DCS can use all 8 cores. Force Windows Game Mode ON and Hardware-accelerated GPU scheduling ON in graphics settings. In RTSS, cap fps – 1 (e.g. 89 fps for 90 Hz) for perfectly even frame pacing. Optional: use bcdedit /set useplatformtick yes to lock timer behavior (reboot to test). That yields the same frametime smoothness without Hyper-V overhead. 5. TL;DR Setting FPS impact Latency impact My recommendation Core Isolation ON (VBS) +2 fps average, more consistent +1–2 ms slower Fine if you prefer raw fps metrics Core Isolation OFF –2 fps average –1–2 ms faster, steadier frametimes Better for VR and input precision So in your case, you can safely leave Core Isolation on if those extra 2–3 fps outweigh the tiny latency difference — but if you’re chasing VR fluidity and lowest motion-to-photon delay, you’ll still want it off once you use RTSS frame-capping and remove Process Lasso’s interference.
  10. Ready
    Cap maxFPS only if you need frametime stability (RTSS at 90 or 60 can help); otherwise set maxFPS = 0. Your log shows DLSS initialized 1280×720 → 2560×1440 while you also had Scaling = 0.66—that double-scales and harms clarity. Fixing this will both clean the image and stabilize GPU frametimes. ============ This is one of the most common DCS performance traps, especially for users running DLSS (or DLAA) in combination with “Scaling” and frame-rate caps. Let’s unpack what’s happening in your setup and why it matters. 1. What those settings actually do Setting What it controls Where it happens DLSS / DLAA NVIDIA’s AI-based internal rendering resolution and anti-aliasing. DLSS renders the game at a lower res (e.g. 1280×720) and upscales it to your screen (e.g. 2560×1440). DLAA renders at native resolution but uses DLSS’s edge smoothing. Inside the game engine before output to GPU. Scaling (the “Resolution Scale” slider) A second, old-fashioned way to render DCS below your monitor resolution. A value of 0.66 means: render at 66% of 2560×1440 = ~1700×960, then stretch it back up. Inside DCS’s own renderer, before DLSS. maxFPS Optional cap inside autoexec.cfg. It tells DCS not to exceed that frame rate. Frame pacing limiter in DCS (not very precise). RTSS External tool (RivaTuner Statistics Server) that can limit FPS very smoothly at the driver level, often giving steadier frametimes. GPU driver level, after rendering. 2. What your log shows From your dcs.log (snippet simplified): DLSS initialized 1280x720 → 2560x1440 Scaling = 0.66 This means: DLSS itself already renders at half your monitor resolution (720p → 1440p upscale). Then, DCS also reduced the input resolution by another 0.66 before DLSS even got it. → So you’re effectively rendering around 850×480, then upscaling twice: native (2560x1440) ↑ DLSS upscales from 1280x720 ↑ DCS scaling 0.66 makes ~850x480 input That’s double-scaling — your image clarity drops (soft cockpit text, shimmering edges) and frametime variance increases because the GPU is reconstructing too aggressively. It’s like applying YouTube’s “480p → 720p → 1080p” chain — it works, but looks blurry and unstable. 3. The correct way to use DLSS or scaling If you want DLSS (for performance): Set Upscaling = DLSS → Quality Set Scaling = 1.0 Set AA = OFF (don’t add DLAA or MSAA) Optionally use Sharpen = 0.2–0.3 Leave maxFPS = 0 unless you see frame pacing spikes. ➜ DLSS alone will choose the right internal scale (~67% of native). ➜ You get balanced image quality and smoothness. If you want DLAA (for clarity): Set Upscaling = DLAA Set Scaling = 1.0 Set MSAA = OFF This renders at full res but uses DLSS anti-aliasing logic. If you want to manually reduce resolution (older GPUs): Set Upscaling = OFF Then use Scaling = 0.75–0.8 This mimics DLSS Performance but without the AI reconstruction. Never combine both DLSS and Scaling — they’re two different downscaling stages. 4. About maxFPS and frametime stability DCS doesn’t have a perfectly smooth internal limiter — if you set maxFPS = 90, it can still fluctuate ±3 fps and produce micro-stutter in VR. RTSS (RivaTuner) can cap at exactly 90.000 fps or 60.000 fps with consistent frametimes. → That’s why I suggested: “Cap maxFPS only if you need frametime stability (RTSS at 90 or 60 can help); otherwise set maxFPS = 0.” If you’re running VR (90 Hz headset) → cap with RTSS at 90 fps. If 2D monitor 60 Hz → cap at 60 fps or leave uncapped. When you remove the double-scaling, the GPU will already have less load, so you’ll hit higher fps with steadier frametimes and clearer cockpit text. In short Goal Recommended setup Best image DLAA, Scaling = 1.0, no MSAA Best performance DLSS Quality, Scaling = 1.0, no MSAA Low-end fallback DLSS Off, Scaling = 0.75, MSAA Off Frametime control Use RTSS for precise FPS cap; set maxFPS = 0 in DCS
  11. Ready
    Your log shows: Hypervisor is active and Process Lasso is running. Both can impact scheduling/timers. Disable Hyper-V / Virtualization-based Security (Core Isolation/Memory Integrity). This removes the “hypervisor is active” warning and often improves input latency/frametimes. -> I checked my previous log. The outcome of tests #183 and #184 was that disabling core isolation added 2.5 fps. So I will keep Core Isolation ON for now.
  12. Ready
    Why not run my dcs.log through ChatGPT. Here is what it said (after I disabled a bunch of mods to be able to get onto a new server).. Looks like a bunch of old mess. Will go through them one by one and see what the outcome will be. Will share results in next post. -- Got it—here’s a focused, do-this-now plan based on your log. I’ll group fixes by what the log actually shows, starting with the biggest noise makers and stability risks. 1) Remove/disable the broken/legacy mods Your log is flooded by errors from community mods and asset packs. These create conflicts, physics issues (negative drag/weight), and “replace not allowed” spam. Move them out of Saved Games\DCS.openbeta\Mods\ (use OVGME for profiles), then repair DCS (step 4). Mods to remove first (they’re explicitly erroring): VAICOMPRO – not supported and throwing a Lua parse error. Remove Saved Games\DCS.openbeta\Mods\tech\VAICOMPRO. dcs “unexpected symbol” & “not supported”. J-11_Au2th – hard Lua error: attempt to index global 'warheads' (a nil value). Remove Saved Games\DCS.openbeta\Mods\aircraft\J-11_Au2th. dcs HighDigitSAMs / AM2 / SAMSitesAssetPack / LLH_Counter_Insurgency / Insurgent-SF-4x4 – “unit replace … not allowed” + duplicate mounts. These conflict with current core assets. Remove their Saved Games\…\Mods\tech\… folders. dcs Civil Aircraft Mod / Military Aircraft Mod – multiple payload physics errors (negative drag). If you keep them, expect log spam; otherwise remove. dcs Hawk / MB-339 community versions – geometry link errors (“Cell … link loop/self”). These are obsolete versus today’s modules. Remove any community Hawk/MB-339. dcs Result: this alone will eliminate most red ERROR/WARNING lines and prevent mission load weirdness. 2) Fix corrupted/stray livery files F-15E livery .zip fails to open – corrupted archive; a DCS repair will re-download. dcs F-14 livery .gitkeep being mounted as a zip – delete those .gitkeep files in CoreMods\aircraft\F14\liveries\… if you manually added them, or just run a full repair (next section). dcs 3) Clean up texture/font misses Missing texture KevinWakePattern812x1024.dds – likely from a custom livery/ship/water mod. Remove the offending livery or re-install it cleanly. dcs UI font cannot load – indicates a missing/altered dxgui\skins\fonts path; the repair in step 4 will restore it. dcs 4) Run a thorough DCS cleanup/repair (restores core files) After moving/removing the mods above: Close DCS. Open an elevated PowerShell in D:\Games\Eagle Dynamics\DCS World OpenBeta clean\bin and run: .\DCS_updater.exe cleanup (say yes to remove leftovers) .\DCS_updater.exe repair slow (verifies & re-downloads corrupt core files) This will fix the F-15E/F-14 livery issues, UI font path, and any stock file drift. dcs 5) Purge shader caches Delete: C:\Users\Edwin\Saved Games\DCS.openbeta\fxo\ C:\Users\Edwin\Saved Games\DCS.openbeta\metashaders2\ Your log shows the shader caches loading; after large mod churn, rebuild them to avoid stutters. dcs 6) Tidy your audio devices (optional, reduces device spam) You’ve got 9 devices (VB-Cable A–D, ButtKicker virtual, Topping DAC, etc.). Consider disabling unused ones in Windows Sound settings so DCS doesn’t enumerate that many every boot (minor startup savings). dcs 7) Fix graphics settings (you’re stacking AA incorrectly) From your options.graphics dump: you’re running Upscaling = DLSS and AA = DLAA and MSAA = 2 with Scaling = 0.66. That’s a performance & clarity conflict. Pick one path: Path A (best clarity, powerful GPU like 4090): Upscaling: OFF AA: DLAA MSAA: OFF Scaling: 1.0 (remove the 0.66 downscale) Anisotropy: 16x (cheap on 4090) Textures: High; Terrain Textures: Low/Std if VRAM tight; otherwise High This uses native res + DLAA’s high quality edges. Path B (more performance headroom): Upscaling: DLSS = Quality AA: OFF (don’t stack MSAA/DLAA on DLSS) Sharpening: ~0.2–0.3 (you’re at 0.3 already) Scaling: 1.0 (DLSS handles scaling) Cap maxFPS only if you need frametime stability (RTSS at 90 or 60 can help); otherwise set maxFPS = 0. Your log shows DLSS initialized 1280×720 → 2560×1440 while you also had Scaling = 0.66—that double-scales and harms clarity. Fixing this will both clean the image and stabilize GPU frametimes. dcs Other small wins in your current config: Anisotropy 4 → 16 (free on 4090). Forest details 0.1 & clutter 0 are already performance-friendly. Clouds 0 saves GPU; if you raise clouds, offset with MSAA=OFF and DLSS Quality. Windows/driver/system hygiene Your log shows: Hypervisor is active and Process Lasso is running. Both can impact scheduling/timers. Do this: Disable Hyper-V / Virtualization-based Security (Core Isolation/Memory Integrity). This removes the “hypervisor is active” warning and often improves input latency/frametimes. dcs Process Lasso: you’ve constrained DCS’s affinity (process affinity mask: 11111000, unavailable cores {0,1,2}). On a Ryzen 7 9800X3D (single-CCD X3D) you generally want all 8 cores available to MT DCS. Let Windows/Game Mode handle scheduling; in Process Lasso, clear any forced affinities/priorities for DCS.exe. dcs Timer resolution shows 15.6 ms at start; DCS/driver usually pull it down when rendering, but if you run apps that fight timer resolution, you’ll get choppier frametimes. Keep background apps minimal (RGB suites, overlays, browser tabs, Discord hardware accel off, etc.). dcs NVIDIA driver: you’re on 571.96; that’s fine for DLSS. In NVCP set: Power management: Prefer maximum performance (per-app for DCS) Low-Latency Mode: Off (let DCS manage) G-Sync/Freesync: as your monitor supports; then uncap maxFPS or cap via RTSS. 9) Reduce services you don’t use You’re loading LeapMotion, CaptoGlove, SensoryxVRFree, VoiceChat services every boot. If you don’t use them, disable those services via module manager/options to shave startup time and a bit of memory. dcs 10) After the cleanup, re-test and re-enable selectively Re-add mods only via OVGME, one pack at a time, checking the log after each. Prefer actively maintained packs that don’t “replace” ED units. Keep a “vanilla” profile for multiplayer/“pure” servers. TL;DR order of operations Move out the listed mods (VAICOMPRO, J-11_Au2th, HighDigitSAMs, AM2, SAM packs, old Hawk/MB-339, etc.). dcs cleanup + repair slow. Delete fxo + metashaders2. Fix graphics: either DLAA native or DLSS Quality, not both; MSAA = OFF in both cases. Set Scaling = 1.0. dcs Disable Hyper-V/VBS; remove Process Lasso affinities so DCS can use all cores. dcs Optional: prune audio devices & unused services. dcs If you want, upload a fresh dcs.log after these changes and I’ll spot-check what’s left and fine-tune graphics for your exact modules/maps and whether you fly 2D or VR.
  13. Ready
    Good you ask. tbh the results are from what I remember. I just checked my change log in my thread on this forum for the numbers (you can find the link in my sig), I found the MSI-util tests I ran back in december before I did a complete reinstall, but... I see the results themselves were not written down in the log. I think I also ran some tests with the MSI change after my reinstall a couple of months later, but those tests are no mentioned in the screenshots of my log. I see some files dissapeared from the thread, only filenames remain. When I am back at my rig I will see if I can pull them straight from my original excel. With regards to how I measured; I have used various tools and methods for the testing, mostly focusing on frametimes, latency and reducing those irritating microstutters that sometimes tend to appear out of nowhere. In my thread you can read about most of the ups and downs with the various tools. iirc I was focusing on input latency towards the end of the thread.
  14. Ready
    Yup I have had good results with it too.
  15. Ready started following Completed A10CII Outpost official campaign and Completed A10CII Outpost
  16. Ready
    Interesting! Might give it a spin after returning from vacation.
×
×
  • Create New...