diamonddriller

Well, I changed all (SR20, SR22, SR22T) Entegras and G1000 varieties to svs=0. I could load them up without crashes, but I couldn't change from one Cirrus to another without a crash. I could change back to a 172, but it then crashed if I went to another Cirrus. A bit odd. The G1000s still look OK. Sadly, the Entegra PFD is flashing still, in all varieties. I tried disabling plugins like Python, FlywithLua, ARO, etc., and that did not help at all. I had a look in XP 11.55. All Cirruses load properly, and I can swap without a crash. The Entegra PFDS are all rock steady. I took a look at the settings.cfg and svs=1 in the XP11 set-up. So, something in XP 12 does not like the Entegra PFD, and the loading of the planes is more flaky than in XP11. I guess you have all the info. you need to see what may be happening. As XP11 works OK, it can't be an AMD thing. If you can find out what's going on, it would be nice. In the meantime, I can use XP11 if I am desperate to fly the Entegras! I don't mind that, as I have 11 set up very nicely.

Actually, Cameron, I had already done that a while back (maybe I missed one?), and on the Islanders - which were fine. I remembered the mtu problem, after you reminded me. I loaded a Cirrus Entegra today, without a crash, and without a 172 first! The bad news is I got a crash with the SR20 G1000 after loading a 172, and my settings.txt was correct. Anyway, the Entegra PFD is still flashing, and (to make life easier), I downloaded minimal scenery, to see if a better frame rate would cure things. Admittedly, 27 fps isn't great, but it should be enough. X-Plane 11 is so much faster.... The TorqueSim planes are always very heavy on frame rates. So, here are some more files and another thrilling movie for you and Coop to look at I believe you are in FL, and, if so, will not have a bad time with the hurricane! 906739076_SR22_AVIDYNE_DFC90-2023-08-2912_39_19.avi Log.txt CrashLog.txt settings.cfg

Updated to XP 12.0.6b7. All the Cirruses (and I have the 20s and the 22s - G1000 and Entegras) crashed X-Plane, but I thought I'd try loading the Laminar C172 first, and that cured the problem. FYI, I've included the crash log, which may show why I need to load the Cessna first. However, the Entegra's PFD is flashing, and that was the same in b6 yesterday. 1709617353_SR22TN_AVIDYNE-2023-08-2900_04_49.avi crash Log .txt Log.txt

@Cyber Copter If you read the update notes, you will see that Coop removed the beta range.

@Cameron After what Coop said, I won't bother editing the XP11 files! Thanks for the reply. @Coop Thanks for the explanation. I would venture that the majority of Mac customers are still on Intel Macs, so your testing comment is a tiny bit worrying, but I suppose you know that things will still work. I'm going to stay put till the M3 chip is in play. My 2020 iMac runs both XP11 and 12 very well - and everything else that I use a computer for - so I'll hang on!

Cameron, as you are looking at the thread, I did ask why the Cirrus and Islanders were affected by the multi-threaded-uploader problem for me in XP12, but not in XP11 - and more so, because the original support article was written for XP11. I'm not a programmer(!), but was just curious about the phenomenon. I'm sure the answer is way above my "pay grade", but I wonder whether this is (a) fixable, and (b) whether it really makes much difference if it's not. I have to say that my frame-rate seems more than reasonable with the alteration to the settings.txt, but then I can't compare it to what it might have been .

@Pils Very interesting. Thanks for that. It seems to have worked! I also disabled XGS, even though I had the latest version, which should be OK. Maybe I'll put that back. What is very strange is that the multi-threaded-uploader has not caused any problems with the Islanders or Cirruses in X-Plane 11 on the same computer - and the value is "0" in those settings.cfg files. So, X-Plane 12 is mucking things up a bit...... By how much the performance has been degraded by disabling these functions, I have no idea. Maybe Cameron or Coop will comment.

Crashing on my Intel iMac immediately, and the BN-2B does as well. Log.txt

I agree on the overly sensitive castoring steering. I'm having to just caress the brake pedals on the TPR, else I'm all over the place. Even doing that, it's tricky. I have many hours in DA40s (RW), and, believe me, they are much easier to steer on the ground! Perhaps I will tweak the brake pedals sensivity, and that may well help. However, X-Plane has never been that good for taxiing....... Never mind. It's a great plane. Thanks.

