PilotEdge Forums

*sigh* Keith, I'm afraid I'm back to square 1 with this. I added the UDP port forwarding back in and was still getting a client crash. Not sure if I happen to be flying at an odd time with odd aircraft in the system or what. Last night I flew for 2 hours with nary a drop and tonight I had to reboot ...

Keith,

Looks like the lack of the UDP port forwarding was the cause. I removed it from the router settings, went to KNSA and sat in GA parking for about 25 minutes and - SHAZAM! - the client froze. I'm using an ASUS RT-966R router if it makes any difference to you.

Took a wonderful 2-hour flight last night from KNSA to KSBP with no trouble at all. Whew!! I will try removing the port forwarding tonight and let you know the results. Thanks for sticking with me on this issue.

Hey Keith,

I went to LAX, set my Multiplayer Visibility to 20 miles and waited. Sometimes I would switch between COM 1 and COM 2 just because I was doing the same thing when the client crashed. I left my plane on the tarmac for almost an hour with no crash. I'm going to try an actual flight later ...

Will do. I'll give it a go when I get home later.

Keith,

I went over to KORD and sat there for a good 20 minutes with no drop. After that, I went back to KSNA and let my plane sit there for about 15 minutes with no crash of the client. Full disclosure alert, I found the port forwarding settings in another post you replied to and plugged those into ...

Thanks, Keith. I'll give it a go and let you know the results.

I tried reducing the Multiplayer Vis down to 3 and the PilotEdge client crashed in about 5 minutes. Is there anything else that could be causing this? I have a copy of Squawkbox installed, but it's not running. Could it be possible that it's causing some issues?

Awesome, thanks! I'll give it a shot.

I don't see a setting for that. Is that a setting on the FSX Settings page or is it something you manage from the config file?