Leaderboard

I'm so sorry....total brain lapse on my part...I was responding "while on the move" and wasn't really thinking this through. Some manipulators are "command" type...and they are "on the command list" however, some are "push button" type, and those are NOT on the list. ...and indeed, this button is not a command type and there is NO command for it unfortunately. I'll add in these for the next update. It probably should have been a command type from the beginning. Again, sorry for confusion. -TK

This will serve as an official announcement that we have released the TOGA Simulations MU-2 Marquise version 2.0.4 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.0.4 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! See all the v2.0.4 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.

The current stable SDK is v3.0.3, which fits with 11.5x. There is also a beta version of the v4.0 SDK available (cf. https://developer.x-plane.com/sdk/plugin-sdk-downloads/), which is the one fitting for 12.0. The API documentation is however not yet updated to incorporate all the XPLM400 changes. So in short, if a plugin builds without issues against the XPLM400 API, there's a good chance it will simply work without problems. If it fails to build and the reasons aren't obvious, it'll depend on the developer's patience digging into the header files and resorting to try & error troubleshooting. In both cases though chances are that SDK changes down the road entail further changes to the plugin code.

all logged Bulva. -TK

Should you wish to actually fly the 650 in XP12, you can request beta build access through the Discord. If you're not already a member the link is below in my signature.

This implies you are running in XP12, which is using a different flight model the MU-2 is not tuned for. You run at your own risk in 12 for the time being!

You are correct that the command is NOT in the list of custom commands on the docs. sorry I missed that, I will get that fixed promptly. The command is: xscenery/mu2b60/manips/ap_button and that command will also turn on the Yaw damper at the same time. Here's a few others on that AP panel also: xscenery/mu2b60/manips/ap_yaw_button xscenery/mu2b60/manips/ap_soft_ride_button Seems I have several "manipulator interface commands" not present. I generate that list automatically via a script as there are so many commands in my code and my parsing script missed a bunch of these "manipulator" commands. Perhaps its time for a dedicated manual perusal of that list. Thx again for pointing this out. -TK

A total mismapping of the cockpit texture on my part....indeed a simple fix, but will need a new 'export' on my end. I'll get a fix out right quick. Sorry about that.....lot of options this guy. -TK

Laminar based their new windscreen effects on the pioneering work Saso has done with librain. In one of the interviews Austin (or Ben?) gave a few details, and it sounded to me like they used his open-source implementation, adapted it to Vulkan, and embedded it within their rendering chain. One of the improvements pointed out in that interview was that now it was embedded, it could make use of all physics data, including prop wash etc. to natively couple effects with XP's physics calculations.

...and for updating the 'last working XP11 version to similar behavior in XP12?....neither will we....we've said it many times and this is not in debate. It is a bit more of a process because XP12 has changed quite a bit with regards to engine and systems, which means we have to audit everything and surgicaly remove code that clashes with XP12 functionality...and we put in a LOT of customization. As far as a discussion of charging a fee relative to "when its finished"., too subjective......I have enough statistical evidence that says to me that a lot of folks have really enjoyed the 737 for a lot longer than the price of a 2 hour anniversary dinner...(for newlyweds anyhow). To those who would argue about 'unsimulated things', all I'm going to say is Pffff. I've been a software 'consumer' for over 40 years, and not casually, I make my living from using software, 100s of titles over the years....and this stuff is always evolving, always changing...LOTS of software is missing things. I use what I can, enjoy the good parts, don't buy what I don't like and everybody has the same choice here...we're not hiding anything. I could easily argue that a lot of products lack "immersion", realistic lighting....or decent sounds. The flight sim dev community isn't like it was. Its more saturated, the bar is higher and the detail we have to put in is a heck of a lot more than PMDG had to in its early days when it had a monopoly on the airliner market. So what would we charge for? ...I can't say, but its true we have no incentive to keep on working for free in perpetuity. Have you noticed how everything is moving to the subscription model? There's a reason for that...and guess what, I have at least 8 software subscriptions...every month/quarter....how would you guys like that? (hint, you wouldn't). If we charge for any update, its fair to say that it would have to justify the deliverable for a majority of customers (cause it'll never be all). Probably....thinking off the top of my head...., includes more variants, the FMS more complete, animated everything, more robust failure interactions, etc...stuff like that. AND it wouldn't be a full price upgrade either, I never like that idea. So...feel free to discuss as much as you like, but I just wanted to throw out some of my thoughts for folks who haven't gotten to know me over the years through other posts. TK

X-Plane 12 is in early access. It's a public beta. There will be many changes, some minor, some major. Laminar have had a private developers chat channel for months already. We've helped them work through a lot of bugs already. Opening the product to the public will find many more. When X-Plane 12 settles down and exits "early access" you're likely to see more products officially updated.