sthompson Posted November 21, 2020 Posted November 21, 2020 I'm sometimes having an issue where I attempt to "Select" an airfield, e.g. "Krymsk, Select" but then find that the command fails with recipient not available. The reported recipient in the log in this case is Hatay -- not on the Caucasus map, even though that is where I am flying. Similarly, "Krasnodar, Select" is recognized but the command fails with recipient Haifa not available reported. It's as if VAICOM is confused about the recipient. "Anapa, Select" works just fine. In each case I've checked the radio tuning and it is correct. I can contact these airfields using the radio menus without trouble. I've also noticed that often when I use Instant Select and Select Tunes Radio at the same time, the radio does not get tuned. For example, if I detune the radio from Anapa and then call "Anapa, Inbound" the call is recognized and an inbound call to Anapa goes out, but the radio tuning does not change to the correct frequency and so there is no response. On the other hand, "Anapa, Select" followed by "Anapa, Inbound" works fine. The first call tunes the radio and the second sends the inbound call, and Anapa responds. I tested all of this in the Mig-15 with Easy Communications turned off. I don't know if these are bugs or a problem with my understanding of how it is supposed to work. I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals
Weegie Posted November 22, 2020 Posted November 22, 2020 Interesting, I could never get select to work to tune the radio although VA was recognizing it, but I've always had instant select turned on. I''ll test it off later and see if that does the trick. Quite a few have problems with the Select command to tune the radio and I've checked that VA recognizes it but Vaicom doesn't do anything, Hollywood insists it's down to Cadence but I think there is bug lurking in there. Is VA recognizing your calls to Hatay and Haifa you can see this in the VA window I'd also enable the Run in Debug mode under Config in the Vaicom pop up and check what the Vaicom log is saying. I'll try it later to see if I'm having a problem I can't really offer much help but should at least be able to assist by finding out if it's specific to your setup or if more generic
sthompson Posted November 22, 2020 Author Posted November 22, 2020 Update: Reset my profile and keyword database, and did a DCS repair before restarting. The issues with Krymsk and Krasnodar becoming Hatay and Haiffa are gone, but the problem with Instant Select remains. That is, Instant Select does not tune the radio even if Select Tunes Radio is ticked in the configuration. See attached log file VA log.txt copied from the VA log window. (BTW, is it possible to get VA to save it's own log? It has info about what was heard and recognized that is not in the VAICOMPRO log.) I'm Softball on Multiplayer. NZXT Player Three Prime, i9-13900K@3.00GHz, 64GB DDR5, Win 11 Home, Nvidia GeForce RTX 4090 24GB, TrackIR 5, VKB Gunfighter III with MCG Ultimate grip, VKB STECS Standard Throttle, CH Pro pedals
Hollywood_315 Posted November 22, 2020 Posted November 22, 2020 Instant Select does not tune the radio even if Select Tunes Radio is ticked in the configuration. That is correct. With easy comms off you need to tune the radio before making the call to the recipient, either manually or using the Select command. There is no spoon. VAICOM PRO plugin for DCS World www.vaicompro.com
Recommended Posts