Vaicom no longer recognizes F-14 after DCS 2.8 update

[MAXsenna]

4 hours ago, Goliathus said:

It is not ED's responsibility to manage their updates in a way that no other third parties mods will be affected.

In a way it is their responsibility to not remove or lock down working features without being honest and transparent about it. This has nothing to do with "updates". Nothing in the game changed for the better for us users. No new features or similar that's related to this. 

Seems everybody has forgotten they did exactly the same a year+ ago. VAICOM, exports etc. stopped working in MP as an anti-cheat feature. I'm willing to put money that the same thing happened now. 

[bonesvf103]

Thanks Jayhawk.  Wish me luck.

 

Some of the problems people reported, I for some reason have not experienced.  No matter how many patches were done, I always got a comms menu, this is my first time losing it.  But you and others have.  That's curiously interesting.  Other people said that while using Vaicom they could access the Jester wheel, and either see a flash of it or see it in another screen.  I never have had either happen.  I could hear the radio chirp and feedback as if the Jester wheel was on but I never got any screen flicker or another wheel elsewhere etc.  Odd that I have such varying (and at that moment, beneficial) results when using my Vaicom Pro compared to others.

 

Hmmm

 

v6,

boNes

[bonesvf103]

Well I deleted the Vaicom Pro line in the export.lua and I did an integrity check, but still no comms menu in the Hornet.  Works fine in the Tomcat though, and even in the Falcon!

 

v6,

boNes

[BMGZ06]

2 hours ago, bonesvf103 said:

Well I deleted the Vaicom Pro line in the export.lua and I did an integrity check, but still no comms menu in the Hornet.  Works fine in the Tomcat though, and even in the Falcon!

 

v6,

boNes

You cant just delete and not delete all traces of vaicom as well or it will just rewirte that code again. You have to comment it out by putting 2 dash marks in front of the code and saving it. Then go into voiceattack options in the general tab and uncheck allow plugin support. Then after that is done run a quick repair. I did not need to do a slow full repair. Dont those 3 things worked for me.

[cdjung1]

This problem may be across the board. Same issues with the Hornet, no comms menu at all. I took a break from DCS waiting for the update and now without Vaicom Pro or a working comms menu the sim is effectively broken. For me Vaicom Pro is essential, as without it you have to wade through the awkward comms menu which takes too much time and breaks immersion. I struggle with aerial refueling if I have to fiddle with menus and many other tasks. JTAC with the menus is a nightmare.
 

I’m surprised to hear Vaicom is not being updated any more without word from the dev, it is very unlike him given the tremendous support he has given the community for many years. Has anyone tried to connect with Hollywood directly to confirm the program is no longer supported?  I’ll try to ping him and see if I can get a response. 

sad day for DCS

[Jayhawk1971]

vor 4 Stunden schrieb bonesvf103:

Well I deleted the Vaicom Pro line in the export.lua and I did an integrity check, but still no comms menu in the Hornet.  Works fine in the Tomcat though, and even in the Falcon!

 

v6,

boNes

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.

 

 

[bonesvf103]

1 hour ago, BMGZ06 said:

You cant just delete and not delete all traces of vaicom as well or it will just rewirte that code again. You have to comment it out by putting 2 dash marks in front of the code and saving it. Then go into voiceattack options in the general tab and uncheck allow plugin support. Then after that is done run a quick repair. I did not need to do a slow full repair. Dont those 3 things worked for me.

Well what I did actually was take the original lua and rename it export.lua.bak.  Then I deleted the line and saved the whole thing as export.lua.

Even after the integrity check and running DCS and Voice Attack and factory resetting Vaicom Pro preferences and unchecking plugin support in Voiceattack settings, it still worked for every aircraft except the Hornet.  When I llok at that export.lua file, no Vaicom code has been written to it.

So, I dunno why it only affects the Hornet.  I'm trying one more integirty check and restart and trying again.

v6,

boNes

[bonesvf103]

And...nope.  Still no Hornet comms menu even though I did what BMG and Jayhawk suggested.

v6,

boNes

[Oceandar]

Thanks to this thread I simply disable Vaicom script right after update and never open Voice Attack. I don't have problem with DCS comm.

