Jordan Robinson 1362626 Posted October 15, 2016 at 03:07 PM Posted October 15, 2016 at 03:07 PM So, I was flying from Doha to Austin recently. The simulator crashed whilst I was flying over ORD, 15HRS INTO MY FLIGHT! This is confusing and odd. The old version (prior to the new x plane update), was VERY stable and NEVER (and i mean NEVER) crashed...EVER. This new update crashes more and more and I want to isolate the problem. I wonder if it is xsquawkbox's fault (and if so if there is an alternative for xp), or my computers fault, or x planes fault. I use a Mac OS X El Capitan Intel Core i5. Any suggestions that might help me? This is sad and I worry that CROSS THE POND (something I have looked forward to for a VERY long time), will be ruined for me if my simulator crashes during the event. Thank you for your help, -"I just want to tell you both good luck. We're all counting on you." Link to comment Share on other sites More sharing options...
Ernesto Alvarez 818262 Posted October 15, 2016 at 03:08 PM Posted October 15, 2016 at 03:08 PM check the crash report Link to comment Share on other sites More sharing options...
Jordan Robinson 1362626 Posted October 15, 2016 at 03:12 PM Author Posted October 15, 2016 at 03:12 PM check the crash report In x plane log.txt? -"I just want to tell you both good luck. We're all counting on you." Link to comment Share on other sites More sharing options...
1275389 Posted October 15, 2016 at 03:14 PM Posted October 15, 2016 at 03:14 PM In x plane log.txt? Yes. Please post a pastebin link to it. Link to comment Share on other sites More sharing options...
Jordan Robinson 1362626 Posted October 15, 2016 at 03:19 PM Author Posted October 15, 2016 at 03:19 PM In x plane log.txt? Yes. Please post a pastebin link to it. http://pastebin.com/28jV3H51 -"I just want to tell you both good luck. We're all counting on you." Link to comment Share on other sites More sharing options...
Mathew Sutcliffe Posted October 15, 2016 at 04:52 PM Posted October 15, 2016 at 04:52 PM In the time between experiencing the crash, and uploading the Log.txt, you have run X-Plane again, so the Log.txt from the crash has been overwritten by that subsequent run of X-Plane. Nevertheless, I can still tell that your XSquawkBox has been installed wrongly. In the zip file that you download there is an XSquawkBox folder. What you have done is extract the contents of that folder into your plugins folder. What you should have done is extract the folder itself into your plugins folder, so that you have an XSquawkBox subfolder inside your plugins folder. On line 56 of Log.txt you had this: Loaded: /Users/jordanrobinson/Desktop/X-Plane 10 Global/Resources/plugins/mac.xpl (vatsim.protodev.clients.xsquawkbox). But it should be this: Loaded: /Users/jordanrobinson/Desktop/X-Plane 10 Global/Resources/plugins/XSquawkBox/mac.xpl (vatsim.protodev.clients.xsquawkbox). ^^^^^^^^^^^^ Also, like many recent payware planes, FlightFactor 777 uses the SASL plugin, which has been implicated in conflicts with XSquawkBox before. swift - Developer Link to comment Share on other sites More sharing options...
Jordan Robinson 1362626 Posted October 16, 2016 at 01:51 AM Author Posted October 16, 2016 at 01:51 AM In the time between experiencing the crash, and uploading the Log.txt, you have run X-Plane again, so the Log.txt from the crash has been overwritten by that subsequent run of X-Plane. Nevertheless, I can still tell that your XSquawkBox has been installed wrongly. In the zip file that you download there is an XSquawkBox folder. What you have done is extract the contents of that folder into your plugins folder. What you should have done is extract the folder itself into your plugins folder, so that you have an XSquawkBox subfolder inside your plugins folder. On line 56 of Log.txt you had this: Loaded: /Users/jordanrobinson/Desktop/X-Plane 10 Global/Resources/plugins/mac.xpl (vatsim.protodev.clients.xsquawkbox). But it should be this: Loaded: /Users/jordanrobinson/Desktop/X-Plane 10 Global/Resources/plugins/XSquawkBox/mac.xpl (vatsim.protodev.clients.xsquawkbox). ^^^^^^^^^^^^ Also, like many recent payware planes, FlightFactor 777 uses the SASL plugin, which has been implicated in conflicts with XSquawkBox before. Okay, that makes sense. I have fixed the install, but because fo SASL conflicts, in order to insure no crashes during cross the pond, would you recommend I don't take a SASL plane because of the conflicts with Xsquawkbox? Thanks. -"I just want to tell you both good luck. We're all counting on you." Link to comment Share on other sites More sharing options...
David Lovell Posted October 16, 2016 at 07:02 AM Posted October 16, 2016 at 07:02 AM I'm wondering why everything was fine for 14 hours and then it crashed. If it was the XSB installation, that's fixed. If it was the aircraft, why after 14 hours? I wonder whether it's scenery or weather? I'd probably start on a ramp in the region of where it crashed and see what happens? I've had to remove my weather plugins since XP 10.50, as weather updates caused crashes, for example. Link to comment Share on other sites More sharing options...
Thimo Koolen Posted October 16, 2016 at 09:14 AM Posted October 16, 2016 at 09:14 AM I can't count the amount of times I had FSX or P3D crash during an oceanic crossing. Once I was starting my descend into KJFK and a Boston Center controller came online. I switch frequency and P3D crashes. That's not really fun. ACCNL4 (Training Director) - Dutch VACC Link to comment Share on other sites More sharing options...
Jordan Robinson 1362626 Posted October 16, 2016 at 01:59 PM Author Posted October 16, 2016 at 01:59 PM I'm wondering why everything was fine for 14 hours and then it crashed. If it was the XSB installation, that's fixed. If it was the aircraft, why after 14 hours? I wonder whether it's scenery or weather? I'd probably start on a ramp in the region of where it crashed and see what happens? I've had to remove my weather plugins since XP 10.50, as weather updates caused crashes, for example. Well, then the aircraft can probably be ruled out since it was fine. I think it could be scenery as it crashed as soon as I (shift-4) looked at the exteior of the aircraft and panned around, and it crashed then. The most likely problem is scenery, however, I spawned in the ramp and it loaded the crash area (near and around KORD), a little laggy midn you, but still just fine -"I just want to tell you both good luck. We're all counting on you." Link to comment Share on other sites More sharing options...
Recommended Posts