WOPR

The Hornet stick works extremely well for the Hornet (duh), AV-8B, Tomcat, and Ka-50. The only flaw, if it is a flaw, is the down press on the weapon select 5-way switch is a little hard to find until (perhaps even after) you get used to it. I prefer it for space sims as well. The only questions are "is it in your budget?" and "will you use it enough to justify the purchase to yourself?"

Make sure each Pylon is programmed independently, and your HUD says IN RANGE.

My group thought it was because we changed board numbers before launch, but that isn't a factor. CATC appears to be working from the last called board number instead of the actual aircraft board number.

"Clara" definitely needs to have a key bind.

Check the radar display. The range shown it it corresponds to the range of the ACM mode. For vertical scan, the order of steps to enter it matters for reasons unknown. I think ED has stated that is correct as is. The steps are Sensor Select (SS) forward, SS left, then SS aft. JHMICS bore sight mode has 2 ranges, 10 miles and 40 miles. SS Forward long (2 or 3 seonds) triggers long range and SS fwd short triggers "normal" range. JHMICS info shows which mode you are in the lower right portion of the helmet display.

The last Hornet Mini-Update stated are coming in the next release which is essentially a promise. If that wasn't the intent, then words should be chosen more carefully to avoid setting the wrong expectations with customers. Silence on everything but the super carrier and the statement from you "we can not make promises about anything" just leads to the assumptions that ED is not able to keep its development schedule and that ED thinks so little of its customers that it can't be bothered to tell them. It's likely already known which of the 4 features above (and new F-16 features) are going to make the patch. If it isn't known, then someone isn't...well, if ED were my company I'd be making a lot of internal process changes. IMHO, ED just doesn't like to deliver bad news and simultaneously underestimated the complexity of the SC, F/A-18, and F-16, while over estimating its production capacity. My opinion doesn't matter. What does matter is how customers are communicated with. We've seen some positive public relations steps recently and it would be shame to see ED go back to the duck and cover method of delivering news that development goals aren't being met. Complaints will be made no matter what ED does, but clear consistent communication with the right level detail detail will do more for positive customer relations than imagined.

1. Arm the laster. Master Arm On. Set A/G Mode. Set LTD switch to arm (right panel in between TGP & NFLIR switches). 2. On the DDI with the TGP display select "TRIG" in the upper right corner of the display. 3. Choose target. 4. Squeeze trigger (2nd detent I think. It's muscle memory at this point.) to turn on laser. 5. Squeeze again to turn off. LTD/R flashes on DDI with TGP displayed.

If you want as real as possible, there are at least a dozen more parameters that DCS doesn't even consider. A single RCS value doesn't come close to what's required to be realistic.

Given the issues we have currently with the Stennis, it is highly unlikely that it is "just FPS." Net code efficiency and low fps may be contributors, but ED hasn't stopped a release to open beta solely for these reasons in the past that I'm aware of.

Try clicking Sensor select towards your TGP display a couple of times to set up a track atrk or ptrk, sweeten the aim point with TDC. Then TDC depress to designate your aim point for the weapon

One of the main features is 14 spawn points which is not super useful in SP. The other is being able to do something similar to what the Stingers demo so frequently on youtube. Releasing module that is so clearly aimed at enhancing the mutli-player experience as single player seems like a bad move. It may not just be the effort. The bugged trapping video that someone sent me is probably why they are holding and trying to fix the bug. The reaction to a bug like that would be way worse than being late.

The Ford is very different from the Nimitz class. It’s not reasonable to expect that ship or class with this module. It would nice to be to be able to at least put the hull numbers for the entire Nimitz class on the ships even if they are only user skins for the carrier and deck crew and maybe even allow end users to set up different names in the mission editor for the ATC menu.

The CCIP pipper in the Hornet appears to just aim at the ground and not the release point. You have to delay your release to a little past the target based on speed, and release altitude.

May 18th is a Monday. Assuming worst case of a presently unannounced delay of the SC module, Wednesday the 21st is the Wednesday after. My preference is for a good release with good and timely status updates, so personally, I can wait. However it would be nice if ED would confirm or correct the sale end date in the forums so the resultant hate and discontent is based on statements from ED instead of speculation.

RWR is an radio receiver. It can’t determine if a missile is launched. It can only detect radio emissions that are directed toward you, and assign a category or type. Per Wikipedia, TVM uses an Illuminati and is just not smart enough to guide itself. Also, I get S300 and Patriot launch warnings frequently. In DCS, you know when they launch, it just may not always be at you. It could be someone closer to the SAM site than you.

I'm looking forward to the Forrestal and the Super Carrier, but we can still use the Stennis for the Tomcat. It's disappointing, not game breaking.

We don't actually know this to be a fact. I agree it would be silly if it weren't true, but I have noticed different performance with different launch platforms (and like you, I haven't tested with this patch).

Try searching for Aegis and Link 16 (any links would be obliterated due to forum rules). That should answer most of the speculation about what can and can't be done with Aegis cruisers and destroyers w.r.t Link 16. ED doesn't haveto limit Link 16 to a newer destoyer varaint to be credible.

With VAICOM PRO 2.5.16 running, and DCS 2.5.6 and audio redirect enabled, probably my favorite feature, I get the following error message in the DCS log file when loading is stuck at 10% 2020-02-17 20:34:23.506 ALERT Dispatcher: Error starting Game GUI: [string "./Scripts/UI/gameMessages.lua"]:30: module 'lentaMessages' not found: with audio redirect NOT enabled, DCS loads fine.

STEAM is not updating to 2.5.6 because of issues that stop DCS from launching. Many people are rolling back to 2.5.5 because of the issues so while the lack of TGP on the cheek is no doubt disappointing, you may be happier waiting a few days.

DDG-112 was shown in the super carrier promo video. She's a Flight IIA Aegis Destroyer.

I believe there was a hotfix released to fix an immediate issue with logins.

You can do this pretty easily with MOOSE, but I agree that some basic ship formation options with the AI units would be a good thing.

I think the answer is "it depends." We already have the beginning (i.e. needs work) of new CASE I comms on the carrier. For CASE II and CASE III, I believe those are SC module only. I'm not certain if ED has said anything explicit about the LSO for non-owners, but since its integral to the module, it seems unrealistic to expect it.

I try to center the camera's FOV on the LEDs and make sure nothing is blocking the LEDs as you turn your head. I.e. If you have a moveable boom mic in the up position, you may need to move it to the down position to prevent the LEDs from being blocked.