What happened with Hollywood? Is he ill or something. Someone from Netherlands probably willing to contact or even visit him.

Sent from my SM-A536E using Tapatalk

[bonesvf103]

Tried other things but still, the Hornet is the only one where the comms menu does not come up.  I am out of ideas, any other ideas to fix this?

 

v6,

boNes

[dburne]

12 hours ago, cdjung1 said:

This problem may be across the board. Same issues with the Hornet, no comms menu at all. I took a break from DCS waiting for the update and now without Vaicom Pro or a working comms menu the sim is effectively broken. For me Vaicom Pro is essential, as without it you have to wade through the awkward comms menu which takes too much time and breaks immersion. I struggle with aerial refueling if I have to fiddle with menus and many other tasks. JTAC with the menus is a nightmare.
 

I’m surprised to hear Vaicom is not being updated any more without word from the dev, it is very unlike him given the tremendous support he has given the community for many years. Has anyone tried to connect with Hollywood directly to confirm the program is no longer supported?  I’ll try to ping him and see if I can get a response. 

sad day for DCS

 

Pretty sure several of us have tried to no avail. Messages go unread.

[MAXsenna]

12 hours ago, bonesvf103 said:

And...nope.  Still no Hornet comms menu even though I did what BMG and Jayhawk suggested.

v6,

boNes

Hi Bones! Can you find DCS in your Steam apps and look in the scrips UI Radiosomething, and tell us the size of the Radiosomething file? It should be like 66KB.

And not sure if you did integrity check last. 

