Michael Feetham 1458998 Posted October 21, 2019 at 11:24 PM Posted October 21, 2019 at 11:24 PM (edited) When I set the xpilot audio output to my speakers, everything is fine. However, when I set output to my headphones, I no longer get audio. The Rx lights up, and other audio mutes slightly, but I don't hear anything. Radios are set correctly, as I can hear ATC and ATIS when I connect to speakers. I have verified audio from com1 AND com2 both work with speakers but not headphone output. Other computer audio is working on headphones without issue, including xplane. Windows 10Home x-plane 11 (latest version as of Oct 20, 2019) xpilot 1.1.0.7 Edited October 22, 2019 at 01:19 AM by Guest Link to comment Share on other sites More sharing options...
Ernie Garcia 1392892 Posted October 22, 2019 at 12:07 PM Posted October 22, 2019 at 12:07 PM I am having the same issue, frustrating!! to the point that I am considering going back to IVAO or flying offline (which is basically the same thing ). Are you using the Logitech G633 by any chance? Link to comment Share on other sites More sharing options...
Justin Shannon Posted October 22, 2019 at 01:10 PM Posted October 22, 2019 at 01:10 PM Look at your xPilot configuration file (by default located in %localappdata%\xPilot) and see if the name of your headset device is getting truncated. If it is, try manually changing it to the full name and then launch xPilot and try again. Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Michael Feetham 1458998 Posted October 22, 2019 at 07:21 PM Author Posted October 22, 2019 at 07:21 PM I am having the same issue, frustrating!! to the point that I am considering going back to IVAO or flying offline (which is basically the same thing ). Are you using the Logitech G633 by any chance? I'm using the G433 Gaming Headset. Link to comment Share on other sites More sharing options...
Michael Feetham 1458998 Posted October 22, 2019 at 07:27 PM Author Posted October 22, 2019 at 07:27 PM Look at your xPilot configuration file (by default located in %localappdata%\xPilot) and see if the name of your headset device is getting truncated. If it is, try manually changing it to the full name and then launch xPilot and try again. Justin, There does not appear to be an xPilot folder in my local app folder. Can you give me the specific file name? I'll search for that. Link to comment Share on other sites More sharing options...
Justin Shannon Posted October 22, 2019 at 07:33 PM Posted October 22, 2019 at 07:33 PM Look at your xPilot configuration file (by default located in %localappdata%\xPilot) and see if the name of your headset device is getting truncated. If it is, try manually changing it to the full name and then launch xPilot and try again. Justin, There does not appear to be an xPilot folder in my local app folder. Can you give me the specific file name? I'll search for that. Then it’s wherever you installed xPilot. Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Michael Feetham 1458998 Posted October 22, 2019 at 09:31 PM Author Posted October 22, 2019 at 09:31 PM Then it’s wherever you installed xPilot. I have found the AppConfig.xml file in the installation directory (I chose a custom directory for install, not default). Looking through that, I found this section. Microphone (Voicemod Virtual Au Speakers (Logitech G433 Gaming Headset) false The OutputDeviceName appears to be correct (though the microphone looks truncated). Link to comment Share on other sites More sharing options...
Ernie Garcia 1392892 Posted October 22, 2019 at 09:44 PM Posted October 22, 2019 at 09:44 PM Look at your xPilot configuration file (by default located in %localappdata%\xPilot) and see if the name of your headset device is getting truncated. If it is, try manually changing it to the full name and then launch xPilot and try again. Thanks for the reply. It doesn't seem to fix anything although it was truncated. I can hear the noise it makes when ppl type and stuff but same problem with receiving voice and ATIS like stated above and since he also has a G headset I'm [Mod - Happy Thoughts]uming Vatsim is not made for the G series (and yes I have all drivers updated). Doing my last flight tonight in the "mute" sort-of-speak and then switching back to IVAO. Link to comment Share on other sites More sharing options...
Justin Shannon Posted October 23, 2019 at 02:33 AM Posted October 23, 2019 at 02:33 AM Does the standalone AFV client work? Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Michael Feetham 1458998 Posted October 23, 2019 at 02:02 PM Author Posted October 23, 2019 at 02:02 PM Does the standalone AFV client work? Uninstalled xPilot, installed xSquawkbox and the AFV standalone client. Exact same result. Audio works when I select speakers as output, doesn't work when I select headphones. Link to comment Share on other sites More sharing options...
Justin Shannon Posted October 23, 2019 at 05:02 PM Posted October 23, 2019 at 05:02 PM Does the standalone AFV client work? Uninstalled xPilot, installed xSquawkbox and the AFV standalone client. Exact same result. Audio works when I select speakers as output, doesn't work when I select headphones. If you open the settings and select your headset as an input device, does the mic level indicator bar move when you speak? Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Michael Feetham 1458998 Posted October 23, 2019 at 10:39 PM Author Posted October 23, 2019 at 10:39 PM If you open the settings and select your headset as an input device, does the mic level indicator bar move when you speak? Yes, the microphone works. Removed the Logitech headphones and uninstalled them. My son has SteelSeries USB headphones, so I tried those. Everything works 100%. Uninstalled the SteelSeries, plugged Logitech headphones back in, forced a driver update and I'm back to the same problem. Link to comment Share on other sites More sharing options...
Michael Feetham 1458998 Posted October 23, 2019 at 11:03 PM Author Posted October 23, 2019 at 11:03 PM GOOD NEWS! I downloaded the latest version of Logitech G Hub from the Logitech website. Installing the new software has resolved my issue. I have tested with xSquawkBox/AFV standalone client as well as wil xPilot. Not sure why this was different than the drivers alone. Justin, thank you for all your due diligence and support. Link to comment Share on other sites More sharing options...
Justin Shannon Posted October 23, 2019 at 11:06 PM Posted October 23, 2019 at 11:06 PM Fantastic news! Happy to hear (pun intended!) it’s working for you now. Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Recommended Posts