WOPR

This may help if you are trying to figure out how to setup your. https://www.digitalcombatsimulator.com/en/files/3315617/

Posting this here because it is related to how some bindings work. Apologies in advance if this not intended for this thread. Volume Increments not on an Axis are too coarse. ICS volume, ALR-67, and probably the radio volumes, when bound to a digital switch, like a rotary dial instead of an analog axis, change values by about 25% on each turn/press. Request this be reduced to about 5% (1/20 of range) or perhaps 10% (1/10 range) at most. JESTER especially needs to be managed a little more precisely at times when you can't use the mouse.

Reducing contrast helps make the nav points legible, but the cost is map legibility.

QNH of 28.89 can not be set for either WSO or pilot.. The numbers jump from 28.88 to 28.90 when incrementing or decrementing the value.

The patch notes state the instructions are in the video. Hopefully, ED will update soon.

AIRIO: JESTER: make marker numbers higher than 10 navigation points. I.e. From: Map Marker <1..10> to [pick your nav target] To: Map Marker <any number> to [pick your nav taget] JESTER WHEEL remains active/available. Long running request. Don't know that is achievable. Not recommended as a high priority. BUG FIX: Have not confirmed in community edition. When communicating with carrier, F/A-18C called by mission editor object number unless 'Force NATO' call signs checked on preferences page. Architecture Enhancement: Figure out how to add the direct commands as a module in saved games vice direct editing of core lua files in install directory. This may not be possible in DCS currently, but the goal is worthy.

Disengage autopilot.

Try to drop the bomb so that falls along the direction of travel of on the road. A transverse drop always risks falling below the bridge and not even hitting a pylon.

Through The Inferno is all PVE (that I know of) servers are also a good place to start and you can download single-player versions of the missions to play off-line if you want.

Assume yes. Case 2 and Case 3 is a heavily managed traffic situation. A controller has to expect to you to be doing something in order to know what to tell you to do.

I don’t know, but I suspect it is. Managing the throttle is a necessity if you want to stay on glide slope with the correct AoA.

The Tomcat has a kneeboard page that shows you your last landing.

It seems like this was supposed to be fixed per the patch notes. However, it persists in MP servers, both the dedicated beta and the traditional versions. It works as intended in single-player.

Do the alignment after you turn it on.

I most certainly can, but making good default keybinds changes benefit far more than just me.

Watch this. I find the settings in this video work extremely well for the Warthog and Thurstmaster TPRs. I suspect they will set you on a good path for other controllers and being able to manage in a hover.

USE LALT+LWIN+<letter|number|other> over LALT+LCTRL+<letter|number|other> to activate the keyboard. Benefits: 1) LALT+LWIN+DEL for clear can now be used 2) LALT+LCTRL+C won't conflict with VAICOM PRO plugin configuration menu.

When using the cyclic stick RTS/Depress, the SWAP button only works on the first row (VHF radio) after the active transmit radio has been changed to a different radio. The RTS rocker switch on the EUFD, SWAP works as expected. The work around is to map the RTS rocker switch to the RTS/Depress button on the cyclic.

Perhaps the real issue is that we're approaching two years since the SC was released to early access and there are some persistent bugs and basic functionality that appear to be lost in the ED development process ether that don't seem like they would take more effort to solve than developing a new ready room (i.e. a way to see deck crew hands in the dark without NVGs or use of landing lights, and the fact that your jet answers everyone else's inbound calls as your jet which creates enormous confusion when trying to get a half-dozen elements on the deck cleanly). Pretty much every developer using the early access model has to be willing to make an enormous investment in asbestos underwear and fire extinguishers to handle less than positive customer feedback. Going silent on progress that customers are asking about only fans the flames harder and asbestos can only protect someone from being on fire for a short period of time. You still have to use the extinguishers by providing the look ahead. Use of neither is pleasant for a bunch of introverted programmers. We're all certain that when the ready room and air boss are available they will be cool because that's something ED does well when it wants to, but the ready room without some critical bug fixes is not what was ever communicated.

Did you run VA as Administrator?

You could just make your human call key-off and then immediately say the VAICOM command for the CVN. Otherwise, you might have to try one of the dynamic switching options, which I would guess don't work well for you. It's a tough integration problem.

I just set VOIP CONTROL to Broadcast parallel in MP options instead of using Tx link or dynamic switching. You can set Allow VAICOM TX Inhibit to off in SRS settings. The attempt to integrate VAICOM better with multiplayer voice is valiant (and appreciated) but has probably been problematic for many.

Logically it should. But you are dealing with code. It may not reset any systems just because you shut down the engines.

Cycling both the left and right generators together often helps with the issues described. Both full off then back on. It won’t work if you cycle 1 at a time.

1. Use https://x51squadron.com/dcs_servers to verify that your server is showing up. If it doesn't there's likely a lot more work to do to determine what's happening. 2. Whether it does or doesn't, verify that both port forwarding and port triggering for DCS are setup correctly. The requirement to setup port triggering depends on your router.