John McPherson Posted February 12, 2022 at 06:28 PM Posted February 12, 2022 at 06:28 PM I'm on the latest beta of X-Pilot and had issues today - my first use of v2.x - with certain ATC positions but not others: Connection to the network via UK server OK Other traffic showed up on the ground as expected - CSL models worked well Not all local ATC positions/frequencies were listed in the 'nearby ATC' window - three times I was handed off to active frequencies not listed in the window. After tuning some ATC positions, I could hear other pilots on the freq, but not the controller. Other pilots could hear me, but the controller could not. For example, while on the ground at Schiphol I could only hear (and be heard by) other pilots on EHAM_Twr and EHAM_del whereas if I tuned EHAA_ctr I could hear all transmissions including ATC, and be heard by ATC. Both controllers confirmed in chat that they could hear some (but not all) pilots. Some, but not all, ATC controllers were very quiet, despite volume set to 100% in the software settings and on the radio stack. I have been using X-Pilot for some time now, and have never experienced these issues with previous versions. Pilots in the chat were citing 'server issues', but I don't see how the servers would pick on ATC!! I tried disconnecting, and going back in via other severs: the German and Amsterdam servers both denied access as they were 'full', and I eventually got back on via Singapore! From Langen Radar right down to Brindisi I had good coverage and voice contact worked as expected, apart from the voice volume issues I mention above (which may be down to the v2.x treatment of microphone levels etc). Anyway...it's still work in progress so please keep it going: these are observations and feedback, not intended as criticism. Link to comment Share on other sites More sharing options...
Dace Nicmane Posted February 12, 2022 at 06:56 PM Posted February 12, 2022 at 06:56 PM 24 minutes ago, John McPherson said: Both controllers confirmed in chat that they could hear some (but not all) pilots. Interesting. The other day I was flying into GVBA, it's a remote location and I was the controller's only pilot, we could not hear one another, so we used text. Link to comment Share on other sites More sharing options...
Marc Sieffert Posted February 13, 2022 at 09:45 AM Posted February 13, 2022 at 09:45 AM I confirm the sound problem of the controllers!! I did a flight from Paris to Gatwick yesterday evening with version 22 and in Paris I could hear the Tower well but all other Controllers especially in UK the sound was so weak that I could not understand them (vol was set on 100%). Please to the technical xPilot team have a look at this, it was a terrible flight!! But for info I could hear most of the pilots... Also I could hear COM2 although I put COM2 on 0%. Then I moved the button a bit and put again on 0 % then it was off. Is there another way to switch off COM2? For info I was on the German server... and I was wondering if it has something to do with the AUDIO API selection... What actually is recommended here when you use X Plane, Nvidia and WIN10?? Thanks!! Link to comment Share on other sites More sharing options...
Gary Oliver Posted February 13, 2022 at 12:01 PM Posted February 13, 2022 at 12:01 PM The ATC volume issue is now resolved in the latest version of the Controller AFV Standalone client. This was not an issue with xPilot and should now be resolved on your next connection to the network. Cheers Gary AFV Lead Developer 1 Link to comment Share on other sites More sharing options...
John McPherson Posted February 13, 2022 at 01:08 PM Author Posted February 13, 2022 at 01:08 PM 1 hour ago, Gary Oliver said: The ATC volume issue is now resolved in the latest version of the Controller AFV Standalone client. This was not an issue with xPilot and should now be resolved on your next connection to the network. Cheers Gary AFV Lead Developer Thanks @Gary Oliver, that's good to know. Going back over my issues yesterday I'm now wondering whether the cause of the 'hearing other pilots but not ATC' was actually the result of me trying out the 'auto-tuning' feature in the app? I fly the Zibo mod in XP11 and usually tune my COM radios manually, but yesterday I was trying out x-Pilot v2 for the first time and trying all its functionality, so I clicked the 'tune COM1' on some handoffs. I've just read that it does not yet resolve down to XXX.xx5 frequencies, only to XXXxx0. I 'm guessing I could not hear ATC on those channels as I was not fully tuned, and the other pilots I could hear were similarly on the wrong channel? Even so, I was able to speak with ATC via text, despite not being tuned into their channel?? So voice and text channels are handled differently, maybe? Link to comment Share on other sites More sharing options...
Marc Sieffert Posted February 13, 2022 at 02:35 PM Posted February 13, 2022 at 02:35 PM Sound pb seems to be solved great! Thanks! But regarding the comment above I also have a question. Frequency for Tower in Gatwick is 124225 and approach is 126825 (see below) but the Controllers show 124220 and 126820. Are these frequencies from the Controllers correct? The pb is that in Zibo frequencies go from x15 to x25... no x20... Thanks for clarifying! Link to comment Share on other sites More sharing options...
Lauri Uusitalo Posted February 14, 2022 at 06:45 AM Posted February 14, 2022 at 06:45 AM Not sure if this is an issue with ATC software actually, but freq ending with 5 works. Link to comment Share on other sites More sharing options...
Recommended Posts