flanker35 Posted January 28, 2022 Report Share Posted January 28, 2022 Hello, if I engaged the autopilot the plane flies loops turned to the right or left and crashed. This behavior I had after the update to 1.2r3 before everything was fine. If I want run an earlier version I get the message "aircraft not activated" Maybe someone had a solution for me. Quote Link to comment Share on other sites More sharing options...
gsuri Posted January 28, 2022 Report Share Posted January 28, 2022 I am having similar issues. See my post Quote Link to comment Share on other sites More sharing options...
flanker35 Posted January 28, 2022 Author Report Share Posted January 28, 2022 Sorry for my post don't see the post from gsuri Thank you, gsuri, exactly the same problem, I'm on OSX 12.1 too. Quote Link to comment Share on other sites More sharing options...
gsuri Posted January 28, 2022 Report Share Posted January 28, 2022 I don’t understand why we can’t use older versions? Never seen this before. i have all versions of the tbm and they work Quote Link to comment Share on other sites More sharing options...
ois650 Posted January 28, 2022 Report Share Posted January 28, 2022 Hello, Can you upload a screenshot of your PFD and MFD when this behaviour occurs? Thanks Quote Link to comment Share on other sites More sharing options...
flanker35 Posted January 28, 2022 Author Report Share Posted January 28, 2022 Hello, the PFD and MFD show normal only the autopilot does not work. Quote Link to comment Share on other sites More sharing options...
gsuri Posted January 29, 2022 Report Share Posted January 29, 2022 Hi Here are some some screen shots from my cockpit. I have posted this issue in Technical Support too. Quote Link to comment Share on other sites More sharing options...
Pils Posted January 29, 2022 Report Share Posted January 29, 2022 Suggest you backup and then delete your …/Output/CL650 directory from X-Plane then start a fresh airframe. Quote Link to comment Share on other sites More sharing options...
Peter Clark Posted January 29, 2022 Report Share Posted January 29, 2022 In neither of those screenshots is the AP showing engaged in the FMA 1 Quote Link to comment Share on other sites More sharing options...
flanker35 Posted January 29, 2022 Author Report Share Posted January 29, 2022 Hi, I delete the airframe and start with fresh but no result, AP is engaged FLC, NAV, and ATS on, but AP still not working. Same result with complete fresh installation of the plane. Quote Link to comment Share on other sites More sharing options...
gsuri Posted January 29, 2022 Report Share Posted January 29, 2022 31 minutes ago, Peter Clark said: In neither of those screenshots is the AP showing engaged in the FMA Because it kept tripping Quote Link to comment Share on other sites More sharing options...
Pils Posted January 29, 2022 Report Share Posted January 29, 2022 3 hours ago, flanker35 said: Hi, I delete the airframe and start with fresh but no result, AP is engaged FLC, NAV, and ATS on, but AP still not working. Same result with complete fresh installation of the plane. Can you capture a video of the behaviour while showing the flight control synoptic page, please. Quote Link to comment Share on other sites More sharing options...
Goran_M Posted January 30, 2022 Report Share Posted January 30, 2022 Also, what kind of hardware do you have connected? Quote Link to comment Share on other sites More sharing options...
flanker35 Posted January 30, 2022 Author Report Share Posted January 30, 2022 A macbook pro M1 max, 16", 64 GB and Saitek x52 Pro. Before the update everything runs without any problem. Quote Link to comment Share on other sites More sharing options...
flanker35 Posted January 30, 2022 Author Report Share Posted January 30, 2022 Update If I fly the plane under High Sierra everything runs like it should. Quote Link to comment Share on other sites More sharing options...
Pils Posted January 30, 2022 Report Share Posted January 30, 2022 34 minutes ago, flanker35 said: Update If I fly the plane under High Sierra everything runs like it should. On another M1? Quote Link to comment Share on other sites More sharing options...
flanker35 Posted January 30, 2022 Author Report Share Posted January 30, 2022 No, on my MacPro early 2008, but with very low fps (15-17). Quote Link to comment Share on other sites More sharing options...
Pils Posted January 30, 2022 Report Share Posted January 30, 2022 1 hour ago, flanker35 said: No, on my MacPro early 2008, but with very low fps (15-17). Sorry, of course, High Sierra is a long time before M1 existed. I can’t keep track of all the California names! What exact version of macOS were you running when you first had the issue? Have you done any upgrades since? Quote Link to comment Share on other sites More sharing options...
Pils Posted January 31, 2022 Report Share Posted January 31, 2022 On 1/28/2022 at 11:05 AM, flanker35 said: 1.2r3 Definitely r3? Did you ever install r2? Quote Link to comment Share on other sites More sharing options...
Goran_M Posted January 31, 2022 Report Share Posted January 31, 2022 Here's what we found. @flanker35 @gsuri We have discovered that the latest update to Apple's OS Monterey 12.2, combined with further optimizations to the 650 code, under the M1 Processor, has done something to how the CPU works with the 650. It just so happened that Monterey 12.2 dropped around the same time our updates did. I wasn't seeing it on my developer build, because I have older code on that version. However, I did load a current beta version, and I was seeing some very strange things happening. Everything seemed to slow down and took its time aligning. As well as getting a sound loop on the various cockpit sounds. This all eventually righted itself after a few minutes, and Saso determined the problem was the Mac's translation through Rosetta that was doing all kinds of strange things. After some digging, Saso eventually fixed a few things, and sent me a new build. After loading, all issues were resolved. So, expect an update in the coming days that resolves this issue. Many apologies for this minor hiccup. 1 Quote Link to comment Share on other sites More sharing options...
gsuri Posted January 31, 2022 Report Share Posted January 31, 2022 41 minutes ago, Goran_M said: Here's what we found. @flanker35 @gsuri We have discovered that the latest update to Apple's OS Monterey 12.2, combined with further optimizations to the 650 code, under the M1 Processor, has done something to how the CPU works with the 650. It just so happened that Monterey 12.2 dropped around the same time our updates did. I wasn't seeing it on my developer build, because I have older code on that version. However, I did load a current beta version, and I was seeing some very strange things happening. Everything seemed to slow down and took its time aligning. As well as getting a sound loop on the various cockpit sounds. This all eventually righted itself after a few minutes, and Saso determined the problem was the Mac's translation through Rosetta that was doing all kinds of strange things. After some digging, Saso eventually fixed a few things, and sent me a new build. After loading, all issues were resolved. So, expect an update in the coming days that resolves this issue. Many apologies for this minor hiccup. Thanks! Outstanding support! You are the BEST developers in this community! Just for info, I am still on Monterey 12.0 regards Quote Link to comment Share on other sites More sharing options...
Goran_M Posted January 31, 2022 Report Share Posted January 31, 2022 3 hours ago, gsuri said: Thanks! Outstanding support! You are the BEST developers in this community! Thank you! 3 hours ago, gsuri said: Just for info, I am still on Monterey 12.0 It appears it's on all ARM CPU's. We're just glad it's fixed on our end, instead of potentially waiting for XP12 or for Apple to fix something. Quote Link to comment Share on other sites More sharing options...
gsuri Posted January 31, 2022 Report Share Posted January 31, 2022 3 minutes ago, Goran_M said: Thank you! It appears it's on all ARM CPU's. We're just glad it's fixed on our end, instead of potentially waiting for XP12 or for Apple to fix something. Great news! Quote Link to comment Share on other sites More sharing options...
flanker35 Posted January 31, 2022 Author Report Share Posted January 31, 2022 Thank you. Quote Link to comment Share on other sites More sharing options...
OAK738 Posted February 3, 2022 Report Share Posted February 3, 2022 On 1/30/2022 at 7:10 PM, Goran_M said: So, expect an update in the coming days that resolves this issue. Has this fix been released? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.