crash to desktop

Only sim crash reporting
Post Reply
abhovi
Posts: 5
Joined: Sat Jan 11, 2020 6:32 pm

crash to desktop

Post by abhovi » Sat Jan 11, 2020 6:44 pm

bugReport.7z
I used 124thatc for a week and everything worked fine.
Suddenly I get a crash to desktop the moment I want to file my flightplan.
I have the latest update for X-Plane and an i7 CPU and GP 1060 GPU. 24 GB Ram. My X-Plane log goes hereby.
Anyone an idea?
You do not have the required permissions to view the files attached to this post.

Andi111882
Posts: 13
Joined: Mon Feb 11, 2019 11:10 am

Re: crash to desktop

Post by Andi111882 » Sun Jan 12, 2020 6:23 pm

It seems that you didn't copy the navdata to the plugins folder as described in the manual:
https://docs.google.com/document/d/1Qcb ... 3cf7nhziz2

Code: Select all

124thATC v2.0-a60 19:24:51: D:\X-Plane 11\Custom Scenery
124thATC v2.0-a60 19:25:20: can't find custom nav data D:\X-Plane 11\Resources\plugins\124thATC64\navdata\earth_nav.dat
124thATC v2.0-a60 19:25:20: reading earth_nav.dat from D:\X-Plane 11\Resources\plugins\124thATC64\navdata\earth_nav.dat
124thATC v2.0-a60 19:25:20: parseSingleNavDat: ILS scanning... D:\X-Plane 11\Resources\plugins\124thATC64\navdata\earth_nav.dat
124thATC v2.0-a60 19:25:20: can't find custom fix data D:\X-Plane 11\Resources\plugins\124thATC64\navdata\earth_fix.dat
124thATC v2.0-a60 19:25:20: Setting file path: 'D:\X-Plane 11\Resources\plugins\124thATC64\Settings.txt'
124thATC v2.0-a60 19:25:20: Settings file could not be found!
124thATC v2.0-a60 19:25:20: Voices file path: 'D:\X-Plane 11\Resources\plugins\124thATC64\Voices.txt'
124thATC v2.0-a60 19:25:20: Voices.txt not found!
124thATC v2.0-a60 19:25:20: User debug enabled
Loaded: D:\X-Plane 11/Resources/plugins/124thATC64/win_x64/124thATC64.xpl (matacchieri.eu.124thatcv2).
However I do not know if that caused the plugin to crash.

There are also some issues with frequencies (these issues are not related to your flight plan, but maybe worth to look at if you like):

Code: Select all

0:01:12.630 E/APT: Found a bad frequency for the Tower controller at LEZG: 139.300. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: The airport LEZG (Zaragoza) has lost some controllers due to bad frequencies.  Each controller needs at least one frequency in the range of 118.00 to 136.990 mhz.
0:01:12.630 E/APT: We found a solitary GND controller at LEZG (Zaragoza). Where's his tower controller?
0:01:12.630 E/APT: Found a bad frequency for the Tower controller at 6K4: 115.400. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: The airport 6K4 (FAIRVIEW MUNI) has lost some controllers due to bad frequencies.  Each controller needs at least one frequency in the range of 118.00 to 136.990 mhz.
0:01:12.630 E/APT: Found a bad frequency for the CTAF controller at VOTV: 112.850. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the Center controller at RJAW: 138.300. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the Approach controller at RJAW: 138.300. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the CTAF controller at LSXG: 159.670. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the CTAF controller at LSXG: 159.200. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the CTAF controller at LFBG: 142.450. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Ramp start "Default" is located too far away (more than 6 km) from the airport NFMO
0:01:12.630 E/APT: Found a bad frequency for the Approach controller at PAUN: 137.500. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the CTAF controller at KMGJ: 116.100. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the CTAF controller at YSHR: 114.400. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the Center controller at MMLP: 112.300. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the CTAF controller at XCAW4: 158.760. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the CTAF controller at YSPI: 116.900. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the CTAF controller at YMVM: 113.200. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the Approach controller at KSAV: 109.900. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the Approach controller at KSAV: 111.900. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the Tower controller at LEBZ: 139.300. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: The airport LEBZ (Badajoz- Talavera La Real) has lost some controllers due to bad frequencies.  Each controller needs at least one frequency in the range of 118.00 to 136.990 mhz.
0:01:12.630 E/APT: Found a bad frequency for the CTAF controller at YGFN: 112.400. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the Tower controller at LELC: 139.300. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: The airport LELC (Murcia San Javier) has lost some controllers due to bad frequencies.  Each controller needs at least one frequency in the range of 118.00 to 136.990 mhz.
0:01:12.630 E/APT: We found a solitary GND controller at LELC (Murcia San Javier). Where's his tower controller?
0:01:12.630 E/APT: Found a bad frequency for the Approach controller at LPOT: 144.000. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Found a bad frequency for the Tower controller at KTCM: 109.600. It should be between 118.000 and 136.990.
0:01:12.630 E/APT: Ramp start "Default" is located too far away (more than 6 km) from the airport NFFR
0:01:12.630 E/APT: Found a bad frequency for the Tower controller at SBFL: 112.800. It should be between 118.000 and 136.990.
0:01:12.630 I/NAVT: NavData is done loading async...

ntnll
Posts: 519
Joined: Sun May 13, 2018 12:32 pm

Re: crash to desktop

