Crashes with X-Plane

[Chicken Patty]

Hello all,
Decided to give the free trial a run for 14 days, and I absolutely so far love PE. i completed my first flight, pretty much issue free. Just a minor misunderstanding with Vegas Controller, but he cleared it up, and was very nice, and prompt about it. So I landed, all went good. I try to do my 2nd flight, and as I'm climbing out of KLAS, the sim locks up, stops responding. I had to close it. Today I tried again, descending into LAX, same thing. It seems to happen right after a voice transmission. I had a similar issue when flying online with VATSIM, and using XSquawkbox. Sometimes I would press the PTT and the SIM would just CTD. Anybody have any idea what might be going on, or has experienced this before? I can't do any online flying with voice if I use X-Plane. I can use FSX, and it is not an issue. Considering how much I enjoy online flying, this is eating at me one piece at a time.

Thanks in advance for your help, and if you need any further information, please don't hesitate to ask.

-David

[Keith Smith]

Sorry to hear that. Would need to see the crashlog from xplane to have any hope of working out what's causing that. However, I've never heard of a PTT causing a crash to desktop in xplane as far as I can recall, so something odd is going on.

[wmburns]

I seem to recall there was an "issue" with Xsquawkbox and PE installed on the same X-plane PC. Something about a duplicate DLL. Note, it's been a long time since I have used Vatsim. My memory maybe dated.

Suggestion. It's very easy to create an alternate X-plane instance. This is very useful for beta testing and fault isolation. Simply copy the entire X-plane directory to a new location. I use X-Plane-beta. Once copied run the x-plane.exe from the new location. X-pane does not use windows registry to store/save installation information as other programs do.

For most people HD space is not an issue if using mechanical drives. I use this option to test any new Beta versions of X-plane before committing to the main sim set up.

From the new instance, delete any/all non standard add on software within x-plane (esp Xsquawkbox plugin). The idea here is to re-create the problem with as basic as possible system. Use the default x-plane aircraft as well. This helps to control the number of variables.

If it still crashes, as Keith said, the x-plane log.txt file is vital.

If it stops crashing, then add back in add-on's one at a time until the offending item is found.

Good luck.

[Chicken Patty]

Sorry to hear that. Would need to see the crashlog from xplane to have any hope of working out what's causing that. However, I've never heard of a PTT causing a crash to desktop in xplane as far as I can recall, so something odd is going on.

I've attached the crash log. I personally see nothing out of the ordinary.

I seem to recall there was an "issue" with Xsquawkbox and PE installed on the same X-plane PC. Something about a duplicate DLL. Note, it's been a long time since I have used Vatsim. My memory maybe dated.

Suggestion. It's very easy to create an alternate X-plane instance. This is very useful for beta testing and fault isolation. Simply copy the entire X-plane directory to a new location. I use X-Plane-beta. Once copied run the x-plane.exe from the new location. X-pane does not use windows registry to store/save installation information as other programs do.

For most people HD space is not an issue if using mechanical drives. I use this option to test any new Beta versions of X-plane before committing to the main sim set up.

From the new instance, delete any/all non standard add on software within x-plane (esp Xsquawkbox plugin). The idea here is to re-create the problem with as basic as possible system. Use the default x-plane aircraft as well. This helps to control the number of variables.

If it still crashes, as Keith said, the x-plane log.txt file is vital.

If it stops crashing, then add back in add-on's one at a time until the offending item is found.

Good luck.

I've attached the file for you to review as well if you can. I will also try your suggesiton above. I currently do not have Xsquawkbox installed, as I removed it when it was giving me issues. But I will do the above when I have a bit of time. Thank you both

[Marcus Becker]

Looks like you still have some X-Squawkbox materials still there. Quite a few instances that are pulling errors.

Example:
XSB WARNING: package 'E:\Program Files\X-Plane 10\X-Plane 10 Regional - North America\Resources\plugins\PilotEdge\VSPro Resources\CSL/Baron' could not be opened. Error was: No such file or directory.

Beyond that, there are a lot of other errors there you may want to start looking at fixing. They may not fix this particular issue but they can create all sorts of problems.

[wmburns]

I see a number of program loading errors.

I also see Gizmo and Skymaxx being installed. Gizmo is well known for certain versions causing problems.

Also saw errors in the log loading the PE client. It might be a good idea to completely remove the PE plugin and re-install the latest version.

IMO your trouble shooting will be greatly advanced by having a Beta/test system to work with.

[stevekirks]

the XSB warning is from the PE client since it uses Xsquawkbox as a code base. The file that can't be opened has a flaw in the forward slash between CSL and the aircraft name. Since the crashes are happening on PE and the CSL filepath is messed up, that seems like the mostly likely answer. A reinstall of the PE client would help--don't add any extra CSLs at this point like the FlyJSim HD ones that were listed. Just pull a fresh copy and use that for now.

[Chicken Patty]

Thank you all. I will check carefully, and remove all instances of XSB. Although folder is not in, I guess there are still some misc files somewhere else. I will look into it. I will also re-install the PE client, and not add any CSL's. Will revert, thanks.