Czar

As a nVidia card owner, I find this sad and ridiculous. It is ironic on how much neglect there is on nVidia for VRAM on newer cards and DCS eats VRAM like there is no tomorrow. "Most benchmarks" features games that run on consoles. Your card has only 8gb of VRAM. Try to look at a hardware resource monitor to see if your VRAM is the bottleneck.

Keep your control panel options default. Exceptions are: fps limiter. Turn up your pagefile to 30gb on a fast drive (SATA or NVME SSD). Your DCS log pointed at 9gb pagefile. Run DCS from the 'bin' folder. Your DCS log points at the .exe inside 'bin-mt' being run. That was for the times where Multi Threading was being tested optionally. You don't need to crank up the preload radius. You can give it a try on 60k to 80k range. I find strange to be mandatory a large custom pagefile if you want to run DCS, but it has been the standard practice if encountering stutters on a good system like yours.

At 6:35 : It seems something is off with the chutes and high drag bomb speeds are very slow when in terminal velocity, though. Maybe something changed since your comment.

Flight Simming angels just blessed us with a FF Zero. Just omg! The P-38 AI is also massive news. A plan to make a FF out of the P-38 would be huge. For now, I'm enjoying the Zero A6M5 news. So many other potentially great FF modules too out of that AI list too.

Potentially GOAT mod!!

Tough times for GPUs at the moment. What @virgo47 said is on point. It is better to avoid using the VRAM tips for general games in DCS. It is not only resolution that will scale the usage of your VRAM. DCS has massive assets and textures, unlike the normal videogame that can run on a console, so you'll need VRAM to load the assets 1080p or not. It is one of the main reasons hardware outlets said that 12gb of VRAM on a 3060 was "too much" and not necessary. They don't play DCS or memory heavy sims nor majority of their audience. Textures anything other than maximum is a harsh degrade and not recommended in older modules as the cockpit will become unreadable in everything other than gauges. Getting your hands on a 16gb+ current gen card or nothing is the best way to go with this. Best of luck with the build.

Correct. It is a fire and forget weapon. The H is a "digital TV" guided CCD. This is a classic case for uploading a track for people to see what's going on.

I get it. :)) It would be sublime Nam or Korea. But that south portion of Iraq is taking a while.

They better be working on the unfinished maps instead, though....

I should of been more direct in my previous comment: Just toss the manual file inside 'docs' folder into your phone or any other handheld device >before flight< instead of relying on google (highly degraded search engine), AI (bloat of regurgitated nonsense) or a website. Lack of manual in hand midflight are a user side problem. The files are always up to date in 'dcs' root folder.

More paths for accessibility are almost always nice..... BUT, here is something better: When I was getting back into the Hornet in 2021, to dust off major amounts of rust, I had put the whole manual from it (in 'docs' folder) in my cellphone on a easily accessible folder. Just that. Simple and much better than relying on internet connectivity. I did the same for the Warthog and it was a breeze to get a "bump" ironed out. I'm currently learning the Apache as well and you reminded me of what I did with the Hornet with this thread. Cool ideas. Manuals should be everywhere indeed. Try out putting in a hand held device the .pdf manual you most rely on... or every single one and I'd bet you won't regret it.

I think it is in a different scope or they would 100% already had showcased it. Perhaps in a upgrade down the line.

Sounds good. 1 more addition: "2025-07-30 14:36:08.086 INFO APP (Main): Command line: "C:\Games\DCS World\bin-mt\DCS.exe" Run DCS through the normal 'bin' folder, not the 'bin-mt'.

well... I do a few. Idk if it will help 100%. "2025-07-30 14:36:08.086 INFO APP (Main): CPU cores: 16, threads: 16, System RAM: 65277 MB, Pagefile: 4096 MB" You're running with only 4gb of page file. Increase it to 30gb on a fast drive. <<< probably the strongest clue. Rename your 'DCS' folder in 'saved games' and boot it up in the settings you're having issues with to see if the loading times improve. If it does, there is something on that folder inducing it. If you're running tacview disable it or uninstall it. Make and exception on windows defender of the 'DCS' folder in 'saved games'. Disable any external app that has scripts in the 'DCS' 'saved games' folder. Have a lean system in terms of background apps. No RGB managers or that kind of stuff, those induced trouble for other people as posted here in the forums. Revert any overclock anywhere on your machine if you did. Disable any hardware monitor including MSI afterburner. Others have pointed problems with it and simulators. I use Libre Hardware Monitor (from github) as that app is super lean and quick to manage (open and close).

Since the Fog Update/Patch, there is a Dithering effect (https://en.wikipedia.org/wiki/Dither#/media/File:Dithering_example_red_blue.svg) or a checkered effect on areas that are in shade/shadows or in dim lighting. These are seen at every DCS image from videos and screenshots, raw and edited. The problem gets worse when the images are not displayed on its native resolution making the "pattern" to produce harmonics through the image with the impression of "dark spots". Example being on youtube as well on some videos in any form other than in full screen. It is also present in full screen as well and visible both in game and recordings or screenshots. This is present on any anti aliasing method and highly degrades upscaled output such as using DLSS by other users bug reports. This is a major hit on image quality for any type of DCS showcase. I have saved more images to compare pre patch to post patch if needed.

The F-16C module's left wing features a mesh gap when it flexes and you can see the other side through it. Not livery dependent. It can be seen on first person as well. Additionally, on the left wing, there is also strange warps on its slats and wing geometry leading edge leading up to the wing tip station that is not present on the right wing. Also when it flexes. This is present since I got the module in late 2023.

Against IR missiles also consider cutting the throttle while pulling Gs and dumping flares.

Yeah, I edited my comment out. You were right.

edit: unrelated. Nevermind.

Same here minus the 4 year experience. 1 and 1/2 years for me. At 170kts most of the time with most payloads I just deflect the stick aft a certain amount and at nose up attitude the aircraft always lifts off no issues.

As a nVidia gpu owner that wants options in the (near) future, also there should be FSRAA in the sim. I use DLAA and it is much superior to DLSS as that one wrecks image quality. FSRAA is analogue to DLAA. Both doesn't downscale the image while looking better than MSAA 4x, but with a bit of ghosting, and having the weight of MSAA turned off. You guys should be pushing for FSRAA as well.

Hey, no problem. These kinds of issues actually makes me scared if there is a bug for my next flights like this. I can't think of a solid possibility other than another unit illuminating you for the missile guidance as the Sa-11 is capable irl, afaik. Some script on the mission might do that, not necessarily DCS itself. My plane was tracked by SAM missiles through mountains a few years ago but the issue was fixed, iirc. I was afraid it was it once again.

In a quick test. I got track then a launch warning. Sa-11 Buk "Gadfly" Fire Dome TEL Missile smoke at the right middle portion of the image before those ridges.

Forgot about VR:\ No zoom command there. ED needs to step up the AAR visual references and quality indeed. Best of luck!