Goofeyfoot

Voice Attack is crashing randomly after just a few minutes of play. Doesn't seem to be connected to a single command. I have Vaicom Pro. I play on Steam. Using VR

Many thanks!

Weegie: I did the "Hot Mic" thing you described above and that seemed to work OK. I just speak a MINE command without engaging a MIC and everything works OK. Have written about 10 commands in MINE and they now all seem to work that way. I didn't do the PTT method because I didn't really understand all that "Multi" stuff you mentioned. Is there a video somewhere that shows all these menus and their utility? It would be good to see a presentation that discusses not only "what" a button does buy also "why" the player might want to use it. Thanks for your help. Michael

Weegie: I tried to use the MINE simultaneous with VAICOM serving as the dominant profile. I said NIGHT VISION which in MINE means turn on the night vision goggles. Nothing happened. VAICOM reports the event this way: 8:42:45.693 Listening suspended 8:42:45.686 Joystick : 'Transmit TX2 release' 8:42:45.272 Recognized : 'night vision' (referenced) (Confidence 82) So we can safely say that VAICOM "recognizes" the command. It just doesn't seem to do anything with it. Then, if we put VAICOM in the subordinate role, with MINE as the dominant role, then the MINE commands work fine by themselves at the outset, but only up to a point. If I first say NIGHT VISION (and I don't need to push the mic button to do that), the command executes. But, if I later trigger the mic switch so to give a VAICOM command, then upon release of the mic switch the headphone icon on the right side of the Voice Attack panel turns red and no further MINE commands are processed from that point. So, from a non-expert point of view it would appear that the mic switch on the VAICOM has some bearing on the problem I'm experiencing. Again, thanks. Michael

Weegie:: Thanks for that detail. Today I will try the suggestions you have set forth. I will get back to you after that. Thanks again. Michael Weegie: I should’ve said one more thing. I have mine set up so that I use the mic switch to trigger the VAICOM instructions. The MINE profile, on the other hand doesn’t have that. I wonder if this fact could have something to do with the issue? Or maybe that is irrelevant? Thanks. Michael

I am not a telecomunications expert so please bear with me. I use VAICOM pro with DCS. Flying A10C. The VAICOM Pro works fine. But I want to add my profile "on top" of VAICOM so I can add voice commands to that. Maybe I have 6 commands in MINE right now. But probably I will end up with more like 20. When I engage my profile, let's call it MINE so we don't get confused, simultaneously with VC the MINE commands are heard but they don't execute in the game. It's like the MINE commands don't exist. If I turn off Profile Support, of course the MINE commands work. But once I engage Profile Support, the MINE commands don't work anymore. I talked to Voice Attack about this, and they referred me to you. Thanks. Michael

OK I can connect time after time. But I can never STAY connected for more than a few seconds. "You're taking fuel" and then the disconnect occurs. Seems like ANY move I make to stay even with the tankser once connection occurs causes an almost immediate disconnect. So my question is, who the heck do you STAY connected.

Is this the right place to ask questions? If I tell the wingman "engage infantry with guns" Vaicom recognizes the entire sentence accurately virtually all the time. But, inthe DCS A10C the wingman only sees "engage infantry", at which point the wingman wastes the most precious weapon he has instead of using the weapon I chose. Same thing happens if I say "with" any other weapon. The wingman hears the "engage" part but not the weapon. Very weird because as I said, the VC application does recognize the entire sentence. But DCS only hears the first part. Thanks. Michael

I am having the same problem with VA with VAICOM. Works fine for several minutes in DCS and then it suddenly crashes altogether. It happens when I fly the A10C which is really the only combat plane I actually use. Any help would be appreciated. Thanks. Michael

I see. Well in this one, the "Bullseye" they give you isn't the one they measure off. The guy comes on the radio and describes a "point" by saying that it is X degrees and Y distance from the bridge. He does that a couple times during the mission, always measuring from the bridge. That bridge gets marked onto the F10 map. So are you saying that I have to make that bridge into a Bullseye and then do an offset from that? Wouldn't it be easier and more realistic to measure that point on the F10 map and mark it right on that same map? Only downside is that it isn't going to show up on the HUD but in the heat of the battle, radio comms, etc., would a pilot really have the time and ability to enter something in the CDU?

Huh? They give you distance snd angle from the bridge. There’s nothing to compute or interpret.

Ok, thanks. Will give it a shot.

Can someone give me some ideas as to how to beat this one? I have been stuck on it for weeks. The ATC gives you directions to a place where there are absolutely no targets. So I just start randomly shooting at whatever enemies are anywhere in the mission. The random approach isn't working for me. I'm just wandering around shooting whatever I can. The weapons they give you in the campaign seem to be totally inadequate. EG no Mavericks. More than too many CBU 87s are provided, all of which seem to kill nothing of any importance. I guess I could rearm at the beginning but as stated above, I don't know specifically what I am trying to do so I can only guess what weapons would be valuable. So is anyone able to suggest a more focused approach? Thanks. Michael

Correct, and as you may have surmised, I set mine to the “switch” setting.

One more thing. I haven’t completely validated this but I think if you left one radio free of any connection to an AI entity such as an ATC and dedicated that one radio to internal team communications you don’t need to use the switch command. Rather, you hold the microphone button down until you hear the second beep and now you’re talking to your fellow players. If this validates, it’s probably a better solution than what I wrote above. Will have to test this further.

OK I might have another workaround to this. Assuming that you connect to three AI radio stations, i.e. three different ATC‘s you have to follow the following procedure if you want to talk to live players in multiplayer mode. You say the word “switch” at which point you’ll hear a tone. Once that tone happens you’re in transmit mode and able to talk to your fellow players. I tried that tonight and it worked perfectly. It is easier to see this in action if you look at the SRS overlay. It will show the transmit signal once you have switched over.

Thanks for your response. I guess I will do things the way you suggested, at least until the bugs are worked out.

According to the manual, when you use dynamic switching two things are supposed to happen. First, an AI command goes out, then after a tone, you are speaking with human players. This way, the human people don't have to listen to whatever AI commands you have given. That works fine as long as I haven't communicated on the radio in question. Once I do that, the program seems to lose its ability to receive an AI command on that particular radio. The AI function will still pertain on a different radio, but only until I have communicated on that radio. Then the same thing happens, i.e. no command to AI. I have only started using this product, so I apologize if this is a newbie question. Enjoy the product very much.

I just installed this a couple days ago. When I was using it originally, the configuration nodes for the different channels would click on "TX" showing me transmitting on one of the six channels. Now for some reason, that does not happen when I PTT. And in Flight Attack it keeps saying to "use an active node" or something like that whenever I try to talk. Also, in VC the little headset icon keeps defaulting to mute or not listening or something. Anyone know what is wrong? Thanks. Michael