All Carenado aircraft transferred to MSFS2024 have non functional GNS530

Bug Reporting Hub Aircraft & Systems
, , , ,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue:
Carenado aircraft in 2024 library using incorrect (inoperable) Garmin 530 units.

If applicable, which aircraft is experiencing this issue:

Aircraft made by Carenado and transferred to MSFS2024
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes

FREQUENCY OF ISSUE

Every flight
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
All the time

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Load any Carenado aircraft
    2.Hit fly
    3.Observe the Garmin units don’t accept waypoints/non functional

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:
None relavent

[PC Only] Are you using Developer Mode or have you made any changes to it?
No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?

RTX470Ti super
[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

1 Like
2

I have the same issue with all Carenado aircraft with garmin 430s. Did you ever resolve this issue?

1 Like
3

Someone gave me a file which fixed the issue for the Mooney. Probably easily adaptable for the other aircraft but I dont know how. Probably something simple like a cfg or json edit.

1 Like
4

Do you have the same issue if you follow the OP’s steps to reproduce it?
• yes, the issues exist for all users

Provide extra information to complete the original description of the issue:
• this appears to happen on Xbox as well as pc

If relevant, provide additional screenshots/video:
• the original poster’s screenshots and videos are sufficient.

1 Like
5

I can verify the same issue with the Carenado Mooney.

GNS 530 is not working in latest SU1 Beta.

OP has details I am experiencing.

RTX 4080 Super, latest NVidia drivers.

1 Like
6

SU1 final build and the recent SU2 BETA and same issue as OP, I mainly fly the Beechcraft 18, another carenado build. SU2 BETA also seemed to break the (load flight plan to avionics), only way I can get a flight plan on the Garmin in that plane.

7

Ah HA! Found a fix on reddit. I modified the Beechcraft 18 panel.cfg file to use the Working Title garmin and everything works great! Will update if maybe something is broken in the process.

https://www.reddit.com/r/MicrosoftFlightSim/comments/15tlhwp/protip_just_because_the_workingtitle_gns530_is/

For anyone interested I have uploaded my Beechcraft 18 mod file, I use this within the Denarq mod files and it works fine with that.

https://flightsim.to/file/90478/beechcraft-18-garmin-gns530-working-title-version

Based on that reddit post, the minor modification to the panel.cfg file should work on all carenado planes to change it to the working title version. Just dont change the “Texture” from AS530 or youll get a white screen.

1 Like
8

Aha!!! I have a mod file to do this too but I couldn’t find the Beech config file and assumed it was because it was encrypted.

Does this mean I just have to download your mod from Flightsim.to, drop it into my 2024 community folder and I get a Beech with a working 530 again?

If so; I love you! :rofl:

9

Yes, the mod replaces the default Asobo 530 with the Working title 530. I did this by following the reddit guide. For anyone curious, I was able to get the panel.cfg file by using the Virtual File System through DEV mode. That gives you access to everything, including aircraft files that are outside of the Standard edition planes.
My mod also works well in conjuction with the Denarq mod

1 Like
10

It is worth noting that IF you use the wb-sim C172 MOD for your Asobo (Carenado ?) MSFS 2020 C172 Classic, that has been moved across to 2024, the wb-sim panel.cfg file already calls up the WT GPS system, so no user FIX is needed in this particular case.

**

Note: The latest Asobo MSFS 2020 C172 Classic, still seems to be trying to use the Asobo AS430 & AS530 GPS gauges.

**

ie CURRENT Asobo MSFS 2020 C172 Classic Panel.cfg file

[VCockpit05]
size_mm				= 350,190
pixel_size			= 350,190
texture				= $AS430_Screen
htmlgauge00=NavSystems/GPS/AS430/AS430.html, 		0, 0, 350, 190

[VCockpit06]
size_mm				= 320,234
pixel_size			= 320,234
texture				= $AS530_Screen
htmlgauge00=NavSystems/GPS/AS530/AS530.html, 		0, 0, 320,234

ie ** MSFS 2020 C172 Classic Panel.cfg file edited to use the Working Title GPS **

[VCockpit05]
size_mm				= 350,190
pixel_size			= 350,190
texture				= $AS430_Screen
htmlgauge00=NavSystems/GPS/WT430/WT430.html, 0, 0, 350, 190

[VCockpit06]
size_mm				= 320,234
pixel_size			= 320,234
texture				= $AS530_Screen
htmlgauge00=NavSystems/GPS/WT530/WT530.html, 0, 0, 320, 234

OBVIOUSLY. edit these files at your own risk, and keep backups in case your Edits “BREAK” things :face_with_bags_under_eyes:

Note: It looks like previous version of the 2020 C172 Classic (SU15) was correctly using the WT GPS Gauges, but the recent mid MARCH 2025 updates to these Carenado ? planes may have reverted their GPS systems to the Asobo version ??

11

And, as if by Magic ..

after making the above post, I fire up MSFS2020 this evening, and TODAY, 3/29/2025 there is an update to the Asobo C172 Classic.

Panel.cfg updated 3/29/2025 – and now calls for the WT GNS Garmins !!

12

But now the new SDK 0.24.4.0 (SDK & Docs) cannot be downloaded.

(The requested content does not exist)

sdk-error
sdk-error1134×330 25.7 KB

1 Like
13

Same here.

14

OK, so I guess I am not that special and selected – Good to know .. Thanks for the confirmation.. so it’s probably NOT Me or my PC.

This does it a little difficult for Developers, when they release an update, update the SDK internally at Asobo, but that update is not available to developers.

15

Seems that today 3/21/25, Asobo /MS have corrected the 0.24.4 SDK downloads links (Core & Documentation)

but in the SDK documentation download, there is no actual documentation files ??