Raven (Elysian Angel)

Ideally that would be the case yes. But as I’m sure you’re aware, DCS massively overexposes the view as soon as you enter the cockpit, and because of the lighting changes in version 2.7 the gamma required for a consistent experience now depends on a module by module basis, based on their age and the availability of a working visor. In FC3 and the A-10, anything over 1.6 blinds me. In the F-16/18 I can get away with 1.7 or 1.8. In the F-4 I use 2.1, and in F-15E, OH-58, Mirage 2000 and F1, and now in the MiG-29 as an ED-first I can use 2.2 - because visors correct the overexposure and makes colour representation consistent between external view and cockpit view. This is all in daylight conditions, mind you. DCS’s night lighting is pretty bad so at night and depending on the circumstances I go up to gamma 3.5 for a believable experience.

Would much rather have a properly working visor so we don't have to faff about with gamma any more

They still have until the end of the year before their self-imposed deadline ends:

Oh? I must have missed those, then. And I also never encountered non-AP related pitch oscillations that were not caused by turbulence. I have done pretty much all of my test flights on the Afghanistan map, and never noticed anything like that.

Some adjustments to the default gamma curve would go a long way. Making the Milky Way clearly visible at night over populated areas is indeed not realistic.

For what it’s worth, I mostly keep TelemFFB at its default values. The only things I change are: - untick “deceleration effect”, because I don’t like it; - change the G at which the maximum force applies from 7 to 9; -untick afterburner rumble, because I don’t like that effect and don’t need it; - and obviously I also tell it which configuration profile to use for each module.

IRL it was the main reason that Su-33 didn’t really take off (tee hee) as a carrier-based fighter: it was too heavy for a non-catapult assisted launch while carrying any useful load-out. MiG-29K was far more popular for that reason. But as someone stated earlier, if you let it operate from land that restriction disappears obviously.

That’s because Sparrows are not using the latest version of the API (yet?). I can confirm though, that flipping the anti-interference switch to the Up position is hugely beneficial and I have been getting 1-shot-1-kill success with my R-27s

I never had that error before. I'll reboot into BIOS and see exactly what I have disabled: I'll try to post a picture here. EDIT: This is what it looks like for me. Obviously I have an AMD system so things look a bit different and have different names, but I believe they are the same: SVM is needed for VBS to work in Windows (I have W11 Pro), so that's enabled. SR-IOV is needed for virtual machines, which I don't need and is thus disabled. Everything else related to virtualisation is left on auto/default.

I have that one particular option disabled in BIOS too. Other virtualisation options in BIOS however are needed in case you want to enable VBS (virtualisation based security) in Windows, which is highly recommended.

Some of the most decorated / famous test pilots are/were “old farts”

That sounds like you swapped the hardware without reinstalling windows? AMD CPUs require very different things from the windows scheduler than Intel CPUs. When doing a complete reinstall, it’s very easy to forget something in windows, so I’m just making sure

I’m not undervolting, so it’s just the default settings. My temperatures stay low because I can hear that by the sound level of the fans. I have a custom fan curve that lets them speed up when the temperatures reach high levels but that doesn’t happen in DCS (other than due to a bug a while ago that was fixed).

I take it you also added exclusions for all DCS folders (both main folder and saved games) in your antivirus software, and are making sure no other processes interfere while gaming/simming? Have you debloated Windows and made sure the amount of processes running stays at a minimum required level, without stuff running in the background that’s not needed?

Yes, there is. The difference can be “just” 10% but can also be quite massive. Even 10% is well worth the effort of doing a fresh install, in my opinion. 24H2 was a pretty substantial upgrade for AMD CPUs, and for me there was a very noticeable difference between upgrade and fresh install.

I haven’t checked in a while. While gaming CPU temperature is around 45-50 degrees, and GPU 70-75. I haven’t done any stress tests since I built the system, and I don’t remember temperatures. I use a 420mm AIO and my case is packed with 140mm fans so temperatures stay low even at low fan speeds, so I can keep the noise down. What do you mean by curve value? Fan curve? I keep my fans between 300 and 600rpm. More is not needed.

Funnily enough that’s exactly why X3D is that good: when I upgraded from a 5900X to 9800X3D, my minimum framerate in various games went up by as much as 50-60%. I also play ARPGs sometimes, and that’s another genre that X3D is particularly suited for: the increase in performance was eyewatering (and I kept my graphics card so in all cases the increase in framerate is 100% due to the CPU). I personally don’t have stutters in any game. DCS can sometimes do weird stuff but that’s when ED messes something up. But they also fix it

As far as I know, the only real problems (on a hardware level) that you could have with a 9800X3D is when you have an Asrock motherboard. Which brand is yours? Indeed I saw in your original post that you already tried a lot. Are you using the latest BIOS version (there are regular stability updates with newer AGESA versions), and the latest chipset drivers? Are you sure all BIOS settings are correct, and not causing desynchronisation issues? Did you try disabling the Power service in Windows? I myself don't need to do that, but a lot of people are recommending it as it can potentially fix stuttering.

Stuttering is one of the most common problems experienced in DCS, and one of the most difficult to properly diagnose. Unless you get lucky, it's a problem that simply throwing money at won't fix. Did you do a search here on the forum and read all other threads about people complaining about stuttering, and how they managed to fix it on their end? It doesn't necessarily mean that their solution will work for you too, but it's worth a try.

That's entirely up to you, but that would be a serious downgrade (X3D is hugely beneficial for flight sims). My guess is that there's something going on that doesn't have anything to do with hardware. If there were issues with the 9800X3D itself, I'm sure you'd see a lot more people complaining about it here on the forum

Not just the graphics, but the level of fidelity in flight models and systems too! We're truly living the dream, in the golden age of flight simulation!

I think implementing a system that credits you for manoeuvre kills won’t exactly be a trivial task. How do you determine what is a manoeuvre kill and what isn’t? Can that be easily defined using language that a computer understands? From what I hear, getting credit for manoeuvre kills in real life isn’t trivial either.

If you believe in yourself, you don’t need external validation