Post by ntnll » Sun Jan 12, 2020 9:08 pm

abhovi wrote:
Sat Jan 11, 2020 6:44 pm
bugReport.7zI used 124thatc for a week and everything worked fine.
Suddenly I get a crash to desktop the moment I want to file my flightplan.
I have the latest update for X-Plane and an i7 CPU and GP 1060 GPU. 24 GB Ram. My X-Plane log goes hereby.
Anyone an idea?
Thanks for reporting abhovi, I'll have a look into it.

Thanks Andi111882, you definitely right, abhovi follow the instructions for a correct navdata installation. It should not be cause of the crashes, but a correct installation is advised.

Moving the thread in the correct (crash reports) section
124thATC Developer

abhovi
Posts: 5
Joined: Sat Jan 11, 2020 6:32 pm

Re: crash to desktop

Post by abhovi » Mon Jan 13, 2020 7:34 am

Hello,
Thanks for your kind answer. And of course for creating this great plugin.

I installed 124thATC only last week and everything worked excellently. Until I used LFPG and LFPO. At both airports I got this ctd. Later on I noticed that other airports, like EGSS and EHAM caused no problems. So indeed some airports are the causes of the crash.

I must admit that I did not study the manual extensively yet because everything seemed to be working so well. My question is: can I discover which airports need navdata and which don't apart from getting crashes in ? Also, the proces of how to do this is not completely clear to me.

Another question: I would like to donate, but I have serious problems with Paypal. Is there another way to show my appreciation financially?

abhovi
Posts: 5
Joined: Sat Jan 11, 2020 6:32 pm

Re: crash to desktop

Post by abhovi » Fri Jan 17, 2020 9:13 am

According to the manual a frequency has to be added in the earth.nav/apt file. I opened that file and the frequencies were there already. I compared the way they were written with a comparable apt. file from an airport where 124thATC did work and spotted no difference.
Could you please elaborate on the reasons why your program works flawlessly in many airports, but causes crashes in others? I cannot finds any difference in the frequencies.

Oh, and my question about donating in a different way than Paypal was not answered yet...

ntnll
Posts: 519
Joined: Sun May 13, 2018 12:32 pm

Re: crash to desktop

Post by ntnll » Sun Jan 19, 2020 11:35 am

abhovi wrote:
Mon Jan 13, 2020 7:34 am
Hello,
Thanks for your kind answer. And of course for creating this great plugin.

I installed 124thATC only last week and everything worked excellently. Until I used LFPG and LFPO. At both airports I got this ctd. Later on I noticed that other airports, like EGSS and EHAM caused no problems. So indeed some airports are the causes of the crash.

I must admit that I did not study the manual extensively yet because everything seemed to be working so well. My question is: can I discover which airports need navdata and which don't apart from getting crashes in ? Also, the proces of how to do this is not completely clear to me.

Another question: I would like to donate, but I have serious problems with Paypal. Is there another way to show my appreciation financially?
Hi abhovi,
generally speaking navadata are used in any airport when "Look for SIDs and STARs" is selected in the flight plan dialog. Try to disable this flag, and see if it fixes the issue. Are you using custom airports while experiencing the crashes?
What kind of problems do you have on Paypal, are problems with your account, or 124thaATC links? Unfortunately there are no any other way to pay at the moment.
Have you installed the Navdata in D:\X-Plane 11\Resources\plugins\124thATC64\navdata\ ?
124thATC Developer

abhovi
Posts: 5
Joined: Sat Jan 11, 2020 6:32 pm

Re: crash to desktop

Post by abhovi » Sun Jan 19, 2020 4:23 pm

In the manual I read nothing about inserting nadata into the nadata into the 124thATC/navdata file. Which nadata should I put there? Also in the installation instructions nadata are not mentioned.

Yes, I do have a lot of custom airports. I think there are a thousand of them, together with all necessary Ortho4XPlane tiles for entire Europe and North America.

My problems with Paypal is that they are able to (and will) take money from your bankaccount if they are billed by someone who thinks you owe him something, without checking if that is right. I experienced this with MacAfee, of which I appeared to have a subscription. Nobody told me that I had to pay every year. I thought is was a onetime payment. That was in itself odd, but much odder was, that Paypal simply took the money from my bank account because I had no money on my Paypal bill. I didn't know that was necessary, because I have a bankaccount already somewhere else. Both Paypal and MacAfee were punished for this behavior, I think they paid 400.000 dollars fine, but no signs of any improvement. So I ended my account there, which is sometimes problematic, especially if I want to donate to people who have made nice and useful things.

I will try and see what happens if I remove the tick for SIDS and STARS and will let you know.
Thank you for your attention.

abhovi
Posts: 5
Joined: Sat Jan 11, 2020 6:32 pm

Re: crash to desktop

Post by abhovi » Sun Jan 19, 2020 6:02 pm

I just tested to untick both Look for SIDS ands STARS and manual input. No difference. Ctd.

ntnll
Posts: 519
Joined: Sun May 13, 2018 12:32 pm

Re: crash to desktop

Post by ntnll » Sun Jan 19, 2020 8:57 pm

abhovi wrote:
Sun Jan 19, 2020 6:02 pm
I just tested to untick both Look for SIDS ands STARS and manual input. No difference. Ctd.
Is quite strange. Did you had this issue also with the previous .59 version?
124thATC Developer

Post Reply