diamonddriller

No reply from the developer after a week...... I'll try Discord again

@EGT Interesting.... I haven't tried the 525 (with the 530s) on an ILS, and I wonder whether the GPSs will identify the localisers, as they certainly don't recognise the VORs. Are you (EGT) running in Windows, and do your 530s identify the VORs? As I'm on a silicon Mac, I wonder whether this is a Mac only problem. Coop has not come in on this yet.

Mac OS 26 Tahoe on a Mac Studio - X-Plane in Mac silicon mode. Both 530s won't recognise any VORs. They don't identify any. The radials - if they show anything at all - are wrong - usually displays 180, and the distances are wrong too. That bit of the display may not even show a radial or distance. The DME sometimes agrees with the GPS derived distance, but I may have to click its button once or twice. Often the ground speed and time is 0, but it may show some value which is way off. I can be doing 140kts, and it will say 25 or whatever..... My X-Plane is running in 12.3.0 b2. Could that be it? Log copy.txt

Support for Rosetta 2 is apparently ceasing (with some exceptions) in MacOS in 2027. I am now surprised that a large number (including many newer and terrific products) from the store have still not been converted to work natively in Mac silicon. As Macs have been using ARM based chips since late 2020 (5 years!), every piece of software that is now produced is for ARM based Macs, although some will still be universal, and will work on Intel Macs. Office stuff, photo-editing, music production, etc. - all work in Mac silicon, including vast numbers of little utilities. As far as X-Plane is concerned, virtually every developer of aircraft has its fleet working natively on silicon Macs. I love my X-Aviation aircraft, but I really don't want to rely on Rosetta (and keep having to change the X-Plane program to work in Rosetta) when I want to fly all those Gizmo reliant aircraft. I'm not too sure how much has to be altered - I guess all the mac.xpl programs have to be changed, but I have no idea how much Gizmo was integrated into the systems. Maybe the sales don't justify the effort.....

Well, the old exxpression: "No news is good news" does not apply - and I have my tongue in my cheek It'll be when it'll be. Of course, I appreciate the fact that developers are often a one or two-man band, and probably have a "regular" job as well. It's a lot of work, and (in this case) no real return, unless you charge an upgrade fee. Actually, I think that's more than acceptable. It's one thing to get bug fixes and the odd extra feature for free, but a rewrite of a lot of code for a percentage of the customer base is another matter, and a few dollars for that would be fine.

Any news on other planes in the "fleet" that are shortly going to be ARM compatible?

Thanks Coop!

Hmmm. I'll try again later, but the preselect was not working for me. I know how to use this, but maybe I got something wrong yesterday... We'll see. No, IAS was not being used. It sort of followed the commanded VS, but it was not that accurate, and when well off the selected altitude, it was nowhere near right. Flies very nicely, but taxiing can be difficult. ------------------- I just tried it again. Started with engine running (saves time!), and it worked properly! Yes, it wanders about a bit from the assigned altitude, but that is expected and realistic, as the air is not static! It does correct itself. So, as to quite what was going on yesterday, I have no explanation. If it happens again, I'll send you a log file. Thanks for your interest :-)

I have just upgraded to a Mac Studio, and run XP12 natively on the M processor (i.e. not Rosetta). I can't remember whether the stec-55x is supposed to have altitude preselect working on the Entegras - because my last Intel iMac couldn't run these planes without flashing screens, so I hardly used them, and stuck with the G1000s. Anyway, today, I found that altitude preselect (what I fed in on the Entegra PFD) was totally ignored by the autopilot. In fact, even the VS speeds were not kept to very accurately. Is this possibly a problem with the M processor? I had, earlier, tried the same plane in X-Plane 11 running in Rosetta, and the autopilot verged on being almost unusable for altitude control, and I gave up. I, so far, have had very limited experience in X-Plane using Mac Silicon, so I don't know what works, and what doesn't! I get super fps, which is a big plus.

Yes, I know. I have already done that. The funny thing is, I was sure I had mentioned this before, but I couldn't find any post from me about it, so I obviously hadn't. Thanks Cameron.

X-Plane 12.2.0b5. Now running on a Mac Studio in Sequoia. The 172 G5 installation seems to disable the Garmin GNS 530 and 430 popouts. No "hand" appears, and neither will popout, no matter where I click. As an obvious first try at fixing this, I deleted the 172 G5, and the G5 installer, and reinstalled the whole 2.2.0 setup, thereby installing a new 172 G5. No difference..... I had a look at the Islanders, and the GNS 530 popout works as normal, and the "hand" is there if I move the cursor into the screen. So, that's a bit odd....

@Pils M4 Max Studio. 40 core GPU version. That should be fine for a few years!

Thanks Cameron for your prompt reply. Those are enough to get me going Your systems requirements on the product page merely states the minimum version of the Mac OS, and I didn't see anything in the manuals, so your list is very welcome!

About to change from an Intel Mac to M4. Would you be kind enough to list the planes you sell that are ready for Mac silicon (universal binaries, or however you set the installer)? Thanks.

That's great Cameron. I trust you try these things with more than default scenery, though Amazingly, after I posted above, Apple just announced the M4 MAX Studio (and the M3 Ultra one - too expensive for what I need!). What a coincidence.