Select recipient is not working

[Japo32]

Hello

I have been talking this in the Vaicom Discord.

Previously to community update 2.8, if I was taking from Kobuleti and wanted to change recipient to Batumi I had just to say:

"Batumi" pause "select" and the Batumi airport was selected in Vaicom so frequency was automatically changed (with easy comms off) in my plane, and I didn't need to say the recipient before the command, so I could just say "inbound" or "abort approach" and DCS would know I was talking to Batumi.

Now it doesn't do it. It will remain in the recipient I was starting the mission and if I say "inbound" it will talk with the first loaded recipient. This is very bad specially for multiplayer, were we can find several Jtac, or tankers to choose. 

STILL works if I say "batumi inbound" or "batumi cancel aproach" but I have to be saying always the recipient before. Of course that doesnt't change the freq.

I tested this is the F18 and F5. None of them are working. With the F14, the frequency is changed... but not selected the new recipient. Will remain in the old one.

Here you have the options choosen. I made a clean install as the instructions to install the community 2.8 says. Also in Vaicom editor I have "select"  under special commands category and segment is (undefined) Select recipient

Edit: Tested in the F18 and the frequency is changed with new recipient.. BUT it don't SELECT the new recipient.

Edited November 1, 2022 by Japo32

[nessuno0505]

If you have easy comms off I think the frequency should not change automatically in your plane. When you have manually tuned the correct frequency, then you should do your calls without saying the recipient's name. That should be the correct behaviour IMHO.

[Japo32]

It was doing previouly.. in fact the popup help in the "select tunes radio"  says: (Easy Comms OFF)Select commands tunes radio.

But that is not the important point for me. I don't care if now don't autotune the frequency (would be great, to be as it was, but....) the important is that CHANGE for the new recipient called, so we do not have to say it previously any command we say. That was the way it was working. If I tune the new recipient freq it will not change (tested)

I don't care if the community now wants to change it other way, but I tihnk still a method to choose recipient and stay in that one without naming previous to each command, would be nice.

Edited November 1, 2022 by Japo32

[sthompson]

3 hours ago, Japo32 said:

Hello

I have been talking this in the Vaicom Discord.

Previously to community update 2.8, if I was taking from Kobuleti and wanted to change recipient to Batumi I had just to say:

"Batumi" pause "select" and the Batumi airport was selected in Vaicom so frequency was automatically changed (with easy comms off) in my plane, and I didn't need to say the recipient before the command, so I could just say "inbound" or "abort approach" and DCS would know I was talking to Batumi.

Now it doesn't do it. It will remain in the recipient I was starting the mission and if I say "inbound" it will talk with the first loaded recipient. This is very bad specially for multiplayer, were we can find several Jtac, or tankers to choose. 

STILL works if I say "batumi inbound" or "batumi cancel aproach" but I have to be saying always the recipient before. Of course that doesnt't change the freq.

I tested this is the F18 and F5. None of them are working. With the F14, the frequency is changed... but not selected the new recipient. Will remain in the old one.

Here you have the options choosen. I made a clean install as the instructions to install the community 2.8 says. Also in Vaicom editor I have "select"  under special commands category and segment is (undefined) Select recipient

Edit: Tested in the F18 and the frequency is changed with new recipient.. BUT it don't SELECT the new recipient.

 

Does the VA log show that the select command was recognized and acted upon by VAICOM? If so then the problem will be with the underlying lua code. Probably something changed with DCS 2.8 that requires something new in the VAICOM lua code. If so the fix will require updating the underlying code. I haven't had time to check out the discord or github for the community project yet, but I'm wondering if they have set up a formal bug reporting system yet.

 

[hornblower793]

2 hours ago, sthompson said:

Does the VA log show that the select command was recognized and acted upon by VAICOM? If so then the problem will be with the underlying lua code. Probably something changed with DCS 2.8 that requires something new in the VAICOM lua code. If so the fix will require updating the underlying code. I haven't had time to check out the discord or github for the community project yet, but I'm wondering if they have set up a formal bug reporting system yet.

 

It is on the github - we would ask people to first concentrate on basic issues with the new version, and will then gradually expand it out to wider issues (such as comms not working with some airframes once wow)

[Japo32]

it appear the info in VoiceAttack.. but now for example it doesn't change neither the radio to the Kobuleti frequency:

 

[sthompson]

35 minutes ago, Japo32 said:

it appear the info in VoiceAttack.. but now for example it doesn't change neither the radio to the Kobuleti frequency:

 

This example does not show that VoiceAttack actually heard a command. Where are the commands that aren't working? Tip: Turn on debugging in VAICOM options before testing.

Also, you complain that the radio is not tuned automatically to Kobuleti. To understand why this might be so, note that in your first screen shot it shows that you have both "Select Tunes Radio" and "Instant Select" both checked.  However "Select Tunes Radio" only works with an explicit "Select" command. Simply naming the recipient (e.g. using "Kobuleti, Inbound") will select the recipient (because you have "Instant Select" turned on) but it will not tune the radio. It's always been like that. If you want the radio to tune automatically either use Easy Comms or an explicit Select command. Once things settle down on the community release I hope we can start a wish list for improvements, and it would be nice if "Instant Select" also tuned the radio when "Select Tunes Radio" is on.

Edited November 1, 2022 by sthompson
clarification of the tip

