daemotron

Aircraft for XP12 slowly start to appear here and there. Some developers who stay close to vanilla X-Plane features (i.e. aircraft purely built with PlaneMaker and not or hardly using plugins, e.g. VSKYLABS) are mostly done converting their fleet. Light turboprops are a bit thin at the moment - only Thranda's Caravan so far, no PC-12, no King Air - but HotStart is working on their TBM, and TOGA will port the Mu-2 v2 in the months to come. Not sure about any King Air, AFL might upgrade theirs, but no official communication as of yet. Aerobask is (mostly) done converting their fleet (all Diamonds, but also their experimental jets and the Phenom). Indeed it's a bit odd we see airliners of all sizes being ported, even the HS Challenger (maybe one of the most complex aircraft models ever built for XP, potentially any sim) has been ported, while there's hardly any GA (piston or light turboprop) available yet (Aerobask being the exception). Quite a few are in the pipeline - TS is working on their Cirrus aircraft and the Islander, and vFlyteAir has the Twin Comanche in beta test. JustFlight and Thranda both said that converting the JustFlight fleet would be the next big project of Thranda after having finished the Caravan (which has happened by now), so we might see some motion there as well. Also LES had announced the Sundowner would come "soon", but that was nearly 5 months ago. That being said, so far we have more announcements than aircraft converted and ready to fly in XP12, and also XP12 itself is anything but mature. There are still a couple of issues Laminar has to solve (and yes, they're aware and working on it). I's say it's no mistake to wait until the end of the year, if stability is your primary goal. XP12 is really cool, but it's still mostly for early adopters who like to (or at least don't mind to) tinker with their sim. Back to topic: I'm not biased about aircraft class and size, I love them all. While I have a thing for light turboprops (gimme a PC-12 in XP!), I mostly fly in XP12 these days, restricting me to aircraft available there. In the past week, I had a blast flying the Challenger from Shemya down to Fairmont in British Columbia, via Anchorage and Pasco, WA. I mostly fly in FSEconomy, so I just fly where the (virtual) jobs take me. And while the Challenger is a great aircraft, I can unfortunately only fly it on weekends - it's an intense aircraft, and performing a flight (including planning and preflight) takes its time - more than I can spare on normal work days throughout the week. On these I did a couple of milk runs with the Caravan, which is relatively quick to set up and get airborne. For the summer I'm eagerly waiting for the LES DC-3 - this will be my go-to aircraft for my California routes in FSEconomy, with KNUQ serving as my hub.

This dropped pretty silently, but the XPLM400 SDK no longer bears a beta version designator... https://developer.x-plane.com/sdk/plugin-sdk-downloads/

Thank you Ilias, this is great news indeed! I'd have been a happy customer of the classic alone, but I love a good retrofit, so that second model is the icing on the cake for me. I'm really looking forward to flying its wings off.

IANAL, so take this with a grain of salt: I'd say if you publish something that's completely your own work, but enhances the experience with one of LR's aircraft (like a livery, or a plugin (REP comes to mind)), then you probably don't need express permission from Laminar (since your work doesn't touch any of Laminar's intellectual property). If you however derive your work from theirs (e.g. modify an object file or tweak one of their xLua scripts) and want to redistribute that, you'd be on the safer side by asking for their permission - an EULA would probably give you the answer; ironically I couldn't find one for X-Plane...

Current MU version hasn't been adapted for 12 yet, so that's not completely unexpected. Regarding landing technique, I'm not any wiser than you - I also tend to land her very firmly. Here's a video where you can see yoke and throttles during final and landing, maybe this helps figuring this out...

