VAICOM Pro not working so well with Fw190D9

[streakeagle]

If I play without VAICOM and use the ingame radio menu, everything works fine. If I have VoiceAttack/VAICOM in use, the Fw190D9 cannot use many if any radio commands.

 

I am going to guess that this is because some aircraft like the Fw190D9 have different comm menus than most other aircraft. For example, the call to "engage bandits" requires different keystrokes/menu options in the game. It really would have been nice if ED had stuck to identical comm tree layouts and just skipped branch numbers that didn't apply to specific aircraft types, but they didn't and it is not an option to mod the core game.

 

My solution to this using my old free Shoot voice command software was to have separate profiles for each aircraft (or class of aircraft) to accommodate the comm menu tree variations.

 

But with VAICOM Pro, I don't see anything I can easily edit within the voice attack profile, and I don't know a way to customize the plugin to make it work with WW2 aircraft, and even if I did, I would need to have an alternative modded plugin to support the odd aircraft.

 

Has anyone else encountered this and have a fix for it?

[hornblower793]

If I play without VAICOM and use the ingame radio menu, everything works fine. If I have VoiceAttack/VAICOM in use, the Fw190D9 cannot use many if any radio commands.

 

 

 

I am going to guess that this is because some aircraft like the Fw190D9 have different comm menus than most other aircraft. For example, the call to "engage bandits" requires different keystrokes/menu options in the game. It really would have been nice if ED had stuck to identical comm tree layouts and just skipped branch numbers that didn't apply to specific aircraft types, but they didn't and it is not an option to mod the core game.

 

 

 

My solution to this using my old free Shoot voice command software was to have separate profiles for each aircraft (or class of aircraft) to accommodate the comm menu tree variations.

 

 

 

But with VAICOM Pro, I don't see anything I can easily edit within the voice attack profile, and I don't know a way to customize the plugin to make it work with WW2 aircraft, and even if I did, I would need to have an alternative modded plugin to support the odd aircraft.

 

 

 

Has anyone else encountered this and have a fix for it?

I have seen this and have sent Hollywood a question about it. The radio works fine on the ground but stops as sonn as the wheels leave the ground

 

Sent from my SM-T835 using Tapatalk

[streakeagle]

That is interesting. I had noticed I could talk to the base on some cold start missions, so I thought it was primarily commands that were on a different menu structure that didn't work.

 

What would change on either end... DCS World engine, Fw190, or VAICOM Pro that would make the behavior change upon leaving the ground? Line of sight calculation error (i.e. blocked or out of range)? Virtual power failure? Mic doesn't key in-game? Bizarre.

 

Overall, this software works brilliantly and I have come to rely on it. It eliminates seeing text on the screen while communicating and makes it so all I have to do is key a mic to talk to anyone, including my virtual RIO. The integration with SRS is very nice, too. ED has come to the party a little late with their voice chat. It doesn't even come close to doing what SRS does. They would have to give me something that rivals the VAICOM Pro/SRS combination to get me to use it at this point.

 

But right now, I was hoping to focus on the Fw190D9 for the first time in a while. This little hangup will force me to do something else, because I am not typing key commands to talk to AI ever again if I can avoid it.

[hornblower793]

I have just been playing around some more and this doesn't seem to occur if Easy Communication is On and the radio works consistently throughout the training flight.

 

 

I then turned Easy Comms off without changing any other settings and repeated the test. The two screenshots below show the VAICOM overlay on the runway and shortly after takeoff with the PTT button pressed. The first clearly shows the radio tuned to the recipient while in the second this information is not present (and it does not show the radio in use either)

Edited July 5, 2020 by hornblower793
Further information added

[streakeagle]

Given how well VAICOM is integrated, I am willing to bet this problem is on the DCS side. Either way, I sure would like to see this fixed. But with DCS, there are quite a few "little things" I would like to see fixed that have been around for years.

[MAXsenna]

Just throwing in my 2 cents.

VAICOM doesn't use the radio menu at all. It talkes with DCS directly using network.

Also, some of us are discussing this issue with several modules. It would be super cool if you have the time to check and test some steps by Hornblower's suggestion in the hope that Hollywood can come up with a fix. I believe you are correct that this is a DCS problem, and not a VAICOM one.

Cheers

 

https://r.tapatalk.com/shareLink/topic?url=https%3A%2F%2Fforums%2Eeagle%2Eru%2Fshowthread%2Ephp%3Ft%3D279268&share_tid=279268&share_fid=74365&share_type=t&link_source=app

 

 

Sent from my ANE-LX1 using Tapatalk

[streakeagle]

I understand that VAICOM doesn't use the menu system... but the difference in the menu system may indicate a difference in the underlying code which for the radio comms for those modules, which could be the source of the problem. In which case, VAICOM would need to implement a different interface for those modules.

 

The fact that it works in easy mode but doesn't work in normal mode is interesting. It means that in easy mode, the radio functionality is the same no matter what. So what changes when easy mode is turned off that is different than other modules that work correctly with VAICOM? Because with VAICOM not running, the radio works fine with easy mode turned off using the menus. So the problem is most likely the exposed interface between DCS World and VAICOIM, but why are some modules different than others?

[MAXsenna]

Exactly. That is sort of what what we are discussing in the other thread. Which modules work, and which don't. So it can be easier to figure out why it has stopped working. Because it was before.

 

Sent from my ANE-LX1 using Tapatalk

[Hollywood_315]

Hi gents - specifically with the Dora there may have been some change recently, we'll have a look to see what's up thanks.

[hornblower793]

Hollywood is taking a look at this case to see if he can figure out what is happening. I think it may help with the other airframes as well