WOPR

Mine flew right past the target and never found them. Used "LARGE" for target size, I'm pretty sure the Kuznetzov qualifies for the size.

Agree, but I don't the author truly understands the technology advance of the 4004.

Enjoy a bit of electronics and aviation history. https://www.wired.com/story/secret-history-of-the-first-microprocessor-f-14/

Just sharing because I'm sure there's interest in the topic.

Are you sure your stick is calibrated? I don't get the same results.

Was your NAV/INS set to IFA? If it was set to NAV the drift rate appears to be unrealistically bad and your pod will look at the wrong point.

You have to maintain track on all targets fired on until the missiles go active. It's hard to do this on more than 2, especially if the targets are maneuvering and/or firing at you. I.e. a formation of AI bombers probably the easiest set of targets to do this on. There was a bug that basically caused only the missile aimed at a primary track to be supported, but I think that was fixed.

I will try that. Thanks.

TACVIEW.DLL is the source of the error and that is located in Save Games\DCS. I've run with 100% without trouble with Tacview until I turned on "Controlled Folder Access."

This is just information for someone who might need it in the future. As of TACVIEW 1.8.4 and Windows 10 20H2, if you have "Controlled Folder Access" turned on, TACVIEW will not be able to write an acmi file. You will see Error 29 in the log file and a message stating that tacview.dll can't open the file. I haven't tried real hard to see if there is a configuration that works. The option is under "Ransomware Protection" in Windows settings.

It seems to work in single player, but not multiplayer.

How fast are you pitching up? The Blue Angles have a 40lb pull spring attached to their stick.

I use the detent to tell me where I am on the throttle & prop control. If you have a lift detent, you might try a push over detent. It's a lot more convenient with non after-burning aircraft.

I've never tried to set a WP height for the Harpoon so I won't claim it's not possible. However it seems like the intent is to set the cruise height on the weapon format using "FLT" (from memory, I'm unsure of button label text). Terminal height is always sea skimming.

This is an older video. The TGP doesn't move in ATK or PTK any more. This video explains the basics. and it looks like the Grim Reapers have a recent tutorial video as well.

I confirm this issue. After I switched back to A2G radar and turned off the offending EXP mode, A2A worked normally.

A common cause for this is your AV randomly scanning the ED directory. If you tell your AV software to ignore the DCS directory, the pauses will likely go away.

Just happened to me in a Huey. 2D.

Make sure you aren't in game mode.

Culprit found! I have a saitek trim controller that was assigned to the thrust axis that was overlooked. Close this as no bug/user error.

The F-14 is the only Jet I own that does this, and I believe it is only on the initial start-up. If I respawn, I don't recall seeing this behavior. I tested by disconnecting my throttle and then clicking on the right throttle handle to go from Cuff off to IDLE and the throttle handled moved to the afterburner position. Not likely a hardware issue.

When doing a cold start on CVN-71 (and I think CVN-74 pre-SC release) my throttles jump to full when pushing over the IDLE cut-off detent. Quickly adjusting the throttle a little brings it back down, but it shouldn't jump to full from CUTOFF. Mostly this is a nuisance, but a fix or a quick lesson on how my setup is wrong would be appreciated. Throttle is a Warthog.

Version: DCS 2.5.6.50979 Open Beta From the inside of the cockpit the canopy can be seen no problem. From the outside the canopy is gone. The only symptom was that I couldn't close the canopy. After as I know, the canopy wasn't ejected. The issue was noticed after Jester announce he was closing the canopy and nothing happened. I did a cold start on CVN-71 and told JESTER to start rather than just letting him decide to start.

Another option is to switch the Hornet to True North HSI > Data (upper right) > A/C(upper left) > MAG HDG (center right) This will put a T in the HUD heading tape and I think switch all compass direction indicators to True North (except the backup compass). I haven't tried this personally for your exact case because I tend to fly visually once I get close enough to an airport TACAN (obviously this is only a good strategy in VFR conditions), but it may save you a little trouble. You can use the same format to switch to DMS way point entry as well with LAT LON DCML button in the lower right.

I see the same/similar behavior in the F/A-18 too both before and after the AIM-120 update. The LOST flag appears to be related to something not (directly) related to the missile update. I don't relaunch at long as I have the target in track and am generally successful landing hits (assuming no other factors). I've not paid attention to any differences with TWS and STT. I use both depending on the situation.