Hello,

Installed the current Update C414 (company name change).

CTD when I click on the PMS50 GTN 750

 

Edited October 23, 20223 yr by vonmar

1 hour ago, vonmar said:

Hello,

Installed the current Update C414 (company name change).

CTD when I click on the PMS50 GTN 750

 

I cannot replicate your problem, the PMS50 GTN750 works fine for me with the latest C414 update. Are you using the latest PMS50 GTN750 version, 2.1.47?  Also, if you happen to have a Heavy Division 787 mod in your Community folder, try removing it and restarting the sim. I expect Heavy Division will be coming out with an update to that mod, but the original one prevented the C414 EFB and GTN750 screens from working.

Al

 

Edited October 23, 20223 yr by ark

Ark ,

Thanks for the reply.

I now used the Simmarket App (again) to Uninstall / reinstall and it is now working.

Edit : I do not use the Division 787 mod.

 

Failed to mention in my first post that in a second test (after the PMS50 CTD) I selected an aircraft with the GNS 530 and it did not CTD.

 

 

Edited October 23, 20223 yr by vonmar
added info

Hello Ark,

I just checked the pms50 documentation.pdf (10-14-2022) and the change log shows version 2.1.46
Next I checked the pms50 GTN70 status page and it also shows version 2.1.46

5 hours ago, vonmar said:

 

Hello Ark,

I just checked the pms50 documentation.pdf (10-14-2022) and the change log shows version 2.1.46
Next I checked the pms50 GTN70 status page and it also shows version 2.1.46

No, sorry, I don't know what the PMS50 GTN status page is, but the latest version of the PMS50 GTN750 is 2.1.47 as you can see from the shot below from the PMS50 website, https://pms50.com/msfs/    I downloaded this version a few days ago, and the manifest.json file also shows it to be ver 2.1.47.  Note on the website PMS50 describes this as a Mandatory Update.

Al

Edited October 24, 20223 yr by ark

Hello Ark,

I was just answering your question by telling you which pms50 version I was using.
I had no knowledge of a newer version until I seen your post.

Later I installed pms50 version 2.1.47.

Note: 
pms50 version 2.1.46, as I previously mentioned, worked ok on my test at that time.

Screenshot of my current pms50 status page.

 

 

4 minutes ago, vonmar said:

I was just answering your question by telling you which pms50 version I was using. I had no knowledge of a newer version until I seen your post. Later I installed pms50 version 2.1.47.

Ah, OK, great.  Glad you have it all working now!  🙂

Al

1 hour ago, ark said:

Ah, OK, great.  Glad you have it all working now!  🙂

Al

Just a quick follow up to confirm:

Actually C414 was working after I reinstalled it (looking back several posts).

Pms50 versions 2.1.46 and 2.1.47 both worked with the new C414 (company name change) Update.



I now went back to read about the mandatory pms50 update (version 2.1.45). 
Note: Pms50 version 2.1.47 was never mentioned in “Read more” the mandatory note:
https://pms50.com/msfs/mandatory-update/

Mandatory update
 
IMPORTANT
Microsoft changed its virus detection table on October 7 causing a case of false detection in our GTN750 package v2.1.44. This may break your aircraft avionics including some other gauges.
 
We assure you that the code does not contain any virus and that it is indeed a case of false detection. Only windows defender detects it.
 
GTN750 new version 2.1.45 fixes the false positive virus detection. Thank you to update to the latest version if you get the defender issue.

Download and install the latest package (v2.1.45 minimum) in your community folder.

Edited October 24, 20223 yr by vonmar

1 hour ago, vonmar said:

Microsoft changed its virus detection table on October 7 causing a case of false detection in our GTN750 package

Yep, I read that a week or so ago. Just a heads up in case any future updates of the GTN750 result in a virus warning. 

It is useful to read the change logs to see why the GTN750 was updated. For example, here are the change logs for the last two updates:

v2.1.47
Adding L variables for Knob state and current COM/NAV index.
Entering OBS mode now displays a page to set the OBS angle.
Adding TAF weather data in airport info page.
WTT mode: allow removing an approach waypoint while the approach is active.
v2.1.46
SU11 compatibility (still compatible with SU10).
Bugfix: can't add an enroute waypoint when a STAR is loaded.
Altitude constraints can now be set to max 49900ft instead of 19900ft.
Bugfix: the VCALC utility was giving bad information for approach waypoints.
Bugfix: the map field DIS (distance) was changing too early.
City information is not displayed anymore for waypoint info (except for airports) because
there is currently an Asobo issue with city data.
Fixed some bugs for departure and arrival selections.
WTT mode: possibility to select an arrival or departure procedure without transition when available.
Adding a way to share a bank of user waypoints across aircraft

 

Al

Edited October 24, 20223 yr by ark