PilotEdge Forums

I noticed similar issues:

XP 10.11, Mac (latest and greatest), no plug-ins except the PE plug-in, X-Plane default Baron:

Sometimes I start XPlane, connect to PE and just listen to ATC. Step away, come back, etc. In other words, I'm not flying or talking. Then, after half an hour or an hour or so I get ready to fly, make a request to ATC, don't get a response. I can hear ATC talking to others. Then I go to the PE online map and look at my frequency. I change the frequency in X-Plane. Online map still shows my previous frequency, even after a minute or so. I can still hear ATC. Disconnect PE, reconnect. Online map still shows my initial frequency from the first session, even though I had a different frequency after reconnecting. Then I quit X-Plane, start it again, connect to PE, everything's working just fine.

This happened 3 times over the last week.

Here's one pointer: I'm with Comcast (New Jersey), and sometimes their Internet service slows down in the evening. However, I'd think that the PE client would disconnect when my Internet connection is bad or lost (like it did on other occasions). But the fact that I can hear ATC just fine would mean that my Internet connection is good enough, but maybe there was an intermittent Internet connection issue on my side and the PE client didn't recover, but it also didn't disconnect?

Are you leaving your engine running while you step away for 30 mins? If not, your battery is probably running out and we're killing the radio. We model that in X-Plane.

It was more than half an hour with the engine off, but I did hear the ATC talk to other pilots. They just didn't respond to me, and when I changed the frequency, I noticed that the PE online map didn't show the new frequency.

Thanks Christoph. There's still a chance it's that, and that it simply failed to move you into the 'dead battery' area of the voice server. If it happens again, stay connected and PM me, and/or, email me the vspro.out file in the xplane root directory.

Will do!

I have been seeing the same thing using FSX. I will be talking to ATC just fine, then my comms will stop working. When I ALT-TAB back to the PilotEdge app, it's frozen in a not responding state and I can't get it back. I kill the app and restart, but it happens again after about 15 minutes.

I would be happy to send some log files over so you can have a look. Just let me know what you need. I'm using Win 7 64-bit.

utexgrad, that's a full on app crash for a completely different client. That's a bit different

I would like to try and debug that, though! There are no known issues that cause PE to crash that I'm aware of at the moment, other than if your connection to the server is lost (I haven't tested that one in a while).

And now for something completely different... Sorry, couldn't resist; It's Pavlovian response to anything resembling a Monty Python quote.

I flew from Catalina to Ramona several times with no issues, but every time I tried to fly from John Wayne to San Luis, the app would die. Maybe the server connection is getting dropped, but there are no messages in the client to that effect.

Try reducing your multiplayer vis down to 3 miles (as an example) and see if you have the issue. Some users' machines just don't like having a lot of AI aircraft in the system.

Aghhhhhh... The loss of coms issue happened again this evening 45 minutes in to a flight where I was just being vectored to land at KLAS. (practicing I-5)

Again, I could hear the controller, controller could not hear me. I was in a Citation Mustang, and wasn't running any external instrumentation this time.

I stopped, restarted VSPro, did not resolve, still he could hear me, I couldn't hear him.

I then hit "Start Debug" on VSPro, and X-Plane crashed.

(sigh)

Brett