Cameron

If you are not running X-Plane once in a 14 day period, this will happen.

The G5 is certified for small piston aircraft, so you'd never find one in an MU-2. You could always opt for the G500's though.

Ben worked real hard to get Gizmo in its new version, and it's great that it's working on ARM. That said, we are not suggesting people switch to it yet because it is still a beta and does have some bugs that still need to be worked through. One of those is random activation disconnects, which will disrupt your flight when it happens. Ben is aware of this stuff, but if you happen to ever experience it, you can at least know about it now and not come asking for support. The old version of Gizmo (current retail) will still be available to you in the meantime should that issue arise on your flights.

Hi Stefan, We don't have plans for that as it stands right now.

Absolutely! Just be sure to run the installer for EACH version of X-Plane. Are you sure you have your throttle setup correctly? Please be sure to check the documentation on that: https://www.togasim.com/mu2docs/setup/hardware_setup.html

https://www.togasim.com/mu2docs/setup/realityxp.html

Yes, it has always been this way. I think @tkyler has expressed interest in this kind of thing before, but for now the focus is diverting back to IXEG. This release served two purposes. 1. To get a working XP 12 version in your hands. 2. To facilitate a co-sponsored contest with a major retailer.

Changes are for X-Plane 12 only. The installer will still retain an older X-Plane 11 version, but it is now considered frozen. Rosetta for now.

This will serve as an official announcement that we have released the TOGA Simulations MU-2 Marquise version 2.1.0 update. All customers who have purchased the MU-2 Marquise v2 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 MU-2 Marquise v2 from today forward, your purchased download will already be updated to version 2.1.0 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 MU-2 Marquise v2 download and re-download the file. It will download as the latest version! This version brings official X-Plane 12 support. See all the v2.1.0 changes by clicking here! 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.

Hi there, Since this seems to be something you're really hoping for (seen a couple posts from you about it now), I don't want to sugarcoat the answer. There are no near-term plans to do anything for MSFS. The team has a very full plate right now with X-Plane work, and it will stay that way for quite a long time should things go as planned.

Yep, you're right! I fat finger scrolled on my phone and missed some of the path. Thanks for all the feedback!

Thanks. Ben knows a bit more about the network side of things, but my question was asked because I note you have a scripts folder with an init.lua file in it. It makes me wonder if Gizmo is attempting to use this, though as I think about it more that would not make sense for a raw lua file. It sounds like you've found the initial issue though, so I won't wonder further about my own conspiracy.

Is this after a fresh install of something with Gizmo, or a one-off that happened when you opened this aircraft?

This already exists in the non persistent mode option. On the CL650 initial load screen, you can click the window to see the additional mode. It's been a while since I've used this mode, but as I recall it also has the pre flight items already done. Just so we're clear, there IS state saving. Not sure if you were aware of that, so mentioning it just in case you weren't just clarifying a difference.

This is a known issue with Zink in general on drawn displays and affects numerous products. Laminar is aware of it and states at this time the problem is related to a driver bug at AMD. They have consistently tried to get AMD to resolve this to no avail as of now. In other words: there's nothing we can do about that.

Once Laminar creates an API for this, yes. Until then, we wait.

I don't mean for this to be rude, but instead factual: The sales numbers disagree with your assessment. This is based on sales data and product comparisons over a 15 years in business period. At this point in our business adventure, we know what sells and what the mass majority of the market seeks. We hit that mark pretty well on the 650. Your computer sounds taxed. More of a settings vs hardware compromise on a sim that uses more rendering resources than it's previous iteration (11 vs 12). How did you save the situation? If it's through the X-Plane menu, that's not going to work. Use the state save from the 650 menus instead. X-Plane's built in situation save system is very basic and cannot capture all the custom datarefs in a product like this.

No. The code base work being done is significant enough that it will not work in X-Plane 11.

No. It's calling out a default X-Plane airfoil.

These are internal X-Plane paths. It's also a crash within X-Plane, not the MU-2. May be an issue with the version/beta you're running, and worthy of a report to Laminar.

The first image is an error for a plugin we don't make. DataRefTool. You can remove that and see how it goes. The last image shows you have some kind of weird permission issues with your X-Plane folder or that drive it's on.

Your log shows the M20 running fine. You made it sound like the product wasn't operating. For RealityXP, you can wait till someone with better knowledge than I answers your other topic.

You didn't give any other information so that someone can assist you. A log.txt file would be a good start.