diamonddriller

My suspicion would be that, as this is a very old product - originally written for X-Plane 9, I think - the installer is still 32-bit, which Big Sur won't run, even on an Intel Mac. Rosetta 2 just won't deal with it on the M1. As the sales of this are probably very small, maybe Cameron forgot (or didn't bother) to redo the installer in 64 bit. Of course, that's just a guess, and there may be another reason altogether!

Yup! That worked. All good. That was quick

Just to confirm, Coop: It doesn't display them on my Mac either. The plugin and g5.cfg files are identical to the last version, where it all worked perfectly.

Managed to do it myself

Hi THis works OK, but I'd like to do the 1.20 upgrade, so I can pop out the panels on the menu. Any chance of a new g5.cfg for me please? BTW, I notice that my Sundowner G5 was not working properly, but saw that you had already offered a new g5.cfg file for that, and it worked perfectly.

That did it! Well done. Your earlier instruction to put it into the G5 folder was the hang-up. Funnily enough, I thought I'd tried putting the .cfg file into the root directory, and on reflection I had - but it was the earlier version, not your new and improved one Nice of you to take the time to indulge this old f--t! Take care.

Hi Coop. No, it didn't work. I know you have better things to do with your time, so I'm not stresed with this at all. It's keeping me amused for a few minutes, while we are still locked down! I still get the dark screens, and can only start up the G5s from a popup. You can see what the file structure looks like. I just duplicated the G5 plane and called it G5 1.2, and experimented in that. Or could that be the problem? I deleted the settings directory, which had the old cfg file. What is interesting to me is that, somehow, a new (slightly smaller) g5.cfg file gets created in the plane's root directory, and I'm attaching it here. g5.cfg

Looking forward to these. I occasionally, RW, flew an Avidyne PA28 (they had them for a while), and they are a lot easier to use than a G1000. Watching some YouTubers with Avidyne GPS nav/coms, their logic is so impressive. I'm a little surprised that they didn't make a heavier dent in Garmin's almost overwhelming adoption in the larger manufacturers' planes. We Mac users can't avail ourselves of the Reality XP Garmins. I wish Aerobask would separately license their version of the GTN 750, which is pretty good...... So, it's LR's Garmins for us - which is not the end of the world, as the earlier Cirruses were so equipped anyway. True to life :-) BTW, Coop, you may not have seen that I added a note to the G5 "update" for the Mooneys forum thread. It was not fully successful.

Never assume anything is a piece of cake I substituted the plugin for the newer version, and resited the .cfg file to the base directory. Loaded up - and "Yippee" - had the menu in the X-Plane plugins menu - and it worked! The G5 screens all sat where they should. Looked promising! However, the G5 screens were blank (as if they were off - the "glass" looked normal). Undeterred, I had a look at the popups and they were off, too. So, I turned them on, and they both fired up. Whether the HSI was properly slaved to the GPS, I can't remember but, unfortunately, the panel G5s remained blank, no matter how I tried to fiddle with the switches on them. I moved the .cfg file around, renamed it to g5.cfg, and back again to no avail. I think I tried all combinations, but gave up after a while. Re-installing the PB5 got rid of the menu, of course, but somehow made the G5s power up inside the GNS530 screen! Very odd. There they were with the AI and HSI side by side...... It was getting very late, so I gave up. Today, rather than re-installing (which lets Cameron's uninstaller work), I just totally deleted both the "M20 Collection" and the "G5 Aircraft Installer" directories, and replaced them from Apple's great Time Machine, so things were back to where they were before I started playing. It all works again. So, obviously, there is an alteration to be made, somewhere in a file, to let the panel G5s fire up in the M20. If it's a simple edit, I'm happy to try. For me, it gives me something else to do on a Saturday

Thanks Coop. I must admit, I'd thought about doing that, but held off until you or Cameron suggested it (just in case it might mess things up). Thank you both for the service. Of course, I would have always had the recourse of just installing again from the PB5 installer. Have a great weekend - well, as much as you can in these crazy times.......