2023-02-10 15:44:12 CL650[except.c:225]: Caught EXCEPTION_ACCESS_VIOLATION Backtrace is: 0 00007FF65CFE1447 D:\X-Plane 12\X-Plane.exe+0000000000A81447 () 1 00007FF65D0301C3 D:\X-Plane 12\X-Plane.exe+0000000000AD01C3 () 2 00007FF65D03F930 D:\X-Plane 12\X-Plane.exe+0000000000ADF930 () 3 00007FF65CE7CE9F D:\X-Plane 12\X-Plane.exe+000000000091CE9F () 4 00007FF65CE7B3E9 D:\X-Plane 12\X-Plane.exe+000000000091B3E9 () 5 00007FF65CE4C8A4 D:\X-Plane 12\X-Plane.exe+00000000008EC8A4 () 6 00007FF65D58AB5C D:\X-Plane 12\X-Plane.exe+000000000102AB5C () 7 00007FF65CF1AC68 D:\X-Plane 12\X-Plane.exe+00000000009BAC68 () 8 00007FF65DA7CD8A D:\X-Plane 12\X-Plane.exe+000000000151CD8A () 9 00007FF65DA6FA82 D:\X-Plane 12\X-Plane.exe+000000000150FA82 () 10 00007FF65DC2B40E D:\X-Plane 12\X-Plane.exe+00000000016CB40E () 11 00007FFBDED626BD C:\WINDOWS\System32\KERNEL32.DLL+00000000000126BD () 12 00007FFBE0B4DFB8 C:\WINDOWS\SYSTEM32\ntdll.dll+000000000005DFB8 () --=={This application has crashed!}==-- --=={UUID: 6e8f7b59-f300-427c-9aa5-53bca3c894f6}==-- I suspect this is a segfault that happend inside X-Plane itself and was only caught by libacfutils, but not 100% sure, so I report it here just in case. debug.log Log.txt

Hm, I also use the TM Warthog throttle (same setup, without any intermediate software) without having the issues you describe. I have attached the control profile I use with the MU. MU2 control profiles.zip

The RXPs can be configured to draw power from one of the (standard) electric buses in XP. If the avionics switch doesn't hook up a standard bus, but instead uses some custom logic to power the other avionics components then indeed, this will become a rather interesting endeavor

AutoFoV View File About AutoFoV AutoFoV is a plugin for the X-Plane flight simulator, automatically setting the field of view based on the currently loaded aircraft. AutoFoV is open source; you can find its source code and more detailed instructions at its public GitHub repository. Installing AutoFoV AutoFoV comes in X-Plane's fat plugin format. Simply extract the directory AutoFoV from the zip file and place it as a sub-folder into the Resources/plugins folder of your X-Plane installation. Using AutoFoV AutoFoV allows to define a custom field of view for each aircraft model (i.e. for each .acf file in your X-Plane's aircraft folder and its subfolders). To define a custom field of view, simply create an empty file in the same folder and with the same name as the .acf file, but suffixed with .fov instead of .acf, and populate it with the numeric FoV value you want to use with this aircraft (only digits 0-9 and the decimal dot are allowed). Submitter daemotron Submitted 01/10/2023 Category Plugins and Utilities  

X-Plane's hypoxia effects are a bit blunt - exceed a certain altitude and you virtually pass out. That's not how it would work in real life, particularly if you had the chance to acclimatize to a greater base altitude (and even without it, a normally healthy person doesn't pass out at 12,000' - I've tried it on several occasions. Headache can become an issue though).

FoV setting per aircraft - ideally we could set all graphics settings in a per-aircraft profile similar to control profiles.

Since the TDS package is based on the Garmin trainers (just like RXP), I can't imagine that would work. The limitation with Garmin data is the same... Now if we want a native 750 GTN or GTN TXi using XP's data (or a custom Navigraph set), I fear there's no way around than talking Coop into coding one

I heared rumors that TDS is working behind the scenes to bring their 750 Txi (currently offered for MSFS) to X-Plane 12. Pretty much like the RXP, it's based on Garmin's trainers, so it will likely be Windows only.

RealityXP GNS and GTN have been updated to 2.5.0 (GNS) resp. 2.6.0 (GTN). These new versions support XP12, so one item less to worry about