(Don't remember if anyone or you mentioned above what keybinds you use in the Hornet. Should be RAlt + \ and RCtrl + \). 

[zyph3r]

Very sad! It really kills the immersion with the Tomcat

[bonesvf103]

3 hours ago, MAXsenna said:

Hi Bones! Can you find DCS in your Steam apps and look in the scrips UI Radiosomething, and tell us the size of the Radiosomething file? It should be like 66KB.

And not sure if you did integrity check last. 

(Don't remember if anyone or you mentioned above what keybinds you use in the Hornet. Should be RAlt + \ and RCtrl + \). 

Hi MAXSenna thanks for trying to help me.

 

My RadioCommandDialogsPanel.lua file is 61 kb.

I pretty much have been doing an integrity check everytime I have tried to change something, and sometimes just for the heck of it.

 

My keybind for the comms menu in the Hornet is \.  I checked it in the controls section and everytime I hit \ in the control set/selection it does display "Communication menu."  This is also what used to work for me before Vaicom Pro died.

 

v6,

boNes

[MAXsenna]

Hi MAXSenna thanks for trying to help me.
 
My RadioCommandDialogsPanel.lua file is 61 kb.
I pretty much have been doing an integrity check everytime I have tried to change something, and sometimes just for the heck of it.
 
My keybind for the comms menu in the Hornet is \.  I checked it in the controls section and everytime I hit \ in the control set/selection it does display "Communication menu."  This is also what used to work for me before Vaicom Pro died.
 
v6,
boNes

Try RAlt + \ when in the air.

Sent from my MAR-LX1A using Tapatalk

[bonesvf103]

Just now, MAXsenna said:

Try RAlt + \ when in the air.

Sent from my MAR-LX1A using Tapatalk
 

Nope it didn't work.

 

v6,

boNes

[Ramtin]

14 hours ago, Oceandar said:

Thanks to this thread I simply disable Vaicom script right after update and never open Voice Attack. I don't have problem with DCS comm.

What happened with Hollywood? Is he ill or something. Someone from Netherlands probably willing to contact or even visit him.

Sent from my SM-A536E using Tapatalk
 

Is the developer from the Netherlands? I live in the Netherlands but without a phone number or adress there isn’t much I can do.  

[bonesvf103]

Followup:

MAX, your suggestion gave me an idea.  I went back into the control settings menu and looked for the comm1 and comm2 radio instead of the communications radio.  I found that there was a keybind for com1 mic switch set to q and for comm2 mic switch set to RCTLR+\.  HIttineither on the keyboard brought up comms1 and comms2 menu respectively.

 

Now why \ doesn't work for a comms menu I don't know but I suspect that with Vaicom Pro it must have understood it to work, but without it doesn't. I think before I had Vaicom Pro years ago I had set Q and LCTRL+\ as my mic buttons...and maybe I just forgot about it being spoiled with VAicom Pro.

 

So, I think it is working that way anyway and I will just have to reassign my HOTAS buttons.

 

I'll let you know if there is anything further.

 

Thanks!

v6,

boNes

[bonesvf103]

And actually to follow up on THAT, I checked my HOTAS and it looks like I do have those keybinds mapped to the right buttons, but I have them listed as VAICOM Pro TX2 and TX1, so I must have years ago set them to VAICOM Pro's TX1 and TX2 for DCS to recognize.  Years of using the HOTAS to use comms rather than the keyboard made me forget this.  SO without BAICOM Pro, I went to using the keyboard, expecting the default would work when I should have been using Q and LCTRL+\.

Although, since comms menu is bound to the \ key, I dunno why THAT wouldn't bring up a comms menu, unless there isn't one in F/A-18C per se, but then, why isn't it listed.

Maybe will always be a mystery, but as long as I have my comm1 and 2 back, I don;t think I care.

 

Thanks for prodding me in the right direction.

v6,

boNes

[MAXsenna]

And actually to follow up on THAT, I checked my HOTAS and it looks like I do have those keybinds mapped to the right buttons, but I have them listed as VAICOM Pro TX2 and TX1, so I must have years ago set them to VAICOM Pro's TX1 and TX2 for DCS to recognize.  Years of using the HOTAS to use comms rather than the keyboard made me forget this.  SO without BAICOM Pro, I went to using the keyboard, expecting the default would work when I should have been using Q and LCTRL+\.

Although, since comms menu is bound to the \ key, I dunno why THAT wouldn't bring up a comms menu, unless there isn't one in F/A-18C per se, but then, why isn't it listed.

Maybe will always be a mystery, but as long as I have my comm1 and 2 back, I don;t think I care.
 
Thanks for prodding me in the right direction.
v6,
boNes

VAICOM doesn't use keybinds, only the TXs you've configured. But I might have misunderstood initially.
VAICOM is broken, needs to be removed or shutdown VoiceAttack. Then shutdown DCS, do a full repair, and start up DCS without starting VoiceAttack. Then you should be good to go.
Anyway. ED changed behaviour in some modules a while back so "\" is only for ground comms/intercom, but I haven't testet in the Hornet, so it might still work there.

Sent from my MAR-LX1A using Tapatalk

[bonesvf103]

Yes that's what I was trying  to say.  My Q keybind for COM1 is set to Vaicom TX1 and my RCTRL+\ for COM2 is set to TX2 in Vaicom.  I've been so used to doing Vaicom after I set this that now that I suddenly don't have Vaicom, I have to realize that I can still use my HOTAS to key the mic since it is going to DCS now not Vaicom then DCS.

But since \ was set in DCS, even with Vaicom Pro gone, I don't know why DCS ignores my \ keystroke whereas in any other plane DCS does not ignore it.  That part makes no sense.

And since there is no Vaicom, in theory it shouldn't matter if I had to vaicom line in that lua or not since my HOTAS buttons emulate a keystroke.  With Vaicom working my keypress would be intercepted by Vaicom and understood as TX1 or TX2 and then would pass my command on to DCS for COM1 or COM2.  In theory wIth Vaicom or even Voice Attack off, I can leave the code in the .lua since it wouldn't apply since neither would be on.  My HOTAS keypress would then go to DCS rather than Vaicom first, but it would only bring up the menu and then I'd have to hit a function key to relay my command since Vaicom won't take my voice command and translate it into a DCS command.  Which would suck, but that was what was so good about Vaicom Pro.  I didn't have to hit F5 for ATC then F1 to ask to taxi.  I could just hit TX1 or TX2 and say "request taxi" and it would bypass all the keystrokes for me and issue the command.

 

I will definitely miss Vaicom Pro.  I hope it comes back fine.

 

I guess I can switch to Bailey's profile but then I would definitely have to comment out the Vaicom Pro line and re-check on the "allow pluug-ins" option in Voice Attack, I think.

But for now I can work with the Jester wheel and the comms by keystroke.  It will jsut take me more time to look for/choose the command, which will suck in the heat of battle/

v6,

boNes

[MAXsenna]

Hi @bonesvf103 I apologise in advance because I don't mean to come off as a smart ass, but this is just not how it works. DCS does not send keybinds to VAICOM which then relayes it to DCS. 

But that's sort of besides the point. VAICOM alteres various files in DCS core, where one hides the menu. That's the problem. It's invisible. If you remember the F sequence, you can try to press a comm key and then press the sequence, but I have a feeling it might not work. 

Some guys in the Discord are trying to make a fix, so cross your fingers and pray to your boss deity!

Cheers! 

 

 

 

[ricktoberfest]

1 hour ago, bonesvf103 said:

Yes that's what I was trying  to say.  My Q keybind for COM1 is set to Vaicom TX1 and my RCTRL+\ for COM2 is set to TX2 in Vaicom.  I've been so used to doing Vaicom after I set this that now that I suddenly don't have Vaicom, I have to realize that I can still use my HOTAS to key the mic since it is going to DCS now not Vaicom then DCS.

But since \ was set in DCS, even with Vaicom Pro gone, I don't know why DCS ignores my \ keystroke whereas in any other plane DCS does not ignore it.  That part makes no sense.

And since there is no Vaicom, in theory it shouldn't matter if I had to vaicom line in that lua or not since my HOTAS buttons emulate a keystroke.  With Vaicom working my keypress would be intercepted by Vaicom and understood as TX1 or TX2 and then would pass my command on to DCS for COM1 or COM2.  In theory wIth Vaicom or even Voice Attack off, I can leave the code in the .lua since it wouldn't apply since neither would be on.  My HOTAS keypress would then go to DCS rather than Vaicom first, but it would only bring up the menu and then I'd have to hit a function key to relay my command since Vaicom won't take my voice command and translate it into a DCS command.  Which would suck, but that was what was so good about Vaicom Pro.  I didn't have to hit F5 for ATC then F1 to ask to taxi.  I could just hit TX1 or TX2 and say "request taxi" and it would bypass all the keystrokes for me and issue the command.

 

I will definitely miss Vaicom Pro.  I hope it comes back fine.

 

I guess I can switch to Bailey's profile but then I would definitely have to comment out the Vaicom Pro line and re-check on the "allow pluug-ins" option in Voice Attack, I think.

But for now I can work with the Jester wheel and the comms by keystroke.  It will jsut take me more time to look for/choose the command, which will suck in the heat of battle/

v6,

boNes

Bailey's doesnt require a plugin.  Its entirely VoiceAttack 

[bonesvf103]

9 hours ago, MAXsenna said:

Hi @bonesvf103 I apologise in advance because I don't mean to come off as a smart ass, but this is just not how it works. DCS does not send keybinds to VAICOM which then relayes it to DCS. 

But that's sort of besides the point. VAICOM alteres various files in DCS core, where one hides the menu. That's the problem. It's invisible. If you remember the F sequence, you can try to press a comm key and then press the sequence, but I have a feeling it might not work. 

Some guys in the Discord are trying to make a fix, so cross your fingers and pray to your boss deity!

Cheers! 

 

 

 

I should have been more clear.  What I meant was my HOTAS sends keystrokes to vaicom not DCS.  ie, I hit my HOTAS mic button, and my HOTAS sends Q which is what Vaicom Pro sees and knows to take whatever I say and match it with a DCS command and then sends that command to DCS.

 

And I didn't think you were being a smart ass, nothing to worry about there.

v6,

boNes

[MAXsenna]

I should have been more clear.  What I meant was my HOTAS sends keystrokes to vaicom not DCS.  ie, I hit my HOTAS mic button, and my HOTAS sends Q which is what Vaicom Pro sees and knows to take whatever I say and match it with a DCS command and then sends that command to DCS.
 
And I didn't think you were being a smart ass, nothing to worry about there.
v6,
boNes

So, what happens when you press "Q" on your keyboard?
Why have you set it up like this? This is far from what the manual tells you do I'm not sure this is really what you've done.
Are you sure you haven't added your HOTAS in VoiceAttack, and configured one of the buttons for a TX like the manual describes how it should done?
What software do you use to make the HOTAS send the "Q"?

Sent from my MAR-LX1A using Tapatalk