WOPR

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.

I don't think we yet have the burble for the Hornet, and don't forget it is fly-by-wire. Getting good at flying the F-14 makes you a better Hornet stick. The opposite is not true.

That is cool. We used to have a retired RF-4 pilot in our group. Hope he's excited about this too.

I agree it is not, but it is still a better fit than the Mud Hen.

AV-8b + South Atlantic is a more logical bundle. Although it would be awesome to get a little better price by both the Mud Hen & SA map at the same time.

This is the best tool for setting up your throttle curve with a detent. Just follow the directions. You won't regret it. https://www.digitalcombatsimulator.com/en/files/3315617/?sphrase_id=10089453

I think the max "spec" number is 18. However, it varies some with the number of static objects on the deck. Spawn points vs. deck configuration is in the SC manual. Throwing the Tomcat into the adds to the complexity and you will likely see problems. The Tomcat, takes more space than the Hornet with wings swept full and there are (have been?) some desync issues which cause some problems, like collisions caused by wings that are spread on one client and not another. and sometimes the Tomcats have trouble finding spawn positions. I don't know what the maximum is.

Try forcing your installation directory using the "Use custom DCS path" check box on the config tab of the settings box.

Has anyone heard from Hollywood since the end of November? His last login was Nov 29, 2020.

Not forcing any call signs or ATC names.

Oldish issue, newly isolated. I am unable to find a post about this issue. Conditions: VAICOM PRO (any recent version including the most recent), All addons, flying in the F/A-18C Hornet. Issue: AWACS calls Hornet by Unit Number - not flight call sign. I.e. AWACS refers to jet as "1711" vice "Doge 1-1" or similar. I ran a repair on DCS and didn't fix VAICOM PRO and the problem disappeared. Had friend confirm the issue for me. The issue doesn't exist for other aircraft. I have been running VAICOM PRO for a while so it could be that the export files never updated as intended for something else. All the files in my export directory are dated 06 JUNE 2020 which means that they are likely not up to date, especially for the new Hornet call signs.

How about reflective patches on gloves, just like what is already on the vests, so we can see them at night without having to turn on landing lights or resort to NVGs? It seems like this could be done as a stop gap (in 2 weeks ).

It might be in the Smithsonian archives. The SI is a notorious collector of such things and they have one in the Udvar-Hazy annex. https://airandspace.si.edu/collection-objects/republic-f-105d-thunderchief/nasm_A19820064000

Wags updated the Viper roadmap today. I think we're overdue for an update, especially since we're near the end of 2021 and there are features that were supposed to be done in 2020 that aren't, regardless of "how minor" they may or may not be.

Close this one to error. I remapped the switch I use to the fuel probe incorrectly after the controls wipe for this patch.

Approach - plug in - hear "your taking fuel" watch your fuel gauge. Sanity check the plug - you aren't really plugged in, you're just close. No fueling happens. Probe never actually mates to the basket.

Try adding TACAN, and possibly Link, and possibly the phrases "TACAN tune" and "Link Tune" to your speech recognition dictionaries. For example TACAN could be recognized as "tack and". I set it up recently but really haven't tested it yet. How to add words to windows speech recognition

Until/if the commands are available (I don't know what Hollywood's plans are), you can use the JESTER OPTION command to pull up the wheel, and then use "Take <number>" to get to the wheel position you want. It's a little awkward, but it does work.