As I said, I thought about that, but didn't see why, because the G5 set up was already in place. Anyway, I ran the installer - which immediately told me that it was installed! Looking at the Mooney again in XP, nothing had changed. I have already said that I have assigned a key combination to give the HSI popup - that took two seconds. Reading about the .cfg file reminded me that I have never had to fiddle with that - either before I upgraded to PB5, and certainly not in the Sundowner G5 nor both the Islander G5 versions. Inspecting further, I saw that there is no g5.cfg file installed from the PB5 installer into the Mooney M20 G5 directory, nor anywhere else in the Mooney tree. Reading the page you referred me to, indicates that G5 is now at 1.20. That would presumably be the version that installs the plugin to X-Plane's menu. The installer I had bought from you is v1.0, and appears not to have changed when I checked the download link in my account. When running X-Plane, I can list the loaded plugins, of course, and the AFM G5 appears in the list with the Islander and Sundowner, but not with the M20. So, obviously, the Mooney does not have the X-Plane menu yet, and I see that many of the plugin files' creation dates are earlier than in the latest planes. As a reminder, I use an iMac, and Catalina. It's no big deal, because my key combo gives me my HSI popup, if I need it, but I'm just surprised that the Mooney pack hasn't had an upgrade. Also, it seems silly to click on the HSI G5 and get the AI popup, when I can't imagine that getting the appropriate instrument up in 2D is difficult to accomplish........ Loooking at the weather in Texas, aren't you glad you are in FL?

I have the latest release (PB5) of the M20, but haven't flown the G5 in quite a while. I have also got the Islander with the G5, and that has G5 options in the X-Plane plugins menu. However, although the G5 gauges are in the Mooney, and they work just fine, there are no entries in the X-Plane menu, and I don't see the G5 plugin loaded either - which is strange. In order to see a popup of the HSI, I have had to asign a keystroke. Maybe I'm dreaming, but I'm sure I had a menu option in PB4. As an experiment, I just re-installed PB5, but it looks the same. Am I supposed to run my G5 installer again? The G5 files seem to be in the M20 already.

I just saw this, Cameron, and you know the subject of trim has been kind of done to death elsewhere. It is a bit frustrating to have this problem, when the "pilot" has verified that the C of G is well within the envelope, but that does not necessarily mean the the plane can be flown with neutral trim. However, there is another aspect to this. It's the entertainment value of the plane in the sim. At the end of the day, the number of customers who either have flown or aspire to fly a turbine Islander, in the real world, will be vanishingly small! So, if Coop tweaks things to make it a bit easier to fly, even though it may be marginally less true to life (and I have to assume that Coop has had input from RW Turbine Islander pilots, when he was adjusting these parameters), does it matter much? I would venture that it doesn't. 99.9999% of the customers who buy this plane will be happy if it trims a bit more neutrally. OK, let it need more down trim when lightly loaded, but it's obviously upsetting quite a few customers. I remember, many years ago, flying in a Seneca, where we had to put a sandbag in the back to make it usable! So, sticking some extra weight here and there is a viable solution Coop's latest tweak certainly improved things a lot, but this "problem" is obviously still catching the punters out! Enjoy your day.

https://forums.x-plane.org/index.php?/files/file/44825-avitab-vr-compatible-tablet-with-pdf-viewer-moving-maps-and-more/ If you haven't already, you will need to register with the ".org" in order to download. After unzipping, put "Avitab" into your X-Plane's /resources/plugins for Macs (or \resources\plugins for Windows). It does not go into the TBM folder tree.

Couldn't be easier. When you open the downloaded zip file, you will create a folder, in which you have an osx-installer (for Mac users) and a windows-x64 installer. Click on the appropriate one, and follow the prompts. Have your X-Aviation login details to hand. Also, make sure you show the installer where your X-Plane 11 folder is. That's the folder (the root X-Plane folder) that you have to select. Also, you will be given a choice of using a beta of Gizmo, or the stable version. Your choice, but I am still using the stable version! The installer will do everything for you, and the plane will appear in your plane selection in X-Plane - it is installed under \Aircraft\X-Aviation in the X-Plane folder tree. When you first start it, you will be asked to fill in your X-Aviation login details again in a pop-up. That takes care of the licensing. Then you will be good to go. Have fun!

