daemotron

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

Thanks, fixes the CTD. If DRT is a problem, does the Challenger work with DRE? I'd need one of the two...

Steps to reproduce: Freshly installed Challenger 650 v1.7 on XP12 (12.00r6) Start X-Plane Configure a new flight with the Challenger, real weather, real time, at KPDX (using Flightcraft 5 as startup position), with engines running not ticked The loading starts, then the CTD occurs. The log gives this backtrace: 2022-12-25 21:28:48 CL650[xplane.c:2817]: BOOT: ecs_init 2022-12-25 21:28:48 CL650[dr.c:553]: assertion "dr->value != ((void *)0)" failed: CL650/glass/heat_on Backtrace is: 0 00007FFFE36906BC C:\WINDOWS\System32\KERNELBASE.dll+00000000000906BC () 1 00000000806DA7F1 D:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000006EA7F1 (read_int_array_cb+121) 2 0000000000000013 D:\X-Plane 12\X-Plane.exe+0000000000000013 () 3 000000A68F4FC560 D:\X-Plane 12\X-Plane.exe+000000A68F4FC560 () 4 FFFFFFFFFFFFFFFE D:\X-Plane 12\X-Plane.exe+FFFFFFFFFFFFFFFE () 5 000000008132D5C0 D:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000133D5C0 () 6 000001C73A364650 D:\X-Plane 12\X-Plane.exe+000001C73A364650 () 7 0000000000000014 D:\X-Plane 12\X-Plane.exe+0000000000000014 () 8 000001C73941AF38 D:\X-Plane 12\X-Plane.exe+000001C73941AF38 () --=={This application has crashed because of the plugin: Challenger 650 by Hot Start}==-- (cf. to full log attached) Log.txt

