Jayhawk1971

Maybe you can try the link Convexrook posted? That should definitely lead you to the Discord community.

If I click on the link I've provided, it's an invitation to the Vaicom Discord community. What landing page are you seeing when you click on the link?

https://discord.gg/mFjqn4Za

@IronMike Something just hit me (figuratively ) : Assuming that HB and True Grit are going to implement DVI on the Eurofighter, couldn't that underlying voice-recognition technology potentially be used for Jester and Jester's Dad (in the Phantom), as well as Jester's Cousin (Intruder)? I mean, giving verbal commands to your RIO basically is "proto-DVI". Because even if some of the tech savvy people over at the VAICOM Discord find a way to undo what ED has decided to plague us with, I fear this will not be a long-term solution. Edit: overtaken by recent, very promising events. Thanks Vaicom Discord community, and thanks @Hollywood_315 for releasing it under GPL! Still, IMO a native solution directly from the dev would be preferable for these module-specific inter-cockpit comms, because it could be much more "custom" and streamlined. Oh, and could you make the Eurofighter respond to my voice inputs with "By your command!" ?

Weird that it does not seem to work globally, but only for select modules. For me it worked with the Viper and the A-10 II. Haven't tried the Hornet yet. I hope you'll get it to work. I'm still reluctant to completely delete Vaicom from my system, in the (perhaps misguided) hope that either some coding hero finds a solution, or ED sees reason and fine-tunes what I assume was some sort of extremely broad-stroked anti-cheating measure which would restore Vaicom functionality.

Hi Bones, I'm on standalone, not Steam, so I don't know if this would be helpful to you. Anyway, I went into my saved games -> dcs -> scripts folder and edited the export.lua (nothing fancy, just opened it in notepad and deleted the Vaicom entry - I did this every time after a patch, because this prevented the comms menu from popping up again and again in the past). Next, I did a "slow" repair (repair all files). Either one of the two, or both, worked in so far as I can again fully use the comms menu. As long as I don't start Vaicom. Since my Tomcat is grounded for the time being, I've moved on to the Viper and am in the process of re-learning the A-10, and I can do this with the comms menu (even though it's a hassle in VR). I hope someone can fix the Vaicom hook into DCS, soon.

Here you go: https://discord.gg/mFjqn4Za

I hope someone will step up and create something similar. From reading these forums, isn't everybody and their moms in IT? Surely (not Shirley!) someone has the necessary skills to access DCS like Hollywood did.

Slow repair, maybe also deleting the vaicom entry in the export.lua in your saved games - scripts folder is supposed to fix that,

Apparently whatever ED did also affected SRS. Now this is a different league altogether, given the size of the online user base that rely on SRS. Maybe that'll make ED reconsider and revert back? As long as the fix is not something that the creators have to do on their side....

Just been over at the inofficial Vaicom discord, and found this post by Folgers: Anyone know which root folder exactly? Might be worth a try.....

Has anyone checked if Voice Attack is at least working? I have nothing set up outside of Vaicom, and I'm currently running a slow repair. If anyone with an already set up VA profile could quickly jump into DCS and check, that would be great. Thanks for the heads up! Slow repair is still repairing.....slooooooooooooooowllllllyyyyyyyyyyy.

Just started a slow repair myself, because comms menus indeed do not work. Great. Seriously thinking about reverting to 2.7.

Concur. VAICOM completely unusable. Which for me is a big deal, as especially the AIRIO extension was a game-changer, especially in VR. @NineLine @BIGNEWY I realize 3rd party apps don't fall under ED's "jurisdiction", but it would be great if the team could maybe look into what change restricted Vaicom's access to the game and if that change maybe could be reversed, or whether Vaicom users could manually change some lua file to make the software work again. Thanks.

Damn, I don't want to go back to the Jester wheel!!!

Just updated DCS to 2.8, and not I can no longer use AIRIO in the Tomcat. It worked well with 2.7, I did not touch a thing, and did what I always do when applying a DCS patch. It says "Easy comms on" (they're off in the DCS options menu, and every time I try to talk to Jester I get "AIRIO commands not available" (or some such). Does AIRIO work for anyone else after today's patch? If so, what are your settings?

'Twas the afternoon on patchday, when all through the board Not a user was posting, not even a mod; The harddrives were placed in their cases with care, In hopes that St. Wagner soon would be there;

Don't forget

A-6, AI A-6, AI J-35 Draken?

So, since it's not mentioned in the changelog, I assume part 2 of the "Reforger" campaign didn't make the patch deadline? Fingers crossed!!!!!

I can confirm. I've played the mission at least dozen times, and it always went the same way, same time/distance, too. Hence my assumption that you used a trigger zone. It worked like a swiss chronometer.