VAICOMPRO-Community
VAICOMPRO-Community copied to clipboard
Penecruz
[BUG] "Select Channel" not working in game
Describe the bug The "Select Channel" command is not working in DCS, though VAICOM is registering is as a command.
To Reproduce Tested in F14 F18 and F16 powered up on the ground, the command is registered in the vaicom log however nothing happens in DCS
Expected behavior Should select a channel preset on the radio
Screenshots N/A
Additional context This "should" be implemented in VAICOMPRO but appears not to hook into DCS properly in any aircraft and should be investigated.
I checked on my end:
"Select Channel" works for the F-14 as well as the F-16. Indications are changing as well on both Radios "Select Channel" does NOT work on the F-18. The command is recognized, but I don't see any changes, neither to the used frequency nor to the channel indicator.
BUT for the command to work, the respective Radio has to be keyed. So it might be in line with Issue #25
Good feedback! Though it did not work in the F14 and F16 for me when I tested it. Let me go back and try some other cases to verify and make the appropriate edits. Though I think you are correct with the radio keys which I do not have bound or use as I use a singular VAICOM PTT. Those commands should be able to work without keying a radio.
FYI, in the F-16, Select Channel works in Single Player but not Multiplayer. I'm keying the actual radio when using the command.
They do not work if using a single PTT I have tried on the F14 F16 and F18.
FYI, in the F-16, Select Channel works in Single Player but not Multiplayer. I'm keying the actual radio when using the command.
You have your DCS radio bind shared with vaicom for those radios? I tried it in that configuration as well and have nothing changing.
They do not work if using a single PTT I have tried on the F14 F16 and F18.
FYI, in the F-16, Select Channel works in Single Player but not Multiplayer. I'm keying the actual radio when using the command.
You have your DCS radio bind shared with vaicom for those radios? I tried it in that configuration as well and have nothing changing.
Yes, I have separate PTT's for the UHF (COM1) and VHF (COM2) radios in Vaicom for the F-16. I'll try it out in the F-18.
They do not work if using a single PTT I have tried on the F14 F16 and F18.
FYI, in the F-16, Select Channel works in Single Player but not Multiplayer. I'm keying the actual radio when using the command.
You have your DCS radio bind shared with vaicom for those radios? I tried it in that configuration as well and have nothing changing.
Yes, I have separate PTT's for the UHF (COM1) and VHF (COM2) radios in Vaicom for the F-16. I'll try it out in the F-18.
I tried this configuration with no luck unfortunately. Confirming this is "Select Channel" command and its changing your radio preset number?
FYI, in the F-16, Select Channel works in Single Player but not Multiplayer. I'm keying the actual radio when using the command.
I did some additional testing and want to correct my previous post. I was only able to get this to work in the F-16. I was not able to ever get it to work in the F-18.
The problem does not appear to be different in Singleplayer vs Multiplayer but rather if the F-16 radio presets have been changed from defaults in the Mission Editor. In a generic mission like F-16 Free Flight in NTTR, the "Select Channel" command works to change both UHF and VHF radio channels (assuming you have PTT Tx 1 & 2 mapped to COM 1 & 2). It also worked on a Multiplayer server (like Rotorheads) if they have not changed the presets in the ME. However, if the presets have been changed in the ME, it doesn't work in either Single- or Multiplayer mode.
Also, you have to be very careful to say "Select Channel #" with no pause between the first and second word or the command does not work (it looks like it tries to process a Wingman command). For this reason, I added the keyword, "Preset #", in the Vaicom profile to avoid that confusion arising.
I hope that helps.
FYI, in the F-16, Select Channel works in Single Player but not Multiplayer. I'm keying the actual radio when using the command.
I did some additional testing and want to correct my previous post. I was only able to get this to work in the F-16. I was not able to ever get it to work in the F-18.
The problem does not appear to be different in Singleplayer vs Multiplayer but rather if the F-16 radio presets have been changed from defaults in the Mission Editor. In a generic mission like F-16 Free Flight in NTTR, the "Select Channel" command works to change both UHF and VHF radio channels (assuming you have PTT Tx 1 & 2 mapped to COM 1 & 2). It also worked on a Multiplayer server (like Rotorheads) if they have not changed the presets in the ME. However, if the presets have been changed in the ME, it doesn't work in either Single- or Multiplayer mode.
Also, you have to be very careful to say "Select Channel #" with no pause between the first and second word or the command does not work (it looks like it tries to process a Wingman command). For this reason, I added the keyword, "Preset #", in the Vaicom profile to avoid that confusion arising.
I hope that helps.
This is good information, though I could not even get it to work in a SP F16 instant action mission, so I know that changing the presets didnt impact it. It is physically changing the number preset on the radio and not just frequency/recipient?
Could you share your vaicom config and ptt settings so I can test those? I still cannot replicate it functioning.
Here are my PTT settings and the Vaicom Command change. I simply duplicated the "Select Channel" command and changed the spoken part to "Preset". I have to be keying TX1 (VHF AM) or TX2 (UHF) for it to work properly.
Could you share your vaicom config pages I mean, PTT Preferences. I still am unable to make this work.
Haha yeah we are tracking that bug....
And my settings are identical other than "Display Info" and I still cannot see the channel presets change in the aircraft
It is true that it doesn't work in many instances for me and it sounds like LtJaeger (above) was also able to get it partially working as well. I think we've safely proven it's mostly bugged :-)