Announcement

Collapse
No announcement yet.

Problems with Easy Comms OFF on A10C

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Problems with Easy Comms OFF on A10C

    Hello everybody,

    I have been using Vaicom successfully and without major problems for a long time.

    But I have to admit that up to now I always made life easy for myself and used Easy Comms, so only 1 button on my Hotas and so the whole radio was done automatically.

    Now the ambition has grabbed me to try it without Easy Comms and to set the frequencies also accordingly manually.

    But with the A-10C I have the following problem:

    Config as follows:

    Mic-Switch forward= TX1 = Num1 = VHF-AM
    Mic-Switch down = TX2 = Num2 = UHF
    Mic-Switch backward = TX3 = Num3 = VHF FM
    Mic-Switch up = TX5 = Num0 = INT (whatever you need it for!?)

    In the Voice Attack menu I have made the bindings to the above mentioned Num0-3 accordingly and programmed them to my Mic-Switch on the throttle. When I test TX1-5, the Voice Attack menu also shows me the correct bindings.

    The selector wheel in the VA menu is set to "normal", so TX1-3 and TX5 are active, TX4 (auto) is greyed out and not active.

    In DCS I have deactivated easy comms, in Voice attack I have also deactivated the other options like "Instant select" etc.

    When I start the game, the menu of Voice attack also shows easy comms OFF correctly.

    When I open the radio menu in the game with the key combination for Mic-Switch forward, down and backwards I can see that I can only reach the corresponding recipients via the correct radio band with the correct frequency. So far everything seems to work correctly.

    But using VA and saying my phrases while pressing the Mic-Switch on my throttle, it makes nearly no difference what Mic switch I press and still reach the recipient.

    As an example: If I set the frequency of the airport in VHF-AM and ask for take-off permission, I can reach the tower via TX1 and TX2 and TX3 (and no, in UHF and VHF-FM the frequency of the airport is not set). I can change the frequencies of TX2 and 3, as long as I have the right frequency in TX1 (VHF-AM radio) I can call the airport via TX 1, 2 and 3.

    Same with my wingman. In UHF I have set his frequency and I can reach him with TX2 but also TX3, but not on TX1. Changing TX3 (VHF-FM) frequency does not hinder me in calling the wingman via TX3, as long as TX2 (UHF) has the correct frequency. On the other hand with TX1 I can not reach my wingman (so that seems to work our correct).


    First of all I hope you understand what I mean and also that someone might have a solution.

    Cheers, MadMonty
    Last edited 09-28-2020, 07:51 PM.

    Thermaltake Core V1 | MSI Z270I Gaming Pro Carbon | Intel I7700K | EVGA GTX 1080 TI SC | 32 GB RAM DDR4-3000 | Corsair H90 | 250 & 500 GB Samsung Evo850 SSD | WIN 10 64bit Pro | TM Hotas Warthog | TM Pendular Rudder | Oculus Rift S

    #2
    Originally posted by MadMonty View Post
    Hello everybody,

    I have been using Vaicom successfully and without major problems for a long time.

    But I have to admit that up to now I always made life easy for myself and used Easy Comms, so only 1 button on my Hotas and so the whole radio was done automatically.

    Now the ambition has grabbed me to try it without Easy Comms and to set the frequencies also accordingly manually.

    But with the A-10C I have the following problem:

    Config as follows:

    Mic-Switch forward= TX1 = Num1 = VHF-AM
    Mic-Switch down = TX2 = Num2 = UHF
    Mic-Switch backward = TX3 = Num3 = VHF FM
    Mic-Switch up = TX5 = Num0 = INT (whatever you need it for!?)

    In the Voice Attack menu I have made the bindings to the above mentioned Num0-3 accordingly and programmed them to my Mic-Switch on the throttle. When I test TX1-5, the Voice Attack menu also shows me the correct bindings.

    The selector wheel in the VA menu is set to "normal", so TX1-3 and TX5 are active, TX4 (auto) is greyed out and not active.

    In DCS I have deactivated easy comms, in Voice attack I have also deactivated the other options like "Instant select" etc.

    When I start the game, the menu of Voice attack also shows easy comms OFF correctly.

    When I open the radio menu in the game with the key combination for Mic-Switch forward, down and backwards I can see that I can only reach the corresponding recipients via the correct radio band with the correct frequency. So far everything seems to work correctly.

    But using VA and saying my phrases while pressing the Mic-Switch on my throttle, it makes nearly no difference what Mic switch I press and still reach the recipient.

    As an example: If I set the frequency of the airport in VHF-AM and ask for take-off permission, I can reach the tower via TX1 and TX2 and TX3 (and no, in UHF and VHF-FM the frequency of the airport is not set). I can change the frequencies of TX2 and 3, as long as I have the right frequency in TX1 (VHF-AM radio) I can call the airport via TX 1, 2 and 3.

    Same with my wingman. In UHF I have set his frequency and I can reach him with TX2 but also TX3, but not on TX1. Changing TX3 (VHF-FM) frequency does not hinder me in calling the wingman via TX3, as long as TX2 (UHF) has the correct frequency. On the other hand with TX1 I can not reach my wingman (so that seems to work our correct).


    First of all I hope you understand what I mean and also that someone might have a solution.

    Cheers, MadMonty
    Does your VA log show the correct TX buttons being pushed and released?

    Do you have Select tunes radio option selected

    Could you post images of your Vaicom config screens

    It is definitely worth resolving and will have an opportunity to sit at my PC tomorrow and look

    Sent from my SM-T835 using Tapatalk
    Windows 10 Home ¦ Z370 AORUS Gaming K3 motherboard ¦ i5-8600K oc to 4.3GHz ¦ 48GB Corsair PC4 memory @ 3000MHz ¦ Samsung 960 EVO M.2 SSD for OS, Samsung 860 EVO 500GB SSD for DCS ¦ ASUS ROG GTX 2060 Super 8GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk2 and MCG ¦ Thrustmaster Warthog Throttle ¦ MFG Crosswinds ¦ Oculus Rift S

    Comment


      #3
      Originally posted by MadMonty View Post
      But using VA and saying my phrases while pressing the Mic-Switch on my throttle, it makes nearly no difference what Mic switch I press and still reach the recipient.
      Suggest you enable debugging and tell us what is in the VA log when this happens.
      I'm Softball on Multiplayer. Dell XPS-8500 24GB, i7-3770@3.40GHz, Win 10Pro, Nvidia GeForce GTX 1060 6GB, TiR, CH hotas and pedals

      Comment


        #4
        Originally posted by hornblower793 View Post
        Does your VA log show the correct TX buttons being pushed and released?

        Do you have Select tunes radio option selected

        Could you post images of your Vaicom config screens

        It is definitely worth resolving and will have an opportunity to sit at my PC tomorrow and look

        Sent from my SM-T835 using Tapatalk
        Yes, VA-Log shows TX buttons working perfect (press and release).

        Select tunes is not selected.

        I will post config screens this evening...

        Thermaltake Core V1 | MSI Z270I Gaming Pro Carbon | Intel I7700K | EVGA GTX 1080 TI SC | 32 GB RAM DDR4-3000 | Corsair H90 | 250 & 500 GB Samsung Evo850 SSD | WIN 10 64bit Pro | TM Hotas Warthog | TM Pendular Rudder | Oculus Rift S

        Comment


          #5
          Originally posted by MadMonty View Post

          Config as follows:

          Mic-Switch forward= TX1 = Num1 = VHF-AM
          Mic-Switch down = TX2 = Num2 = UHF
          Mic-Switch backward = TX3 = Num3 = VHF FM
          Mic-Switch up = TX5 = Num0 = INT (whatever you need it for!?)

          In the Voice Attack menu I have made the bindings to the above mentioned Num0-3 accordingly and programmed them to my Mic-Switch on the throttle. When I test TX1-5, the Voice Attack menu also shows me the correct bindings.

          The selector wheel in the VA menu is set to "normal", so TX1-3 and TX5 are active, TX4 (auto) is greyed out and not active.
          Could you show your VA edit screen where you set up this config? I've been dreaming of doing this exact config for a while, with no luck thus far. Thanks.
          Jim

          Dell T5500, X5687 CPU @3.6 GHz, 48GB DDR3, Zotac GTX 980, Windows 10 Pro. TMWH throttle & stick. Alienware AW3418DW monitor. TrackIR 5 with UTC MkII Pro clip. VKB Mk. III rudder pedals.

          Comment


            #6
            Perhaps check that in DCS config you have disabled the HOTAS MIC keybinds (as per the user manual).
            There is no spoon.

            sigpic

            VAICOM PRO plugin for DCS World
            www.vaicompro.com

            Comment


              #7
              So, got my sceenshots...

              Like I said, TX1-5 bindings work fine, as shown in screenshot, however, TX1-3 seems to work for different radios while doing my phrases.
              Attached Files

              Thermaltake Core V1 | MSI Z270I Gaming Pro Carbon | Intel I7700K | EVGA GTX 1080 TI SC | 32 GB RAM DDR4-3000 | Corsair H90 | 250 & 500 GB Samsung Evo850 SSD | WIN 10 64bit Pro | TM Hotas Warthog | TM Pendular Rudder | Oculus Rift S

              Comment


                #8
                Originally posted by Hollywood_315 View Post
                Perhaps check that in DCS config you have disabled the HOTAS MIC keybinds (as per the user manual).
                Do you mean, to deleted the following bindings? But I do need them, when VA is not recognizing what I have said. Then I can enter the comm menu manually and work via F1 - F10. When I use the comm menu, it seems I can only use the correct radio on the correct frequency. That works therefore how it should be on easy comms off. But not using TX1-3 via VA.
                Attached Files

                Thermaltake Core V1 | MSI Z270I Gaming Pro Carbon | Intel I7700K | EVGA GTX 1080 TI SC | 32 GB RAM DDR4-3000 | Corsair H90 | 250 & 500 GB Samsung Evo850 SSD | WIN 10 64bit Pro | TM Hotas Warthog | TM Pendular Rudder | Oculus Rift S

                Comment


                  #9
                  One more thing I just saw while taking the screenshots. While TX1 - VHF-AM shows the correct frequency in the VA-Options-Window, it does show no frequency for TX2 and TX3.

                  PS: Tried already "select tunes radio", makes no difference.
                  Attached Files
                  Last edited 09-29-2020, 08:56 PM.

                  Thermaltake Core V1 | MSI Z270I Gaming Pro Carbon | Intel I7700K | EVGA GTX 1080 TI SC | 32 GB RAM DDR4-3000 | Corsair H90 | 250 & 500 GB Samsung Evo850 SSD | WIN 10 64bit Pro | TM Hotas Warthog | TM Pendular Rudder | Oculus Rift S

                  Comment


                    #10
                    No - don't get rid of the keyboard bindings - it is if you have bindings to your PTT switch


                    I think the issue might be with your Voiceattack Vaicom settings (your 3rd screenshot showing the PTT push and release commands


                    Attached is my image and it doesn't show the Start listening and Stop listening items (this changed some updates ago). To fix this, double click on each command in turn and remove the 'Start listening' or 'Stop listening' command from the dialog box. The second image shows how my edit command looks for TX1 press


                    Try this and see if it works
                    Attached Files
                    Last edited 09-29-2020, 09:58 PM.
                    Windows 10 Home ¦ Z370 AORUS Gaming K3 motherboard ¦ i5-8600K oc to 4.3GHz ¦ 48GB Corsair PC4 memory @ 3000MHz ¦ Samsung 960 EVO M.2 SSD for OS, Samsung 860 EVO 500GB SSD for DCS ¦ ASUS ROG GTX 2060 Super 8GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk2 and MCG ¦ Thrustmaster Warthog Throttle ¦ MFG Crosswinds ¦ Oculus Rift S

                    Comment


                      #11
                      Originally posted by hornblower793 View Post
                      No - don't get rid of the keyboard bindings - it is if you have bindings to your PTT switch


                      I think the issue might be with your Voiceattack Vaicom settings (your 3rd screenshot showing the PTT push and release commands


                      Attached is my image and it doesn't show the Start listening and Stop listening items (this changed some updates ago). To fix this, double click on each command in turn and remove the 'Start listening' or 'Stop listening' command from the dialog box. The second image shows how my edit command looks for TX1 press


                      Try this and see if it works
                      Thx, tried it, but it did not work out. Actually, I lost the ability to radio at all via VA. So I put everything back as it has been, now I can radio, but still like easy comms ON with multiple TX buttons serving for one radio, like it seems.

                      Any further ideas?

                      Thermaltake Core V1 | MSI Z270I Gaming Pro Carbon | Intel I7700K | EVGA GTX 1080 TI SC | 32 GB RAM DDR4-3000 | Corsair H90 | 250 & 500 GB Samsung Evo850 SSD | WIN 10 64bit Pro | TM Hotas Warthog | TM Pendular Rudder | Oculus Rift S

                      Comment


                        #12
                        Originally posted by MadMonty View Post
                        Thx, tried it, but it did not work out. Actually, I lost the ability to radio at all via VA. So I put everything back as it has been, now I can radio, but still like easy comms ON with multiple TX buttons serving for one radio, like it seems.



                        Any further ideas?
                        What version of Vaicom are you running and what extensions do you have?

                        Sent from my SM-T835 using Tapatalk
                        Windows 10 Home ¦ Z370 AORUS Gaming K3 motherboard ¦ i5-8600K oc to 4.3GHz ¦ 48GB Corsair PC4 memory @ 3000MHz ¦ Samsung 960 EVO M.2 SSD for OS, Samsung 860 EVO 500GB SSD for DCS ¦ ASUS ROG GTX 2060 Super 8GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk2 and MCG ¦ Thrustmaster Warthog Throttle ¦ MFG Crosswinds ¦ Oculus Rift S

                        Comment


                          #13
                          Originally posted by hornblower793 View Post
                          What version of Vaicom are you running and what extensions do you have?

                          Sent from my SM-T835 using Tapatalk
                          I am running the latest version of Vaicom and I have upgraded VA from 1.8.5 to 1.8.6. I reinstalled Vaicom and deleted my existing profile, using the given standard DCS profile and configured TX1-5 new. This time not using key bindings, but joystick buttons.

                          But still, I can radio to my wingman via TX1, 2 and 3.

                          Thermaltake Core V1 | MSI Z270I Gaming Pro Carbon | Intel I7700K | EVGA GTX 1080 TI SC | 32 GB RAM DDR4-3000 | Corsair H90 | 250 & 500 GB Samsung Evo850 SSD | WIN 10 64bit Pro | TM Hotas Warthog | TM Pendular Rudder | Oculus Rift S

                          Comment


                            #14
                            Originally posted by MadMonty View Post
                            I am running the latest version of Vaicom and I have upgraded VA from 1.8.5 to 1.8.6. I reinstalled Vaicom and deleted my existing profile, using the given standard DCS profile and configured TX1-5 new. This time not using key bindings, but joystick buttons.



                            But still, I can radio to my wingman via TX1, 2 and 3.
                            Is it just to your wingman now, or is it still to any recipient?

                            Sent from my SM-T835 using Tapatalk
                            Windows 10 Home ¦ Z370 AORUS Gaming K3 motherboard ¦ i5-8600K oc to 4.3GHz ¦ 48GB Corsair PC4 memory @ 3000MHz ¦ Samsung 960 EVO M.2 SSD for OS, Samsung 860 EVO 500GB SSD for DCS ¦ ASUS ROG GTX 2060 Super 8GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk2 and MCG ¦ Thrustmaster Warthog Throttle ¦ MFG Crosswinds ¦ Oculus Rift S

                            Comment


                              #15
                              Originally posted by hornblower793 View Post
                              Is it just to your wingman now, or is it still to any recipient?

                              Sent from my SM-T835 using Tapatalk
                              The problem seems to occur with any reciepient.

                              For example, flying a A10C mission from eneny within campaign 3.0, being at the ramp I tune the following frequencies:

                              TX1/AM - 133.00 (airport)
                              TX2/UHF - 252.400 (warrior 1)
                              TX3/FM - 33.40 (flight / wingman)

                              So when I request taxi, I can only use the AM comm menu to communicate with the tower. But using VA I can talk via TX1, 2 and 3 to the tower and always get a response.

                              After takeoff, I can communicate to my wingman only via the FM comm menu. But using VA, I can talk via TX 2 and 3 (not 1!?) to my wingman and get a response.

                              Thermaltake Core V1 | MSI Z270I Gaming Pro Carbon | Intel I7700K | EVGA GTX 1080 TI SC | 32 GB RAM DDR4-3000 | Corsair H90 | 250 & 500 GB Samsung Evo850 SSD | WIN 10 64bit Pro | TM Hotas Warthog | TM Pendular Rudder | Oculus Rift S

                              Comment


                                #16
                                Originally posted by MadMonty View Post
                                The problem seems to occur with any reciepient.



                                For example, flying a A10C mission from eneny within campaign 3.0, being at the ramp I tune the following frequencies:



                                TX1/AM - 133.00 (airport)

                                TX2/UHF - 252.400 (warrior 1)

                                TX3/FM - 33.40 (flight / wingman)



                                So when I request taxi, I can only use the AM comm menu to communicate with the tower. But using VA I can talk via TX1, 2 and 3 to the tower and always get a response.



                                After takeoff, I can communicate to my wingman only via the FM comm menu. But using VA, I can talk via TX 2 and 3 (not 1!?) to my wingman and get a response.
                                One of your earlier posts shows that TX2 and TX3 have no frequency associated with them in the Vaicom PTT window - is this still the case?

                                If so, I think that this is the clue - if not already done, please could you turn on debug in Vaicom and see whether any clues appear in the VA log

                                Sent from my SM-T835 using Tapatalk
                                Last edited 10-04-2020, 07:50 AM.
                                Windows 10 Home ¦ Z370 AORUS Gaming K3 motherboard ¦ i5-8600K oc to 4.3GHz ¦ 48GB Corsair PC4 memory @ 3000MHz ¦ Samsung 960 EVO M.2 SSD for OS, Samsung 860 EVO 500GB SSD for DCS ¦ ASUS ROG GTX 2060 Super 8GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk2 and MCG ¦ Thrustmaster Warthog Throttle ¦ MFG Crosswinds ¦ Oculus Rift S

                                Comment


                                  #17
                                  Originally posted by hornblower793 View Post
                                  One of your earlier posts shows that TX2 and TX3 have no frequency associated with them in the Vaicom PTT window - is this still the case?

                                  If so, I think that this is the clue - if not already done, please could you turn on debug in Vaicom and see whether any clues appear in the VA log

                                  Sent from my SM-T835 using Tapatalk
                                  Yeah, still no frequencies shown in TX2 and 3.

                                  In debug I cannot see any failure. Since I am planning to upgrade my system it is likely, that I will do a complete new installation of DCS and VA/Vaicom and maybe from then on it is running. For now, I have no clue what else I could do. At least, it is flyable...

                                  Thermaltake Core V1 | MSI Z270I Gaming Pro Carbon | Intel I7700K | EVGA GTX 1080 TI SC | 32 GB RAM DDR4-3000 | Corsair H90 | 250 & 500 GB Samsung Evo850 SSD | WIN 10 64bit Pro | TM Hotas Warthog | TM Pendular Rudder | Oculus Rift S

                                  Comment

                                  Working...
                                  X