Hi. Should we update in XP-11 as well, or is this v 2.1.0 specifically designed for XP-12? I haven't downloaded anything yet, so haven't examined the file structure! 30 minutes later: Sorry - installed for XP-12, and saw it had a version for it. So, I did it in 11 as well, and - yes - it identifies itself as an 11 version!

OK. So I may as well leave my XP11 version as is, and put 2.0.0 into 12. Thanks Cameron.

Is this OK in XP11 as well?

Thanks Cameron. I've just had another look, and everything is as it should be. I downloaded 1.2.0 with no problem. Obviously a glitch - maybe I tried it before you had reset the link. All the best!

Hi. I think it all worked on my Islanders, but I was not sure because none of the file modification dates for the G5 look any different from earlier ones. So, to make sure I re-ran the installer, and then ran the G5 installer itself. Again, no changes (although the G5 installer shows today's date). However, I guess it did work, because the copyright date on the G5 screens was 2023!

My link is not live. All other purchased links are in red, and get the "hand" when I hover over them. The G500 link is in small black print, and is not clickable.

I got the G500 installed into the PC12, as per Ither's work. However, although I can start the engine up, no electrical systems are visibly working, except the G500 and Garmin screens. I've flicked all the switches every way, to no avail. I posted this problem in Ither's thread, but he has not come back on it this time. If Coop or Cameron see this, do they (or anyone) have any ideas? Carenado's plane is activated. As a reminder, this is on an Intel iMac, under Monterey.

As a follow-up, Cameron, I posted in the .org forum, and Ither replied within a few minutes All good!

Thanks Cameron. I did (see my last sentence) say that Ither would know, but I expected Coop to have an idea, as he presumably has tried this out. As for SASL, I know you use Gizmo and not SASL, but Ither seems to have changed SASL, which probably prompted the reactivation message. I wondered whether Coop had tried to see what would happen if or when he tried to reactivate Carenado's product. Coop may see this, but I will also post this in the appropriate .org forum - but Ither has not contributed to that for a long time, so he may not even look at it..... It's not that important. I was only mucking about, as I'm quite happy with the G500 in the X-Aviation planes where it does work!

On an Intel iMac. For some reason the author of the mod says no Mac or Linux. Looking at the file structure, I was not sure why, so I duplicated the Pilatus, installed the mod and then used the G500 installer. I loaded the plane, and the G500 looks fine on the panel, but the PC12 asks for activation. Seeing that there is a change in SASL, I suppose I should not be surprised, and the plugin changelog.txt talks about activation. So: (1) Why does the author say no to Macs? (2) How would my registration string work on the plane, which is no longer Carenado's coding? I don't want to waste an activation. I should ask "Ither", but as you wrote the G500 program, I think you may well know the answers, as you have obviously looked at the mod.

Thanks @Pils. I just never thought to look in there - and, of course, a few other of X-Aviation's vendors' planes output to "output". I usually whip into that directory to either do something in the FMS folder, or X-Plane's preferences, and hardly glance at what else is lurking in there! Deleting the maintlog and airframes files did the trick. I have, once again, got a functioning turboprop

I've just had the request to install Gizmo again, which I had the other week, and I just reinstalled the plane. I saw an earlier thread with this. Then, I had an inoperative starter, despite reinstalling, getting a new airframe and using a GPU. I can't figure this out at all. I deleted the TBM log.txt, but there is another file somewhere that holds details of my reg. no., etc., so I need to get rid of that. It was all working perfectly a while back, but (like above), I updated to Monterey 12.6 - but that is unlikely to be a problem. I haven't had any new Mac requests for permissions with the plane. I know I've seen the other preferences file somewhere, but could you point me to it please?

Sadly, I think it unlikely. Other updates were hinted at, but nothing has materialised. The plane is a lot of fun, and as I have no intention of deleting XP-11 for a long time, I'll continue to enjoy it It's a VFR plane, so fabulous depiction of lousy weather is of no benefit whatsoever!

Hi Did you ever fix the HSI and the Nav 2 annunciations? Have I missed an update? My version is PB5, but did you ever patch that? I was flying the six-pack Ovation II yesterday, and noticed the errors again. I had forgotten about this, till I looked up the forum to see that I had already mentioned it :-)

I did suspect that the thousands might be larger. Thanks for the reply. Delighted with the set-up. It looks and works so nicely.

Flying the BN2P today, with my new G500 suite! Love it - also in anticipation of the new MU-2! Noted the carb heat discrepancies are still there, so Laminar didn't fix the problem........ Not to worry. It doesn't affect the flying!