some1

Yes, just like other helicopters. Both to one axis, or separate axis for each one.

Immersion is great, all the detail in the cockpits, NVGs sticking out on the hemlet, the eyepiece. FPS is similar or slightly worse than Mi-24, so not great, but nothing surprising. However, that's without PNVS. Turning on the infrared image on the eyepiece makes it considerably more demanding on the hardware. Easily the most demanding module currently in DCS.

Maybe because Razbam also talked about making another Harrier variant (which hasn't materialized yet), and they also talked about making another MiG-19 variant (which hasn't materialized yet), and they also have the longest backlog of unfinished and unreleased modules of all DCS developers. So let's wait for F-15E to be released and brought to a more or less complete state, before asking for a yet another toy added to the collection.

In terms of aircraft design that's basically concurrent development. Especially taking into account different manufacturers, different military communities and even different branches.

The first A7s did not have such a fancy HUD like we know from the upgraded D and E models. The F14 suffered from protracted development and budget cuts. The F14A, instead of being inertim configuration of the first few dozen units, became the main variant for the whole cold war and beyond. Also HUD is not a super high priority if the aircraft primary role is lobing BVR missiles.

It's already there in the game, called "UFC INTEN inc/dec".

Broken https://forums.eagle.ru/topic/267540-f5-radar-gunsight-solution-incorrect

This is a forum for bugs, isn't it?

The TMS left long and TMS right long functions activate only after you release the button, it's the same problem as the Hornet issue described here:

TGP FLIR/CCD toggle has been fixed, but HMD LACQ activation (hold Sensor Control Switch forward) is still bad.

Nope, at 30,000 feet -47 does not have enough energy left when launched from 30 nm. The AI outmaneuvers it every time.

I did a few practice engagements against an AI Flanker at 35'000 feet recently, and did not really see much guidance problems, most often a single mk.47 missile launched from 30 nm scores a hit. It may have something to do with how AI responds to my actions, as in my case it's pressing with attack, and fails to beam or outrun the missile. Tacview-20220217-210410-DCS-bvr_F14_LR.zip.acmi Tacview-20220217-210658-DCS-bvr_F14A_LR.zip.acmi

The currently imposed limits when running decades old parts in an airframe worth millions during peacetime should not even be a factor in this discussion. Two different worlds, literally. They don't fly them at WEP any more either.

That still works differently. PD-STT + ACM cover up - missile won't go active. P-STT + ACM cover up - missile will go active. Also, how about making Jester switch to P-STT when we flip the cover? Or making him a bit more conscious with switching from doppler to pulse? As it is now, he's useless and 80% of the time simply looses track of the target in the process. notactive.trk active.trk

Worse. Heavier and has more drag. It will be able to carry aim-9x, so that will even things a little, but no HMD for the pilot.

With pilot body: L39, C101, Fw190D, Bf109, P47, P51, Spitfire, Mig15, F86, F5, AJS37, AV8B, M2000, FA18, Su25, Su27, Su33, Gazelle, UH1, Mi8 Without pilot body: I16, Fw190A, Mosquito, Mig19, Mig21, A10, F14, F16, JF17, F15, Mig29, Mi24, Ka50

You can always close one eye as a workaround, that's what you would have to do with the real thing anyway.

Same. X10 view is wrong. (G2)

In most cases too hard to justify doing it for free, and too easy to justify selling them as a separate product.

He wrote he doesn't play multiplayer, so it doesn't matter how many years of MP experience you have. I also did not write about DCS memory usage, or the "in use" value, but total committed memory. That's what's important in relation to pagefile - when committed memory exceeds physical memory available, pagefile starts being used. Want to really see how much of pagefile is really being used, you can always do that with built in system tools https://support.tilaa.com/hc/en-us/articles/228651847-How-to-see-swap-pagefile-usage-in-Windows-

Not really. It comes into play if committed memory exceeds the amount of physical memory. In this case, if the pagefile is too small, Windows will start to increase it and shuffle things around, so it can stutter for a while. An if the upper pagefile limit is still too small, DCS or something else in the system will crash. For a guy with 64 GB ram playing SP, a 32GB pagefile is simply overkill. I mean sure, it's a safe support answer, worst case scenario it will just waste some free space on SSD.

From my experience playing with large pagefile won't help in this situation. Sure, setting a pagefile to a fixed size won't hurt, but the RAM is not the problem, the problem is that the GPU gets hammered by F-14 model and textures. The only solution is to dial down pixel density and/or Steam supersampling setting, whichever you choose, to give GPU more headroom.

This gentleman will gladly sell you an F-4E with 9Ms, a year supply of argon and a free complimentary load of chaff and flares

Many pedal designs do not return exactly to centre. It's typical for cam based models that have no centre detent. I have a joystick with no centre detent and the same problem with autopilots in other aircraft. They sometimes refuse to engage simply because my stick is not dead in the middle position.

That would require you to have a deadzone in the hardware or in the DCS curves, otherwise the AP would never activate. But the adjustable AP deadzone as an option in special settings tab would be the best.