Cameron

This is the correct answer!

Thank you for sharing your observations and feedback. We've indeed noticed that with the current state of X-Plane 12, particularly in the latest beta, there seem to be some challenges related to unloading aircraft plugins. It's important to note that this isn't specific to the Cirrus products alone. We're observing this across several of our development products at this time. We're hopeful that as X-Plane 12 continues to evolve and stabilize, many of these issues will be addressed. In the meantime, we appreciate your understanding and patience. It's good to hear that you have a stable setup with X-Plane 11 to fall back on. We'll certainly keep monitoring the situation and do our best to ensure optimal performance for all our products. Thank you for your continued support.

Hey @diamonddriller, Firstly, thank you so much for your kind thoughts regarding the hurricane. We are doing our best with the preparations and sincerely hope everyone in its path remains safe. Regarding your aircraft issue, I appreciate the detailed information and the files you sent over. It helps us get a clearer picture of what might be causing the problems. It sounds like the issue could be related to SVS being enabled, which has been a known factor in some cases. To address this, you can disable SVS without loading the simulator: Navigate to X-Plane 12/Aircraft/X-Aviation/SR22 Series/{Aircraft Type}/plugins/sr_systems/settings/. Open the file settings.cfg in a text editor. Find the line related to SVS. To disable SVS, change it to: svs = 0 To enable SVS, change it to: svs = 1 Save the file and try loading the aircraft again. This should help stabilize the experience, and hopefully, you won't encounter further crashes with the SR2X G1000s. I completely understand your concerns about the frame rates. As a fellow Mac user I'll just say that Mac hardware (especially Intel based), gets hit especially hard with things like that, whereas the Windows gaming rig experience is much different. That said, the M1/M2 chips are very impressive at handling products like these. Thank you again for your understanding and patience. Let me know if there's anything else I can assist you with.

Hi @diamonddriller, It seems you're encountering issues with the multi-threaded uploader. To troubleshoot the issue, please consider the following steps: https://support.torquesim.com/hc/en-us/articles/1500004699102-Multi-Threaded-Uploader-Causing-Crash If you continue to experience problems, please let us know any specific error messages or behaviors you observe, so we can assist further.

It looks like the issue you're encountering is being caused by DataRefTool. By simply removing that, the problem should go away. I understand it can be a bit frustrating, so I appreciate your patience in troubleshooting this. If you'd like an alternative, you can utilize DataRefEditor instead. It's a great tool and should meet your needs without any trouble.

Just to clarify, the position-saving feature is exlusively designed to work with the RealSimGear hardware. So, if you're not using that particular hardware, that's the reason you're experiencing this issue. We understand how this can be a bit confusing, and we appreciate your understanding.

We're currently focused on updates for the TBM and CL650, which are our top priorities at the moment. As for the A220, it's in the early stages and hasn't been our main focus lately. While we're excited about its potential, it might be a while before we can dive deeper into its development, and a release is not likely for around 18 months or so. We truly appreciate your interest and patience. Thank you for understanding.

Hi @MarioTG, I just wanted to mention that the functionality for saving the size and position of this plugin is specifically designed with the G5 screens/hardware from RealSimGear in mind. Could you kindly confirm if that's the setup you're using? If it's different, that might be the reason you're experiencing some challenges. But if you're indeed using RealSimGear hardware and still having issues, please let us know. We're here to help!

Hey, the enthusiasm is still definitely appreciated!

Indeed, while Coop has identified the root cause of the bug, it’s important to note that pinpointing the issue and implementing a fix are two distinct steps. Additionally, the complexity of the solution can vary, and implementing the change might require thorough testing to ensure it doesn’t introduce new issues. Furthermore, the upcoming update will encompass more than just this single fix, so it’s a collective effort that requires some time. Thank you for your patience and understanding.

Kindly take a moment to review the previous posts in the thread before asking questions. The answer to your query was addressed in my most recent post. It’s essential to read through existing content to keep the discussion streamlined and productive. Thanks for understanding,

While we don’t have a specific timeframe to share at the moment, I can assure you that support for ARM is actively in the works. We appreciate your patience and look forward to bringing you this update in the near future.

I absolutely understand the anticipation you must be feeling as you wait for this release! It's a thrilling time for all of us, and I can assure you that our team is diligently working away to bring it to you. We're following the latest update from Tom just last week, so everything is still on track. Please keep an eye on our announcements, and we'll make sure to keep you informed as soon as there's news to share. Your patience and excitement mean a lot to us, and we're eager to deliver something fantastic for you!

