Carl Buchler 1299832 Posted December 14, 2016 at 09:01 PM Posted December 14, 2016 at 09:01 PM I got some issues with my Vpilot.... after 10 minutes when im on a frequency, I cant hear any ATC and I need to refresh the frequency to hear again. I have already tried to reinstall and update Vpilot, but it still doesnt work. I would be very happy if someone could help me! Link to comment Share on other sites More sharing options...
Lindsey Wiebe 1101951 Posted December 14, 2016 at 09:57 PM Posted December 14, 2016 at 09:57 PM Are you possibly using a USB headset for vPilot? Sometimes with newer Windows they turn off power to USB ports, flipping frequency will just wake it up. Google "USB power windows" there's a setting to keep them always on. It's an ongoing issue with not just headsets/mic but also peddles, yokes, etc. Mr. VATSIM P2 Link to comment Share on other sites More sharing options...
Board of Governors Simon Kelsey Posted December 14, 2016 at 10:30 PM Board of Governors Posted December 14, 2016 at 10:30 PM This is almost certainly a UDP port timeout issue. The best solution is to go in to your router settings and forward UDP ports 3782 and 3290 to your vPilot machine. Vice President, Pilot Training Link to comment Share on other sites More sharing options...
Carl Buchler 1299832 Posted December 15, 2016 at 03:13 PM Author Posted December 15, 2016 at 03:13 PM Are you possibly using a USB headset for vPilot? Sometimes with newer Windows they turn off power to USB ports, flipping frequency will just wake it up. Google "USB power windows" there's a setting to keep them always on. It's an ongoing issue with not just headsets/mic but also peddles, yokes, etc. Im not using USB headset but I will try it anyways thanks Link to comment Share on other sites More sharing options...
Carl Buchler 1299832 Posted December 15, 2016 at 03:14 PM Author Posted December 15, 2016 at 03:14 PM This is almost certainly a UDP port timeout issue. The best solution is to go in to your router settings and forward UDP ports 3782 and 3290 to your vPilot machine. didnt work :/ thanks anyway Link to comment Share on other sites More sharing options...
Norman Blackburn Posted December 15, 2016 at 05:54 PM Posted December 15, 2016 at 05:54 PM This is almost certainly a UDP port timeout issue. The best solution is to go in to your router settings and forward UDP ports 3782 and 3290 to your vPilot machine. didnt work :/ thanks anyway Carl, The UDP timeout is absolutely the issue. This router your are port forwarding on - is it the only router between you and your telco? i.e. this in in your house rather than in a university etc. Norman Link to comment Share on other sites More sharing options...
Carl Buchler 1299832 Posted January 31, 2017 at 07:41 PM Author Posted January 31, 2017 at 07:41 PM This is almost certainly a UDP port timeout issue. The best solution is to go in to your router settings and forward UDP ports 3782 and 3290 to your vPilot machine. didnt work :/ thanks anyway Carl, The UDP timeout is absolutely the issue. This router your are port forwarding on - is it the only router between you and your telco? i.e. this in in your house rather than in a university etc. I forwarded 3782 and 3290 in my router settings to my Vpilot. the router is the only router between me and my telco yes and its in my house. Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted January 31, 2017 at 07:58 PM Board of Governors Posted January 31, 2017 at 07:58 PM Confirm you forwarded UDP ports? Simon and Norman are right --- these symptoms are the cl[Mod - Happy Thoughts]ic symptoms of a port timeout issue. Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Carl Buchler 1299832 Posted February 1, 2017 at 11:39 AM Author Posted February 1, 2017 at 11:39 AM Confirm you forwarded UDP ports? Simon and Norman are right --- these symptoms are the cl[Mod - Happy Thoughts]ic symptoms of a port timeout issue. this is what it looks like: http://prntscr.com/e32tub Link to comment Share on other sites More sharing options...
Norman Blackburn Posted February 1, 2017 at 12:13 PM Posted February 1, 2017 at 12:13 PM Did you map 3782->3290 or is that what your entry looks like? It should be one for 3782 and another for 3290. Norman Link to comment Share on other sites More sharing options...
Carl Buchler 1299832 Posted February 1, 2017 at 12:51 PM Author Posted February 1, 2017 at 12:51 PM Did you map 3782->3290 or is that what your entry looks like? It should be one for 3782 and another for 3290. http://prntscr.com/e33qrr this is what it looks like Link to comment Share on other sites More sharing options...
Norman Blackburn Posted February 1, 2017 at 02:05 PM Posted February 1, 2017 at 02:05 PM That's wrong. That is mapping one port to another. Norman Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted February 1, 2017 at 02:22 PM Board of Governors Posted February 1, 2017 at 02:22 PM You need UDP port forwarding, not mapping. Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 1, 2017 at 02:36 PM Posted February 1, 2017 at 02:36 PM You need UDP port forwarding, not mapping. Different routers use different terms, but they both mean the same thing. He's in the right place. Carl, you only need port 3290, and you only need UDP. Both the WAN and LAN ports should be 3290. (3782 does not require forwarding/mapping.) Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Board of Governors Don Desfosse Posted February 1, 2017 at 03:01 PM Board of Governors Posted February 1, 2017 at 03:01 PM OK, thanks, I had never seen the mapping term before. Don Desfosse Vice President, Operations Link to comment Share on other sites More sharing options...
Carl Buchler 1299832 Posted February 1, 2017 at 07:47 PM Author Posted February 1, 2017 at 07:47 PM You need UDP port forwarding, not mapping. Different routers use different terms, but they both mean the same thing. He's in the right place. Carl, you only need port 3290, and you only need UDP. Both the WAN and LAN ports should be 3290. (3782 does not require forwarding/mapping.) so I changed to only UDP and changed WAN and LAN ports to 3290 and logged on at EHAM (vasterdam), tuned the frequency and after 1 hour I could still hear the atc. thank you for the help everyone! Link to comment Share on other sites More sharing options...
Recommended Posts