All Activity

@Ce_Zeta Thanks! [emoji1303] Sent from my SM-A536B using Tapatalk

Great, thanks. Unfortunately Into the Jungle requires these jurassic mods. I wouldn't ask otherwise. I wish missions would only use most recent mods like Current Hill.

Two WeeksTM

The same issue was observed in the subsequent Oil Refinery Mission, better check all missions that starts from H4 Airport in Jordan.

Странно. У меня работает. Обогрев ПВД?

One of the main problems with the interview is that it seems like it doesn't follow a script, or if it does, it literally skips it... until almost halfway through the interview, it's not bad, but after that, the interviewers keep cutting the interviewee off and don't let them explain. I don't understand why, with these types of interviews, they don't cover key topics, such as their future plans, if there's interest in creating a map or AI units, which modules they'd like to work on, if there's interest in WWII (the Spanish Civil War, for example).... No, they spend almost the last third or quarter of the interview rambling...

Ну да, с учётом радиуса боевого применения самолёта, смысла нет, всё в зоне радиосредств.

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

Excellent! Will be even better when it covers the whole screen! Same to you! Now I'm off to get me the new National Graphic "Top Guns: The New Generation" series!

Something similar happened to me recently, turns out my trial Su-27 module was causing the issue, i disabled the module and dynamic spawn works fine. Maybe try disabling your modules one by one to find out which one is causing the issue

@Ulukaii Many thanks for your response, I will try the simapp software to export the screens. Would I be correct to assume I will have to add a line of script in the simapp for the export of the screens in VR? Another question, has anyone done any mods for the WW super Taurus to integrate into the Open Hornet left console?

Thank you, When I saw the visor thing mentioned in the F16 and F18 changelog, I thought that it must have something to do with it. Went into controls and configured a shortcut to toggle it on/off and.... it worked! Thanks again and have a nice Sunday! Georg

It's the new visor. It was mentioned in the changelog. It's been reported by others. Cheers!

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.

In building a small mission I have been trying to turn the Immortality of Ground Troops off for a short period of say 5 seconds and then back on. I have been using the condition flag of "Is User Flag" and then trying to combine with switched conditions and Repetitive Conditions based on a rocket/rockets in a zone. This is all with normal MB flags and not any code- I am not really good with that side of things. However nothing seems to work out for me. Is anyone to give me any pointers?

Aha! Then I guess the "twisting" of the actual materials actually bend the grip a tiny bit, and probably move the magnet/lever, (I assume it's not a potentiometer being VBK and all). Can you fix it with a deadzone? Sent from my SM-A536B using Tapatalk

Running DCS the CPU maxes out between 40-60 %, while the GPU is usually hovering around 100%, in VR and 2d. But in the game, the in game resource indicator keeps bouncing between CPU and GPU bottleknecked. So, how would I know if a CPU upgrade would improve FPS? Or is it more likely I need a GPU upgrade. The key issue for me is there is occasional stuttering in VR. Upgrading to a AMD platform is not an option due to cost. Thanks for any input.

It's reported. It's the new visor for the F-16C and F/A-18C. It was mentioned in the changelog. Somehow it doesn't cover the whole screen when you have triple screens. Don't know if it is intentional or not. Cheers! Sent from my SM-A536B using Tapatalk

The problem is outside of DCS by the looks of it. If I rotate the AB9 I can see a momentary input in the VK software on the axis for the lever.

Saldy Vibora doesnt provide new info or any Big headlines. It was a good chat between old friends, aviation lovers and simmers. The most important information from the interview is that they really appreciate positive feedback in these forums. One relevant thing is that the owners of Aerges are passionate about aviation and flight simulators. They need money to keep lights on, to make more modules but it is crystal clear that everything is fueled by passion. Vibora is a very well known member of the spanish combat flight sim community involved for more than a decade (he was beta tester for ED prior this adventure for example) and before that he was member of Alas Rojas, one of the biggest spanish squadrons at the beginning of the XXI century (with Escuadron 111). They are still developing the F-1M and good news is the flight model of the F-104G is completed. They are working now in the art part and making alive the starfighter cockpit. They doesn't know yet the next module. Also interesting that F-1M cockpit looks better than the EE one and Starfighter looks also very good (you can see the teaser recorded by Ismael Jorda). A vey interesting anecdote from the podcast is that when they tested the F-1 inside DCS to validate the module, in one test (climb from runway to 60.000 ft) data shown that the Module was more thirsty than his real counterpart. They spent a lot of time trying to figure it out where the issue was. At the end it was found that DCS atmosphere simulation was simplified. From 40k to 60 k air density was the same, so for this reason fuel consumption was much higher in the module. They spoke about the requirements to make a module for DCS. Thats all I can remember.

Thanks chaps. No idea what is happening here. Will keep an eye out to resolve this LG

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.

Auf Discord sind alle am Durchdrehen... Ein Kommentar vom Developer sagte, dass man nicht unbedingt davon ausgehen muss, das die C130 im normalen Update Cycle veröffentlicht wird. Kann also gut sein, dass sie in 1 - 2 Wochen released wird.

I don't have the first, but I do have the 2nd: Here is a link to my copy: IX-514 Keep in mind that this is a 5 year old Mod, so test it to make sure it still works as intended, as I've not used it in a long time.

No, nulla, don't work