Malaromane

Another update to Aerofly has been released (patch 2026-04-17). This one adds a new Airbus A321XLR to the sim (https://www.aerofly.com/features/aircraft/a321xlr/) Change-Log (2026-04-17) New A321XLR added Two new A350-1000 liveries added Minor autopilot bug fixes Minor assistance bug fixes They've made additional changes in the A321XLR which they plan to roll out to the entire A320 family at a later date: Status page automatically removed after 3 seconds when status normal Changes to the alternate braking logic and hydraulics Nose wheel steering and brakes can now fail when hydraulic pressure is lost Additional indications on the ECAM wheel page Nose gear light visual model removed, not needed since we've installed the MFRL in the wing root

Well the good news is that the supposed hold up on finishing the TBM update was that Toto was focused on the CL650 update. So the path should be clear for the TBM update now! Here's hoping. I truly miss that aircraft but just can't bring myself to reinstall XP11 just to fly the TBM.

I just tried it 20 seconds before writing this response post and it's working for me.

I've patched up but haven't had a chance to take it for a flight yet. Really hoping that the "...dedicated pause/freeze command for Tobii Eye Tracker..." means that when I pause the tracker, the view will remain where I paused it rather than recentering.

Release notes pasted below. There's also a Laminar blog post about the release available at https://www.x-plane.com/2026/04/whats-new-in-12-4-2/ Public Beta 12.4.2-R1 (Yes we know it's called R1... this is still a Beta release! Please check the beta box or use the beta_channel) ATC Fixed a crash when entering a flight plan on the ATC screen (XPD-17948) Avionics Fixed a crash when using a secondary monitor for avionics display, such as the G1000 PFD Graphics Engine Fixed an issue where aircraft LODs (Levels of Detail) were not switching correctly with distance, causing only the highest-detail model to render at all ranges and leaving visual artifacts at maximum distance (XPD-17984) Graphics engine improvements, including updates to the VMA allocator and Vulkan transfer coordinator for better performance and stability (XPD-17946) Flight Model Loading an in-flight situation file is now significantly more stable. Aircraft previously exhibited pitch oscillations and erratic behavior when resuming a mid-flight save (XPD-17832) Scenery Nice Côte d'Azur Airport (LFMN) - improved custom airport scenery with enhanced detail and accuracy. Many thanks to Matthias Gerstberger for this update! Windsock indicated airspeed accuracy - windsock deflection now more accurately reflects actual wind conditions (XPD-17994) Updated Global Airports with the latest approved submissions from the X-Plane Gateway. User Interface & Controls Fixed a crash when displaying "All Planes Altitude" in the Data Output window (XPD-17962) Added a dedicated pause/freeze command for Tobii Eye Tracker users (XPD-17867) Fixed the joystick configuration for the Honeycomb Echo Controller, as four buttons were not registering correctly and are now fully functional (XPD-17983) Also, a separate post about an X-Plane Gateway update has been posted at https://developer.x-plane.com/2026/04/x-plane-gateway-update-12-4-2-april-2026/

Just figured I'd resurrect this old thread to mention that there is now a test version of SimHeaven X-World Pro available to download and try out: https://simheaven.com/package/x-world-pro-test/ I've downloaded it but not yet had a chance to set it up.

According to the FAQ on X-Codr's website: Based on their statement that "it's position in the ini does not matter", it leads me to believe that the contents of that directory consists of library files and thus, ordering is irrelevant.

Well, the absolute easiest way is to just use Winctrl's SimAppPro which maps pretty much everything for you out of the box (for supported aircraft models). On the other hand, if you're willing to spend some money, I can highly recommend SPAD.next. Support for just about all of the Winctrl devices is in place and you can usually find "snippets" that others have already created and shared for various aircraft models.

X-ATC-Chatter is also affected.

On the other hand, as a non-tubeliner guy, it's nice to see the X1000 getting some more love: Also happy to see the native Tobii Eye Tracker support getting some improvements: Thanks Laminar!

Pretty sure you'll still need a PC in the loop somewhere. The "streaming" part is streaming X-Plane from your gaming PC or a cloud gaming server (via NvidiaXR) to your AVP headset that's running a "companion app". If you want to be able to use your existing flight sim peripherals, they have to plug into a USB port somewhere and that's not going to be a cloud server.

Because he has the E195 which is part of the X-Crafts E-Jets family (E170, E175, E190, E195, and Lineage 1000). The v2.0 upgrade for those jets came out quite some time ago. https://www.xcrafts.com/ejets-family They are not the same as the ERJ family that was just released yesterday. Those are comprised of the ERJ 135, ERJ 140, ERJ 145, ERJ 145XR, and the Legacy 650. https://www.xcrafts.com/erj-family

If you watch the AviationLads trailer on YouTube and jump to 1:20 in the video there's a very clear shot of the ERJ FMS units and they don't look like the default XP12 Citation X FMS to me:

Got a small patch for FS4 on Steam today. Patch notes below: Changelog Version 4.08.01.14 (2026-02-05) This update features the following changes: Improved performance when using the Vulkan renderer New renderer for Apple Silicon based Mac computers Minor fixes to the autopilot and flight management code Small corrections on the C172 and B787-9 Added a few more new landmarks world wide I've installed the patch but haven't yet had a chance to try it out.

It's the very first line of the release notes above:

That was never promised as part of the 12.4.0 update. https://www.x-plane.com/2025/12/x-plane-roadmap-update-december-2025/

Beta 5 for X-Plane 12.4.0 available now. Release notes (https://www.x-plane.com/kb/x-plane-12-4-0-release-notes/): Public Beta 12.4.0-B5 ⚠️ Notes: SAM will no longer work in this beta (unfortunately unavoidable due to some SDK violations). Users are advised to switch to openSAM https://github.com/hotbso/openSAM Aircraft Airbus A330-300 Fixed an issue where arming LOC mode would switch to HDG mode (XPD-17688) Fixed an issue where to autopilot auto-engaged back-course. Back-course should be engaged either by entering “B” for the course on the RADNAV page, or automatically as part of auto-tuning for a LOC back-course approach that is in the flight plan. Graphics Improved logging in case of a device loss error User Interface & Controls Added new menu item “Settings” to the file menu Fixed some translation related issues (XPD-17733) Blacklisted SAM plugin due to many crashes Fixed various crashes

Haven't had a chance to check it out fully but definitely nice to see a reported fix for FPS loss when popping out avionics.

Beta 4 available now. Release notes posted at https://www.x-plane.com/kb/x-plane-12-4-0-release-notes/ Public Beta 12.4.0-B4 ⚠️ Notes: Plugin authors are advised to privately contact us now regarding any outstanding issues. Aircraft Fixed a crash when starting a flight using the Grumman F-14 Tomcat with AI - Aircraft in place Avionics & Radio There will be no longer a huge FPS penalty when popping out an avionics instrument (XPD-16890) Fixed ATIS Frequencies (XPD-17705) Graphics Fixed scenery flicking when using popped out windows (XPD-17621) User Interface & Controls Show ramps and runways correctly when returning from the special starts view back to the airport view (XPD-17706) SDK Improved error logging and handling Fixed function XPLMIsCursorOverAvionics Fixed 3d mouse cursor callbacks of custom devices Fixed a crash when right-click dragging out of a custom device manipulator XPluginReceiveMessage will be called with the correct plugin id now, when a plugin requests TCAS/AI control (XPD-17713)

Hot off the press https://www.x-plane.com/kb/x-plane-12-4-0-release-notes/: Public Beta 12.4.0-B3 Aircraft Fixed an error where the landing gear indicator lights were broken on fixed tailwheel planes (XPD-17687) Fixed an issue where the flight plan route was not shown correctly on EFIS Maps (XPD-17691) Airbus A330-300 Various smaller improvements and fixes Fixed an issue where the “Managed Dot” on the altitude indicator did not extinguish when reaching cruise altitude (XPD-17391) Graphics Fixed an issue where the sky wasn’t drawn correctly (XPD-17690) User Interface & Controls Fixed a crash when the user slewed an aircraft on the map with chocks set (XPD-17680) Fixed an issue where the camera position wasn’t populated correctly to the corresponding datarefs (XPD-17694) Fixed an issue where popping out an avionics screen to Operating System level could cause a FPS reduction (XPD-16890) VR Fixed an issue where the radial menu was hanging sometimes (XPD-17686) SDK Improved error handling in case of unexpected behavior of plugins Improved stability of SDK in case of plugin errors (XPD-17697 & XPD-17689) Fixed an issue where mouse cursor callbacks didn’t work anymore when using 3D Custom Avionics panels (XPD-17702)

Available now.

Either XSaitekPanels (free): https://forums.x-plane.org/files/file/14646-xsaitekpanels-linwinmac/ Or SPAD.next (not free): https://www.spadnext.com/home.html There are probably other ways to do it but those are the two I know about. Google is your friend.

Careful Goran. Your bias is showing. 🙂 But I agree; the CL650 is the cream of the crop. Now if only there was a TBM for XP12 that we could all fawn over. 😜

I believe that's actually what's triggering the crash (in SPAD and many other plugins). According to the dev, the underlying "bug" is that the crash is triggered when the plugin attempts to de-register its private commands when shutting down.

I know. After all, I took the time to fully diagnose what was causing the issue before submitting bug reports. I merely posted the information so that others who might be encountering this crash -- which is being triggered by many more plugins than just the SPAD.next connector -- know what's going on. As for me, since the crash is occurring on shutdown and I need the SPAD connector for my various peripherals, I'm content to live with the Safe Mode prompt on start up until a fix is released.