@Coop OK. I still seem to need a lot of down trim, no matter how I load the plane, however I obviously accept your explanation. The trim quadrant markings are heavily biased to the up position, which would seem to indicate that the manufacturer expected one to need quite a bit of nose-up trim at some time. Or, was it the fact that they would have used the same part from the avgas version, and it bears little relation to the expected behaviour of the turbine version? I find the differences in loading the two varieties quite interesting. The swapping of the avgas engines for the turbines seems to have made a significant alteration to the W&B situation. Anyway, they are fun to fly, and I'm enjoying using them - and that's what it's all about

@Jim Lynch Happy to see I'm not a lone wolf on this It's definitely not right.

Update installed on an iMac with no problems at all. Trim is sort of better, but still needs a lot of down trim to fly level, no matter how I load the plane. The trim is no longer on the "down" stop, but the way it is, I can hardly think I'd ever have to move it to the "up" area at all....... maybe for very slow flight, but I haven't tried that yet today. I'd love to know where Coop thinks is a reasonable trim position for level flight, and, say, just the two crew on board. So, some improvement, but I'm still not convinced it is how it should be - although I've never flown an Islander RW

Interesting that Cameron says they've bumped 11.1.13 up to be still supported in Mac OS X 10.13 (not supported in 10.12 anymore), but Apple are reputed to have stopped support for High Sierra. The last security update for it was in November, and several companies have stopped supporting their software in it now. In theory, according to the update list, it should work for you, though. As X-TCAS is not mentioned in the TBM docs., I still think it may be worth a try at getting rid of it, as I wouldn't have thought that it would affect flying the plane in any way. Skiselkov wrote the plugin, and he says it's updated to work OK in OS X 10.13, so .....?? If 11.1.12 works, then quite why the latest version crashes is something that Goran may have an idea about.

You appear to be running High Sierra, which is no longer supported. I suggest you update to at least Catalina, for now. However, you seem to be using an NVidia GTX Titan in perhaps an older Mac Pro (with an Intel Xeon). Those graphics cards had to have their firmware flashed to run Mojave and above. You may see other posts where the graphics card has proved to be an issue with the TBM. Macs run with AMD, not NVidia....... Whether that is the root of your problem, it is hard to say, but it is fair to comment that you are trying to run one of the most complex planes sold for X-Plane on pretty old and unsupported hardware, and on an unsupported OS. As a thought, see what happens if you just delete the X-TCAS plugin. It may not work, but it just might...........

Hi Cameron. Here's an odd Mac thing. On Catalina 10.15.7. The installer stayed in the dock after it was quitted, and it would neither restart from the icon, nor could I "force quit" it! That's never happened before - that I can remember, anyway. Actually, it may be connected to the fact that the installer did not seem to connect to your server when it asked for my login details (which were inserted correctly), but it just hung with "next" grayed out. I cancelled that installation and then started again. That second try connected instantly, but it did sit there for a while before doing the Gizmo installation. The whole installation went fine, so no problem. Unusual, but there you go. That installer closed normally, and it's dock icon went away, stilll leaving the first one there. I could not get rid of that icon, and I couldn't even see the process in Activity Monitor. The Mac would not restart, because it claimed I had to quit the installer, but it did shut down normally (after a bit of a wait), and everything was gone, of course, when I rebooted. The joys of software :-)

@Stevev M Good idea. Works a treat

Yes, Jim. I'm sure they will fix this, as it is too tiring to hand fly, and all the juggling with power and the condition levers cannot be realistic. It's around usable with the autopilot, but I'm hanging on for the update, to be honest. Unusual for TorqueSim not to have noticed this anomaly.

I put some more forward weight in, but it didn't make a lot of difference with the trim setting. It's quite easy to throw the CG out of the envelope with some loads, and I find the W & B pdf very interesting. I'm curious as to where the datum is. I flew RW in a Trislander, and remember the prop (tail support) they put under the tail on the tarmac, so it wouldn't drop the tail till they had some weight up front. If you just had the pilot on board (surely not unusual), would you really expect to dial the trim all the way down to maintain level flight? That can't be right. Or is it??? Surely, one designs the trim so that you have a lot of leeway at each end of the usual expected area or range of travel.

I'll also run another test tomorrow, but my flaps were up too, and I made the point that I had even dialled back the power - maybe not enough, though???