This topic is closed due to the original poster using a pirated copy of the product.

Happy to hear!

It seems like a puzzling issue you're facing. From what you've described, the airframe doesn't appear to have any failures or broken parts. Here's what I recommend: Double Check the Prop Slings: Ensure that you've removed the prop slings before attempting an engine start. This could be a simple oversight that's causing the problem. Record a Short Video: If the issue persists, please record a short video of it happening using a tool like OBS or ShadowPlay. Sometimes, seeing the problem in action can give us clues that aren't apparent from a description alone. Please let us know how it goes, or if you need any further assistance. We're committed to helping you get back in the virtual skies!

Firstly, don't worry about the machine name; it's simply a reference for you to easily identify your device in the future. There's no right or wrong answer; it's just for your convenience. As for the TBM900 issue you're facing, it might not be activation-related. Instead, it seems like it could be tied to the aircraft's persistence settings. Could you try initiating a new airframe in the TBM airframe manager? If that doesn't sort it out, please share your X-Plane log.txt file with us. This will help us take a closer look and assist you better.

Examining the information you provided, things are not adding up. What you’re describing does not correspond to version 1.33, and it appears to be a many-year-old pirated copy of the product judging by stuff you've posted here. If you’d like to discuss this matter further, please provide your order number. This will allow us to verify your purchase and assist you properly.

I can certainly appreciate your anticipation and eagerness for the update. Currently, we're working diligently on adapting to the intricacies introduced by X-Plane 12, especially due to its major changes affecting our unique turbine engine model. While I'd love to give you a specific timeline, we're diving deep into a comprehensive re-write on multiple levels to ensure the best possible experience for our users. Therefore, it's difficult to pinpoint a release date. All I can assure you is that we're committed to getting it right, rather than rushing it. Quality takes time. We appreciate your patience and understanding. It'll definitely be worth the wait.

I completely understand your frustration with the lack of weather radar functionality in the Challenger 650, especially considering the significance of weather navigation in real-world flying. However, I must clarify a misconception regarding the situation. The absence of weather radar is not due to any negligence or unwillingness on our part. Rather, it is a technical limitation tied to the way X-Plane interprets and represents weather within the simulator. While Laminar Research has indeed made commendable improvements to weather depiction in X-Plane 12, they have not yet provided a way for plugins or aircraft to accurately identify the specific cloud patterns, storm cells, or their exact locations within the simulated environment. This is more than a minor obstacle; it renders what you're asking for technically unfeasible at this time. Even if we were to access real weather data, it would not correlate with Laminar's approximated in-sim depiction, leading to potentially inaccurate and misleading information. Please know that we share your eagerness for this feature, and our hands are literally tied until Laminar extends the necessary support in their API. We remain committed to enhancing our products and are hopeful for future developments that may allow us to provide the weather radar functionality you desire. I hope this sheds light on the complexity of the situation, and we sincerely appreciate your understanding.

Got Zink enabled? Seeing flicker issues a lot related to this lately.

Your credit card transaction was declined by your bank and the order did not go through. Thus, you have no downloads. This was also communicated to you in your support ticket.

It would definitely not be something you could do in Plane Maker. Only way to know if it's Zink is to disable it and see if the problem goes away then.

Except we didn't use that phrase in the release, and stated Fall. We're still well within the window.

This will serve as an official announcement that we have released the version 1.0.2 update for the DA40NG. All customers who have purchased the DA40NG up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the DA40NG from today forward, your purchased download will already be updated to version 1.0.2 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original DA40NG download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: REMINDER!: ARM64 support prepped for future. (Note: For ARM64 Mac (M1+ processors) users, ensure you are running Rosetta for now. Bug Fixes and Improvements: RSG-1700 Custom throttle control unit with power lever calibration curve for ECU commanded power RSG-1682 Increase brake rolling friction RSG-1689 Flap indication light should show during transition RSG-1688 EIS alert radio-coloring mode on engine indications RSG-1686 Adjust ECU test annunciator behavior RSG-1683 Add experimental support for VR Popups RSG-1673 Alternate static selection RSG-1760 Add electric master switch direct position commands RSG-1761 Add full off and full on commands for slider-type manipulators RSG-1767 ECU test should require proper gearbox temperature RSG-1687 Light directionality tuned As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.