diamonddriller

This was corrected by the developer, as we discovered that there was a faulty g5.cfg file in the distribution!

On a Mac Studio. Installed the G5 into the new plane, and it worked, except the 530 gave a course to the waypoint, but the G5 bearing pointer did not. I could adjust it, of course, but it was not automatic. Checked in PlaneMaker and the GPS sync option is correctly on. Anyway, I remembered that you have updated to 2.30, so I installed that, hoping that would cure the anomaly. However the gauges are there, the G5.cfg and the plugin are correctly installed in the plane, but the screens are blank. I can push the power buttons, and they light up, but the screens remain blank. Very odd.. I checked one of my Islanders, and that had updated to v2.30 (as expected), and works perfectly. So, what do I have to ask Jetstream to look at? Log copy 4.txt

You may (probably did ) miss this posting in Discord, a few days ago: Hi. I know 1.1 does not cure the problem with the 530s. You said we need to wait till 1.1.1 So, I just moved libradio out, and the GNSs work with VORs and ILSs perfectly! However, what am I missing, as the NAV, autopilot, etc. work OK? I know the radios won't sound so realistic, but what else won't work? Or, won't work as well??? I'm on a Mac, so the GTN750s don't matter. Will the FMS work properly without libradio? Worth an "ask" in this forum. I don't want to get involved with spending time preparing for flights that wouldn't work without libradio. Obviously, if Saso or Laminar do come up with a fix soon, it would be reassuring.

Before I start mucking around with symlinks and scenery_packs.ini, has anybody tried these products in XP12, and (if so) were there any problems?

Thank you both. Always good to know it's not only me with these minor annoyances

Thanks Coop. I look forward to the fixes Love the plane!

Thanks Cameron. Is this a 12.4.0 b4 thing? I have not seen it before, although I hadn't used a G5 plane for a couple of months, or so. I presume it doesn't change XP12's structure, as nothing was picked up on my last XP update process.

On a Mac Studio (M4 MAX), and X-Plane 12.4.0 b4 I got this message (after installing the G5 plugin to the A36). The message (as in the screenshot) now appears in my G5 Islander, and I guess it will in other G5 planes. I'm also adding a log.txt, which shows a few G5 "alterations". Probably due to the X-Plane beta.....? Log copy 2.txt

@Pils That is brilliant. I think other problems above may be related to 12.4.0, but quite what they could be, I have no idea! I would not have thought Xchecklist, mentioned above, would be a cause, but I haven't tested it, and will leave it for a few days while others see what they have found. A perfect example is the librain problem with the 525. FlyJSim had already done something about that with the Q4XP

In my case, using a Mac Studio and running XP12 in MacOS Tahoe 26.2 under Rosetta, the plane has a big red X in one of the glass panels, stating that the plane is not activated. Studying both the older Gizmo activation and newer X-Aviation panels show that the plane is licensed. Running 12.4.0-b2 as above. As this plane is one of the newer products in the X-Aviation fleet, is it possible to get it to work natively in ARM64? I do see that earlier products, which had a lot of their systems running with Gizmo64, may well be much more of a problem for a small team, and I guess (to be honest) that the work involved would not bring in enough money to cover the cost in time to do this work. Some of the planes are still not compatible with XP12. I would, however, not expect Cameron to give away such upgrades, because they are not bug fixes, nor minor additions to functionality. A sensible charge is reasonable. In fact, other developers are charging, often like a completely new product, but giving a (say) 20% discount for customers who own an earlier version. The CL650 worked with XP11 from the start, and was working in 12 in 2022, so the conversion to ARM64 really should not warrant buying the product again. However, we Mac users (a minority of the user base) are probably a bit surprised that the genius who is Toto, did not make the plane ARM compatible from the word go. After all, Macs were being produced with ARM chips in late 2020, and the transition from Intel was almost complete by 2022! Oh well, I can use the 525 in the meantime

Me too. I was just getting my log.txt, but suddenly thought to look here

Apparently the SR20 Entegra will not work on a silicon Mac (but it will under Rosetta, I am sure), although the SR22 Entegra will work natively on the newer Macs. I presume that "they" have not yet done what is necessary to get rid of Gizmo64 for authentication - and, maybe, Gizmo is used in other functions of this particular version of the plane. If you run the SR20 with X-Plane 12 in Rosetta, it will use the provided Gizmo, and will work perfectly. Ben Russell wrote a version of Gizmo to work on "M" Macs - Gizmo64 LTS. You can buy it for a small sum, and others (and me) have found that it works on just a few of the older planes in the X-Aviation fleet that would work in X-Plane 12 in Rosetta, but seem to be OK without Rosetta, using this version of Gizmo. The SR20 Entegra does work, using this version of Gizmo. However, to be fair, this is not really approved by X-Aviation, and they are working to eliminate Gizmo throughout their "fleet", and implement their newer activation system. Some planes (the IXEG 737 is one) were apparently using Gizmo for a lot of their functioning, and just won't work properly with this LTS version. The only downside of having to start XP12 in Rosetta is a small frame hit. If you are on a new Mac, it will hardly be noticeable, but may be a nuisance on (say) an M1 machine. I don't know.

@UncontrolledAirSpace Hi there. I have no problems with any other plane with a 530, a 430, or even a combination of the two. As I said above, even the 2 530s work together fine in the AFL Kingair. It's just the 2 530s in the 525. I've been using XP for years, and been an X-Av customer also for years :-)

@Pivot Luck? Hmm.... On Discord, my only reply was from someone who has the same problem. I'm sad, because I have bought every product that TS has produced, and have had such good support from them in the past. As I have tried this on Intel and silicon Macs, and users of Windows have reported this too, it's not like I am a unique case. Although @Pils suggested it may be a Laminar problem, the Airfoillabs Kingair has the two GNS530s, side by side, and they are working perfectly. In the meantime, I can fly this without the 530s, and get by...... I would bet that a far larger number of customers are on Windows, and can use the 750s that are not available for Macs. So, most (probably) customers don't see this happening, as they have no need to use the 530s.

@Pivot Hi. You will see, from an ealier post, that I did use Discord - but to no avail. As I have since investigated further, I'm going to post again there, and add the screenshots I later made.