Personally (but that's not more than crystal ball gazing) I would interpret it in a way that some changes are going to come already in X-Plane 12 (just not in 12.0, but in 12.x). What these changes are and if they actually prepare for streamed scenery, I have no idea. Maybe Laminar will just focus on providing an API, and leave the actual scenery streaming to third parties (in my book, Orbx would be suspect no. #1 for this). Maybe they come up with something of their own. We will know once Austin decides he can tell the public.

If you notice ice is building up on the windscreen, it's high time to turn on the TKS system and escape from the icing conditions. Pretty sure then ice is also building up on your airfoils and the propeller, which is what will ultimately lead to a crash. The TKS system isn't designed to fly continuously in icing conditions, it's merely a tool to help you escape from those without falling out of the sky. So when it happened to me, I set up both, the air conditioning and the TKS system to get rid of the ice. If one of them alone would have cleared the windshield, I do not know.

It takes a while to get rid of ice on the windscreen if it has already built up. I once ended up with an iced-up windscreen (forgot to take appropriate preventive measures), and it took like 20 minutes or maybe even a bit longer to get rid of the ice.

Philipp Ringler also hinted that there would be a significant change (with regards to scenery) coming later down XP12's release cycle. It was back at the Aero exhibition, in April 2022. Here's the video (in German, so I'll provide a transcript below) - check out from 8:35 onwards: Julius: And now for the last question, which of course I have to ask: How do you deal with the competition, i.e. Microsoft Flight Simulator (if you can call it competition), which has pretty strong visuals and offers scenery streaming? Are there any plans to go down that road as well at Laminar? Philipp: We're going to do something about the scenery system, however not for X-Plane 12. We already broke compatibility with weather addons, the whole weather system is completely new, and no stone was left unturned. If we would now go and tell people that all their weather (addons) don't work anymore, and they also had to bin all their scenery and airport addons on top of that - well, we just can't do that. So, something will definitely happen in the area of scenery, but not for X-Plane 12.0 (he emphasized "point zero" - translator's note). In due course of the time X-Plane 12 is the current release (keep in mind what we added in X-Plane 11 in due course of its release cycle), so in due course of X-Plane 12's release cycle something is going to happen with the scenery system. Just don't expect to install 12.0 (he emphasized "point zero" again - translator's note) right after release and have ortho scenery out of the box. That's not gonna happen.

Each development team will assess the risk involved releasing an aircraft for a not yet final release of X-Plane (as I see it, XP11 wasn't even close to stable before 11.10; a lot of aircraft had to be adapted after Austin had some fun with the free shaft turboprop engine model, setting them... uhm, well, on fire ). Depending on the complexity of the aircraft, the team's aspiration in terms of perfection, realism etc., the team's capacity to manage early-access issues, the (perceived) evaluation of XP12's stability and maturity, and probably many more factors, the development teams may come to different conclusions as to when is the right moment to update, upgrade or refurbish their products. Also bear in mind that some developers have already been involved in XP12 since the days of the first alpha builds, and others just started their familiarization journey with the public EA. And that's perfectly ok - IMO each team should only release if they feel comfortable doing so. Anything else just leads to inappropriate expectations, misunderstandings, and disappointment on customer side, and/or burned-out and frustrated developers on the other side.

Thank you, Ilias, that's great news - the Sundowner v2 is a superb aircraft, looking very much forward to do some cloud-dodging in XP12 And a huge thanks for the G500 retrofit; this looks to be an awesome panel!

That crash is happening on Windows, not Mac, so I think this is something else going on here. In particular since I only deactivated (moved) the rsg_g500 plugin folder but kept the OpenGPWS one. Unfortunately, those crashes are "hard" CTDs, i.e., the log is just ending abruptly, and also XP doesn't generate a crash dump in those cases - doesn't make it any easier to figure out what's happening. Only correlation I could find up to now is the combination of startup location and the G500 plugin. Now what's interesting is that I can load the Cessna 172 with G500 on those spots without producing a CTD (which also uses both plugins, G500 and OpenGPWS). Conclusively, it must be something in the interaction between the G500 and the MU-2B which causes this crash. If I can obtain a log or crash dump, I'll upload them here. P.S. another observation: this crash only happens if loading the MU directly after starting X-Plane, i.e., loading it from the "Start new flight" screen. If I load the C172 first in such a spot, and then switch to the MU, it doesn't crash. P.P.S. the OpenGPWS crash on unload (known for Mac iirc) also happens on Windows (cf. attached log and crash report). crash_report_11_13_2022_07_44_53.rpt Log.txt

Observed in the 5 Blade GNS model - as the title says, the clock's display remains dark (button backlights do work though). From the information available at https://www.davtron.com/product-detail.php?M877-17, I couldn't really figure out whether the A models (grey face plate) do have a lit display or not, but in the general feature description it says things like "BRIGHT SULIGHT READABLE DISPLAY" and "AUTOMATIC DIMMING", so I'm assuming also the display of the A model would be somehow readable at night.

There's a thread on XP12 progress over in the general discussion area:

I use the "Save control positions on exit" option with the MU2, but I noticed the parking brake lever's position is not saved - it always defaults to OFF. I even have a two way switch assigned to xscenery/mu2b60/set_parking_brake (resp. xscenery/mu2b60/release_parking_brake). I usually keep it in the SET position when shutting down the sim, but when I reload (with the switch in the SET position), the parking brake still defaults to OFF - a bit of an issue if the MU loads in a spot that's not perfectly level. Would it be possible to either save the state of the parking brake lever with the other controls, and restore it, or alternatively initialize the parking brake in the ON position?

Can confirm now it's at least related to the G500 plugin. I deactivated it (moved it out of the plugins folder and into plugins_deactivated), and the MU loads without crashing.

Fresh attempt - I reset all Mu-related configuration files and deactivated the RXP GTNs. Now I could start it. Weird, but *shrug* In return, I found another issue - the MU seems to be sensitive with regards to where it's loaded. Example: when I try loading it at CYYR (11.55 default scenery) ramp position 38, it CTDs a few seconds after having been loaded. At ramp position 40, no issues. (also with the RXP GTNs deactivated). My suspicion: it could be the G500 plugin (which loads in the background, no matter which version of the MU you actually load in sim) - position 40 is on a fake tarmac, not a real taxiway tarmac.

The 5 blade GNS version seems to have an issue with engine management: the yellow ignition light doesn't come up when trying to start engines (exactly following the checklist) engines can be started through the menu though (Shift+Ctrl+e) if started this way, props don't come off the locks when trying to unlock them The 5 blade glass version works completely normal; engines can be started, and props unlocked after start. Any ideas?

The numbers are a bit off, but not that much. My POH recommends 72% torque for a cruise altitude of 24,000 ft (ISA), which should result in 193 - 205 kt CAS (depending on weight). In your screenshot it looks as if you were temperature-limited on the engines and therefore could not reach the recommended torque - ending up at 165 kt IAS with less than 60% of torque seems about right, or even a bit fast when comparing to the POH numbers.

Cooper already confirmed he'll update the G500 plugin for XP12, but a bit further down towards a more stable version of X-Plane. Also Tom and Cameron both confirmed there will be an XP12 version of the Moo, so all we have to do is being patient and wait - XP12 won't be a beta forever

Observed in the 5 blade glass variant, version 2.0.4: from outside, the glass looks as if it weren't there: When looking from a different angle, it's obvious the glass object must be there however: To me it appears as if there's something going on with the tinting or reflection of the glass, but it could also simply be my dreadful eyesight ^^

I have played with the GTN configuration to see if I can improve the integration with the G500 to a similar level we see in the BN-2 Islander. So far I managed to see the whole flight plan from the GTN drawn in the G500 by modifying the RealityXP.GTN.ini file: [GTN_750_1] ... stuff that's been there already ... MasterDevice = true LinkHsi = true LinkCrs = false LinkObs = false LinkVor = false LinkOto = true LinkSimGps = true AutoNavGps = true AutoCdiSrc = true What doesn't work yet is having the CDI show the correct course (LinkCrs didn't work, nor did LinkObs, so there must be something else). While the GTN is in GPS mode, the G500 blocks the course selector, so it also can't be adjusted manually by the pilot. Maybe @Coop could point us in the right direction here.