PMS50 GNS530 mod

Hello

The CTD occurs when manipulating a GPS button?
There is no relashionship between the weather and the GPS. Maybe this is something else but I will try your FPL.

I was suspecting that the vnav page was the problem but no. There is no difference. One flight (5) i didnt touch anything there except of putting flight plan before take off and still i had CTD. In my last flight with clear sky i put the vnav info and checked other screens and it was just fine. No CTD. But all CTD were when i was just flying, no CTD occured when i was manipulating buttons.

Currently running your FPL with m20R at live time/weather. No issue until now. Iā€™m at 40nm from the destination.

Is it expected, that any LNM ,fpl file imported to the GNS530 Mod will not have any LNM USER Waypoints, visible in the GNS530 displayed FP ??

Iā€™ve tried this now in another region. So direct flight from EPKM to EPKK, live weather and time and had CTD during my final.

Didnā€™t get any issue on your Flight plan, I reached the destination correctly.
Donā€™t know what to do here.

Waypoint must have a valid ICAO to be taken in care. Not the case for user waypoints.
We need both the ICAO Ident and the region.

Thatā€™s a shame ā€¦ I assume thats a failing in MSFS ?

So a WP name and lat/Long is not enough for MSFS ?

Sure, Iā€™m gonna download older version and check next updates after some time.

Maybe itā€™s possible. I have that on my todo list.

The question is: somebody else has this kind of issue ?

i can also vouch for this. m20R into TJSJ runway 10. as soon as I capture glide slope CTD.

Thanks ā€¦ Reason for request ā€”

I made a great FP for the CannonBall Run in LNM, that routed through the Rockiesā€™s canyons, with user WPs, but then when I loaded it into the Garmin, none of the user WP were there.

Had to end up manually flying, with reference to the FP displayed on LNM.
If the GNS530 could have followed my LNM FP with User WPs, it would have been great ā€¦

Got no issue here at all. Perfect fly.
TJRV/TJSJ Approach ILS10 transition KOTME.
Correctly captured the glidescope and landed. No CTD.
Are you able to reproduce this issue?

I havenā€™t gotten a CTD yet, but, it would be helpful to know how to capture the crash log?
Thatā€™s probably the next step.

yes happens every time I fly the

Ok so please check the bug reporting steps in the readme or at the top of this topic.
I will need the exact way to reproduce the issue.

1 Like

A direct To should not modify the flight plan except maybe if your direct TO target is an airport.

For the very first time, and about 20 minutes before the touchdown on a 4 hr flight with the Mooney, Iā€™ve also had a CTD. I doubt its related, or fault of the GPSā€¦ except for the weather radar feature, I wasnt using it.
Hereā€™s the dump anyway, if someone can make sense of it.

Log Name: Application
Source: Application Error
Date: 28.12.2020 18:09:42
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ryzenPC
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba
Exception code: 0xc0000005
Fault offset: 0x000000000011639a
Faulting process id: 0x2180
Faulting application start time: 0x01d6dd153ecc19a9
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 7871bdc0-4b9d-4849-b9b4-e330aeb75820
Faulting package full name: Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:



1000
2
100
0x80000000000000

42706
Application
ryzenPC



FlightSimulator.exe
0.0.0.0
5fda32ba
FlightSimulator.exe
0.0.0.0
5fda32ba
c0000005
000000000011639a
2180
01d6dd153ecc19a9
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
7871bdc0-4b9d-4849-b9b4-e330aeb75820
Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe
App

Well, pretty much the only thing I got out of the log, is that youā€™re using an AMD product, and, apparently, it was a Classic CTDā€¦ :wink:

Sorry I couldnā€™t be of further help.

(sorry, when I read keywords: Classic, I had to respond)