PilotEdge Forums

Last night, had same crash problem as described above. Have also reinstalled the plugin, and will see if it cures things later today. Yosemite is hardly trouble-free...

Good luck! On one level, I hope it doesn't work—just because I took the same measures and they have not worked for me.
(Nothing personal...)

Let us know!

sgabriel wrote:...but not the X-Plane crash log.

It's the log.txt file we need to see in order to help you, not the crash log. X-Plane ALWAYS creates a log.txt file no matter how it shuts down or crashes. The log.txt tells us what your X-Plane installation is doing and what plugins you're using that might be causing conflicts.

Well, I lowered my resolution under rendering (including dropping the clouds to around 30%), and flew the Carenado Seneca on a test VFR flight under PE today. Worked like a charm. Good frame rate, and no crashes. Next, I'll try upping the resolution a notch, as taxiway signs and so on are blurred, and the ground looks a bit like mushy pea soup

sgabriel wrote:Update:

Dammit! Just enjoyed a perfect flight from KLGB to KSBA with flight following. Upon disconnecting from the PE network, X-Plane crashed to desktop, again issuing the Apple crash report (attached), but not the X-Plane crash log.

Argh.

X-Plane.Crash.2014.11.1.rtf

So may should have mentioned this. This does happen to me as well if I do not disconnrct from PE. As long as I disconnect from PE and then quit,,,no crash. Stay connected I get the crash to desktop.

I once had a crash by turning the avionics off before disconnecting from PE - and that was in Mavericks. Like sgabriel, but he did not state if he shut the plane down first. I don't think this problem is OS related - more likely the plugin. However, Keith is looking at the problems iMac users are reporting.

Turning off the avionics causes you to move to a voiceroom that has the same name as your callsign. A problem was reported with the linux plugin were 6 character callsigns were causing memory overflows (something I'll look into).

Can you see if if you can replicate the crash (turning avionics off, or connecting to PE with avionics off) with 6 character callsign, then see if a 5 character callsign makes a difference on the Mac?

Hey Keith. So I have been traveling but had some time on my hands so I loaded X-Plane up on my Mac Air I have with me (no comment on burning up the hotels bandwidth,,,not sure I would do this again )

Sooooooo...I can reproduce the issue on the Mac Air Avionics on or off it crashes to the desktop if you are connected to PilotEdge and quit X-Plane. Not a huge issue mind you as I am exiting the program anyway. If I log out of PilotEdge is exits normaly and all happy.

Crash report is attached. Hope it helps. If you need me to try another test I can. I have it loaded now and while not sure I would want to fly with this configuration I can at least test for you.

Ok very good, that should be fixable, will look into it when I return from this trip on Friday.

Keith Smith wrote:Turning off the avionics causes you to move to a voiceroom that has the same name as your callsign. A problem was reported with the linux plugin were 6 character callsigns were causing memory overflows (something I'll look into).

Can you see if if you can replicate the crash (turning avionics off, or connecting to PE with avionics off) with 6 character callsign, then see if a 5 character callsign makes a difference on the Mac?

Sorry, Keith.

Have been away for most of the week. If you still want me to try the "test" with callsign lengths, I will. Let me know.