[Japo32]

I don't know if that was the way it was before... but I swear that same profile, with easy comms off and all that same vaicom config you see.. when I said "Batumi (pause) select" the radio was tuned to batumi frequency and the recipient was selected as batumi (so no more needed to say batumi before inbound. I am not asking better features than we had before.. I am asking to have the same. 

[sthompson]

8 minutes ago, Japo32 said:

I don't know if that was the way it was before... but I swear that same profile, with easy comms off and all that same vaicom config you see.. when I said "Batumi (pause) select" the radio was tuned to batumi frequency and the recipient was selected as batumi (so no more needed to say batumi before inbound. I am not asking better features than we had before.. I am asking to have the same. 

That behavior is consistent with what I wrote, so I believe you. However the example you posted did not include a visible "Select" command. In fact it did not show that you gave any commands at all. And so it is impossible to use it to see what might be going wrong now. So turn on debugging, fire up a mission, give that Select command, then report back with the log.

[Japo32]

Thanks.. here is is.. with 3 planes. F18, F14 and F16

 

VAICOMPRO.log

[sthompson]

@Japo32. I am unable to reproduce the problem. Can you confirm that you ran your tests using DCS 2.8 Open Beta version?

 

[Lt_Jaeger]

Untic instant select.

Instant select = Batumi inbound (the transmission will be automatically sent on Batumi tower freq) - no freq changes in the planes Radio

 

Select tunes radio =  Batumi - select (Radio will tuned to Batumi Tower) all subsequent transmission will be send to that freq

 

[Japo32]

It is tested with instant select on and off. Previous to 2.8 was always on without any issue. I am in Openbeta 2.8 but my vaicom is set to release one because I had a problem with something I don't remember and I needed to put all the files into DCS, instead of DCS.openbeta. Never that was an issue.... until now. But If the plugin works with the rest of things don't understand what could be.

1. I imported my old voiceattack profile. VAICOM PRO for DCS World-Spanish.vap

2. it is in spanish, but never was a problem.

If you can import the profile and take a quick look... I say "batumi (pause) seleccionar" to select recipient.

[sthompson]

15 hours ago, Lt_Jaeger said:

Instant select = Batumi inbound (the transmission will be automatically sent on Batumi tower freq) - no freq changes in the planes Radio

 

The part I highlighted in red is not accurate. With instant select VAICOM will first select Batumi as the intended ATC recipient even if you have not given an explicit SELECT command. However the transmission will go out on whatever frequency the radio is currently tuned to. It is NOT automatically sent on the Batumi tower frequency (unless you are using easy comms). You need to tune the radio first, either using cockpit controls or by using "select tunes radio" and giving an explicit select command.

[sthompson]

6 hours ago, Japo32 said:

 I am in Openbeta 2.8 but my vaicom is set to release one because I had a problem with something I don't remember and I needed to put all the files into DCS, instead of DCS.openbeta.

If you are flying Openbeta 2.8 but the VAICOM sliders are set to the release version then VAICOM probably is not updating your lua files properly, and that is the source of the trouble. In general the slider needs to be on the openbeta setting if you are flying openbeta.

I suggest you post your "CONFIG" page settings and also tell us the path to where your DCS openbeta version is installed.

[nessuno0505]

1 ora fa, sthompson ha scritto:

The part I highlighted in red is not accurate. With instant select VAICOM will first select Batumi as the intended ATC recipient even if you have not given an explicit SELECT command. However the transmission will go out on whatever frequency the radio is currently tuned to. It is NOT automatically sent on the Batumi tower frequency (unless you are using easy comms). You need to tune the radio first, either using cockpit controls or by using "select tunes radio" and giving an explicit select command.

Exactly. That has always been the behaviour. In some training missions it could be otherwise because that specific mission had "easy comms" always on. But with easy comms off you have to manually select the frequency on your airplane's equipment: that would be what you do in real life, and I hope this won't be changed by further development.

Edited November 3, 2022 by nessuno0505

[Japo32]

15 hours ago, sthompson said:

If you are flying Openbeta 2.8 but the VAICOM sliders are set to the release version then VAICOM probably is not updating your lua files properly, and that is the source of the trouble. In general the slider needs to be on the openbeta setting if you are flying openbeta.

I suggest you post your "CONFIG" page settings and also tell us the path to where your DCS openbeta version is installed.

here is my config. I changed this time to openbeta.. but as you can see my install directory is c:\DCS World, not DCS World beta. in any case it is the same result. It is rare that reseting the lua files, and even removing them from savedgames, Vaicom write again in dcs and dcs.openbeta (in savegames) the VAICOMPRO.export.lua FILE. 

As said, previous to 2.8 this was not a problem. it was working like a charm. "batumi" pause "select" and the recipient was selected. Now, don't know because DCS change or Vaicom change I cannot do it. Still I can do the "batumi" pause "inbound" order and it will say the inbound to batumi or whatever recipient I say.. but of course I have to set the correct frequency first by hand (no problem with that).

[Japo32]

This is driving me crazy. Sometimes (very very very rare) it recognizes and with recipient select it changes. Others tune de frequency. and others change the recipient also when I say "recipient" "command" so next commands will be switf to the new recipient.

But usually it doesn't change. Now why it changes sometimes???? where is the problem..