Fjordmonkey

All of them, if the campaign-maker has a semblance of imagination and is able to create a believable setting for it.

Is it even possible to be a regretful passenger in a Phantom? Asking for a friend

Learn something every day. Thanks!

Even our old AM/BM's with the AFLCC moves the stabs/flightcontrols way faster than they currently do in DCS, and the RNoAF AM/BM's were never updated to DFLCC. Also, from what I remember from my days on the flightline, even the old OCU-birds were quite violent in moving the FLCS during BIT. Glad to see it sped up in the next patch, though.

Will this be an option? For those that don't know what this is, it can be seen used here on a Luftwaffe F-4F. Instead of using a huffer-cart to supply compressed air for engine-start, they use a cartridge-system that inject a jet of high-pressure gas into the engine to spin it up to speed for ignition.

I just went with the latest. No issues with it.

Just make sure your drivers are updated, and you shouldn't have any issues.

Strangely enough I don't have that issue at all, using OpenTrack as an endpoint for SmoothTrack running on an iPad above my monitors. Will check more on this.

Remember that if you're on an AMD-CPU, install the latest chipset-drivers, install KB5006746, and set a Ryzen powerplan in the controlpanel. That solves the early issues people had with Win11 on AMD. Running on the RTM of Win11 now. Zero issues what so ever, small increase in fps (3-5fps average). Your mileage may vary. Ryzen 5 3600, 32Gb RAM on a ASUS TUF B450M mobo. 1660Super 6Gb GPU.

KB5006746 dropped for me today, which fixes the L3-cache latency-issues for AMD-CPU's. Haven't tested things with DCS yet but will do so a bit later today.

An update on my end: I ended up just wiping the entire system due to the framerate-issues in DCS (yes, I AM that level of maniac) and reinstalled the at-the-time latest Beta-build from USB. Since that time I've been happily running Win 11 without any issues what so ever, and even gained 3-7 fps in DCS overall. Usually sitting at between 45 and 50 on the ground in Caucasus and PG, about 40 on the ground on Syria. I don't run VR, so cannot comment at all on how that behaves. Specs: AMD Ryzen 5 3600 on a ASUS TUF B450M-PRO mobo, 32Gb G.Skill Ripjaws V DDR4 3200Mhz RAM. DCS installed on its own 512Gb m.2 NVME SSD, system running on a 256Gb m.2 NVME. ASUS GeForce 1660 Super 6Gb Vidcard, latest drivers. 32" QHD-monitor with a 27" QHD as secondary. No overclocking of any kind. Have had zero issues with other games (Diablo III, Aliens Fireteam Elite, Battletech, Outriders, Elite Dangerous, Star Citizen etc). Haven't done any direct comparisons between framerates from Win10 to WIn11 on any except DCS, mostly since I haven't noticed any issues in the first place. Wiped my workflaptop (HP ZBook 14u G5) and installed the release-build of Win11 on it. Zero issues with any of the workloads I have on it. Take it for what it's worth, but so far I'd have to say that the main differences for me with Win11 are all visual.

I'd say that unless you have a very specific reason to run what's basically a Beta-OS on your computer with all which that entails: wait with installing it until it's released mainstream into the update-channel. Since I'm a mental muppet with less sense than your average broom and a glutton for punishment to boot, I'm running it everywhere I can, even on my daily driver at work

Quick update on my own post: I ended up just wiping the system and installing Win11 from a USB-stick. Couldn't get DCS to function properly before I did, but after a reinstall it works just fine. Got the same or slightly higher framerates with the same settings I used on Win 10, no issues with for example SRS, OpenTrack or other applications I use with DCS.

I've been spending my workday doing something productive so far, namely researching Win11 and framerate-issues in various games. There's been multiple people that have had lower framerates in various games while running Win11. Some have reported that changing/lowering the mouse polling-frequency from 1000Hz helps a lot, plus not running things in Borderless Fullscreen or with VSync on. Another option is to disable the "Send Optional Diagnostics Data" option under Privacy & Security -> Diagnostics & Feedback, so I'll have a gander at those when I get home and report back. If that doesn't work, I'll try nuking the box and reinstalling Win11 from an USB'ed ISO and see if that helps. There's rumors of a new Dev-build coming today and will test that too if it drops before I faceslam my pillow.