AtomicMysteryWeasel

Does anyone know if there is someplace online where you can purchase replacement parts for Winwing equipment? Button 14 on my F-16 JGrip fell off somewhere and I can't find it. Thanks.

Ah it was just me. Evidently I just needed to reboot my machine after the update. I'm all good. Thanks, Flap.

I haven't tried that yet, Mel. But I will and I'll let you know. Thanks!

Is it just me or is this a known issue? With the May 18, 2022 update does anyone else see all white washed out vehicles on the stores and loadout page when editing a mission?

Yes I have done the finish step. OK so...with the Easy Comms and VPSX on...as long as I speak quickly it seems to work as normal. No beeps when I initially address my recipient, but it works pretty darned well. I over flew several air fields and called out to Washington or Marshall and had no issues contacting them. Also my VA seems to load up with a lot more dialogs when it first starts up. Unless I've hit some verbose switch I was previously unaware of a ton of F10 selections are loading on startup and that never happened before. Before on the old PC that is. I'm beginning to think my old setup was bent, just bent in a way I liked and got used to, but may be this is how VA is supposed to work? I'm not sure. I need to go through the Vaicom Pro manual and learn some of the more nuanced commands. I always had issues on the new machine giving wingman more than just the most basic commands. All this F10 load out at start business makes me wonder if maybe the old machine wasn't loading up the way it should? That would explain beeps where they shouldn't be. I really appreciate you guys trying to help me. I need to poke around on this some more, but I feel like I'm headed in the right direction with it. I don't get the chance to play DCS much through the week. I've normally had enough of computers by the time I get off work, but I'll keep you guys posted how I make out as I work through this. Thank you all again.

Ok so if I just breeze through the command quickly without any pausing: "ChiefRemoveTheWheelChocks." "JTAC,Playtime15Minutes." etc. It looks like everything is working fine - outside of DCS. Maybe it's just me and I'm an idiot. I know that VPSX commands are supposed to be given in an expeditated manner, but I could have sworn I used to get a beep after addressing my recipient ("Chief," beep "...remove the wheel chocks."beep. ; "JTAC", beep "...playtime 15 minutes. beep. ") but maybe I'm wrong. I'll fire up the hornet after Sunday lunch and try this out again. I'll let you know how I make out. The hard part is going to to be unEasy Comms and trying to figure out where to map three additional TX buttons.

OK well it is possible I'm remember how this worked incorrectly. There was quite a bit of time between the death of the old PC and my new box getting here. I'll try what you're suggesting as far as not starting DCS and see what happens. I'll also try going without Easy Comms - that sounds kind of daunting, but I'll try it. --Thank you.

"Not quit @MAXsenna. When I say ‘Chief’ and then pauze, I here a beep from vaicom that it recognized the intended recipient. Same with Overlord, Magic etc. @AtomicMysteryWeasel doesn’t hear that beep and he should. If I read it right then because vaicom doesn’t recognize the intended recipient it doesn’t carry out the command. If this correct then unfortunately I have no solution." Yes, this is indeed what is going on. "So it doesn't know "Marshall" or "Washington" or "Tower" I think it's just picking the nearest tower etc. Which would explain also why it doesn't know what do with "Chief" or "Sarge"." This is my own supposition, and I could very easily be wrong - but this seems to be why it's doing what it's doing. Yes, I am using Easy Communications. I never play multiplayer. I'm just not that good yet, and it's just less hassle. OK Max, So are you saying maybe I need to keyword train VA/VP?

OK well...maybe I'm losing my mind? Setting all of this stuff up from scratch has been a real job. Maybe I'm mistaken. I'll try what you mentioned and let you know how I make out. Thanks.

I just Master Zeroed the following settings. Still no joy.

Hi Max, OK so I tried the OPER switch. No joy. It's not that VA/Vaicom Pro aren't hearing me. It seems as though they're not picking up on who I want to talk to. Both Windows Speech and VA understand "Washington", "Tower", "Chief" et al all with a high 90% success rate. And both VA/Vaicom Pro know that I want to speak to "the nearest tower", or "nearest AWACs" etc. But it seems as though specific destinations are not being recognized. So it doesn't know "Marshall" or "Washington" or "Tower" I think it's just picking the nearest tower etc. Which would explain also why it doesn't know what do with "Chief" or "Sarge". Do you suppose this is a lua issue?

Here's some of my attempts over the past few minutes. What's weird is it says it doesn't recognize these words it actually recognizes. I mean...how do you understand you don't recognize the words "Washington" or "Tower" if you don't recognize the words Washington or Tower?

Hi sthompson, I appreciate the thought. Unfortunately that is a negative, Ghost rider.

Hi Max, Thanks for the suggestions. I did try them. I'm pretty sure the setting identified in the first picture attached is the setting you mean. It's on. Still no beep. Still the same behavior. Tower, Overlord, Marshall, Chief, JTAC, etc...doesn't matter who I address I get nothing. Just dead silence until my transmission ends. THEN I get a beep. It's so weird. I don't understand this.

I recently got a new PC and had to reinstall VoiceAttack and Vaicom Pro from scratch. Now that I've finally gotten everything reinstalled and reconfigured (geez what a chore!) the beep I normally got after addressing my intended outbound recipient is not occurring. For instance if I call up "Chief: remove the wheel chocks." Or "Tower request startup", etc. I get no beep after the slight pause in Chief or Tower. That is to say in the past what I should hear sounds like this: "Chief..." (brief pause) beep "Remove the wheel chocks" "Tower..." (brief pause) beep "Request start up" I'm no longer getting that beep , but I do get a beep at the end of my transmission. Which is really weird. I've tried this using Easy and Normal Comms, also with and without VSPX processing. Nothing changes. Everything else seems to work OK, but man I really like that first (hey my intended recipient heard and is listening to my transmission) beep. Has anyone else seen this behavior? What am I doing wrong? I've been over my settings a dozen times and all through the manual and this is driving me nuts.