bonesvf103

what happens when I hit Q is the COM1 menu comes up. What I did was assign a mic button press and mic button release to Vaicom Pro via my physical HOTAS button for COM1 and COM2, and for ICS in the Tomcat. I also assigned a shortcut key in Vaicom Pro (in the Hornet's case, Q for COM1 and RCLT+\ for COM2. IT's been years since I did that so I'm not sure why except for that is what I have my comms set to in DCS and emulated by my HOTAS, so probably top be sure, or if I decided to not use Vaicom after trying it out. But I stuckwith it so it probably just remained there as a leftover since. In any cae I had a key assigned on my HOTAS to a TX like in the manual. My HOTAS software is HUD, which came with my Logitech X56. v6, boNes

Great news for all! My question is will it continue to be payware? I'm sure those who are taking the reins should be compensated somehow and those who have already purchased it should get their money's worth, especially those who just bought it recently not knowing it was no longer supported, it's doesn't seem fair to them to have paid for it and everyone in the future does not. v6, boNes

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

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

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

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

Nope it didn't work. v6, boNes

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

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

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

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

Just want to add that at least for me, the Hornet is the only plane affected by no radio comms menu. EVen with VAICOM Pro not working anymore, I atill can bring up the comms menu in the Tomcat, Falcon, etc, curious as that may be... v6, boNes

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

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

Update. I did a Steam integrity check and the radio menus are working again for the Tomcat but not for say the Hornet. I also have a Jester wheel. I haven't started Voice Attack though to see if it will change anything or if Bailey's profile will work instead. SO I dunno.... v6, boNes

I too am hugely disappointed. Even if I go to Bailey's profile, it was nowhere near as robust and had as many workable functions as VAICOM Pro did. But until then, I need to know what to do especially since it not only doesn't work, but I now have a DCS with broken comms--I can't make radio calls via keystroke at all. I am too squeamish on messing with lua lines. I don't want to break anything further and end up having a full reinstall to fix things. I don't think a slow repair is my answer as I am running the Steam version. MAybe I'll try the integrity check first. But I may need help doing lua line things (guess it's time to learn), or even to uninstall VAICOM Pro, which I hope will come back. Best scenario is getting my DCS radio functions to work again while leaving VAICOM PRo intact just not started or plugged in in case Hollywood come back to fix things. Jayhawk, I may be emailing you about this since you seem to know what you're doing... v6, boNes

Hi, OK I tried it with the patch. On the one hand, I did get another Phoenix killing Phoenix instance. On the other hand, when I fly it a few more times, the Phoenixes so far appear to behave much better now, I got 90-100% kill every time. What I didn't kill I got with Sparrow or Sidewinder. The bandits sure do know how to maneuver and smartly defend now! He had my Sparrow and Sidewinder in a tailchase for a while before turning back at me and I had to take him with the gun, it's scary! Thanks! I'll let you know if anything else comes up. v6, boNes

Sounds good, thanks v6, boNes

So I was doing the PG BVR mission and I fired 2 AIM-54Cs at 30000 ft, flying as fast as I could, at Fulcrums that were 25-30 miles away (closer to 30). As I monitored things, Jester called splash. I thought, OK, one Fulcrum dead. BUt when I merged both were still up and unscathed. As it turned out, my 2nd Phoenix killed my first Phoenix! How is that possible? In addition to that, the Fulcrum had deployed chaff to trash the Phoenix. I would think that a countermeasure resistant AIM-54C would fare better against that than it did. TacView attached, missile on missile kill at 12:02:20. Also shown in results at 15:32:40 I dunno, but after the last updates, I basically can't get a single Phoenix to hit even though it's the same mission and I attacked the same way where I was getting 90+% kill ratio. I even went in as close as 25 nm and shot from high altitude and highspeed and they still missed. They get dodged alot, no matter if they were As or Cs. And now they are killing each other. Puzzled. v6, boNes Tacview-20221026-231141-DCS.zip.acmi

Haha with the "Damn Bugs" patch! v6, boNes

I've hit a few maneuvering fighters with Phoenix active off the rail. To be honest, I did not think they would hit because they flew a straight line path and as mentioned before, they were slow. But then to my surprise, they turned hard to lead the target and boom. I fired 2 because I thought the first one was messed up, and they both hit! Best $3 million I ever spent! v6, boNes

Ak ok, guess I was being impatient. Thanks! v6, boNes

I fired Phoenix with ACM cover up and it still took a half second or so to come off the rail. I thought when fired that way they are supposed to come off the rail immediately? It did track as advertised though. v6, boNes

That all is what I was experiencing, yes. It is purely visual. Thanks v6, boNes

Does this include the emerg oversweep flag? I've noticed with wings set to auto, cover down, and you go fast renough so they sweep back to 68 deg, the emerg oversweep flag comes on. Is that a bug? v6, boNes