EGT

I'll check it out again. I have two controllers, and I'm not using any other software between them and XP, so XP is using the raw inputs. I'll also check the keybinds again.

Hi, Is the engine modelling outside of X-Plane? When setting the condition levers to TAXI in the Beta range, EGT rises from 200-300 deg. C to 700 deg. C. Seems rather hot!

Hi, As I understand it, the 750 and 650 should only be powered when the radio master is ON. As it is, the 750 powers the second battery power is available, and there is no way to switch it off.

Hi, I tried to map the key bind for single condition lever "toggle between EMER and TAXI", but it does not do anything.

Hi, There are a few problems with the setting UI: * It doesn't like scaling factor (Windows is set to 150%) and so draws half off the screen (top half of the window is cut off). * Option to place the inlet covers is missing

Hi, I'm using a hardware throttle (TM Warthog throttle) which is mapped using standard axis in XP11 as per the recommendations in the MU-2 documentation. The throttle is a single throttle mapped to Throttle 5, and the other throttle is mapped to prop lever (PROP) as stated. The option "manipulators with hardware" is UNCHECKED. There is a serious problem with how the HARDWARE is interacting with the sim. The throttles and condition levers are working correctly IN SO FAR AS the animations, detents, etc., and working, and I can operate the THROTTLE detent via a button on the throttle to lift the throttles. Basically the bugs as I can see them relate to how the MU-2 handles hardware input, in addition to several missing or malfunctioning features. First, the throttle: * Moves the levers as expected * Gate works correctly * Button to lift throttles for single-lever hardware works However... the engines do NOT respond to the throttle. Second, the condition levers. * Moves the levers as expected * Gate/toggle does NOT work However, again, the engines do NOT respond to the hardware! This also makes it IMPOSSIBLE to start the engines using the normal procedures AT ALL. The workaround. Before starting the engines, the levers MUST be moved USING THE MOUSE to TAKEOFF/LANDING then they can be operated with the hardware throttles. Failure to do this results in the engine system thinking the condition levers are still in EMERGENCY/FEATHER position when they are NOT. Levers in the cockpit are moving in response to the hardware when this happens. A similar problem exists with the throttles, however that bug relates to the setting of "use manipulators with hardware". The manipulators MUST be disabled, otherwise the engines totally do NOT respond to either throttle or condition lever input. After I figured this out I was finally able to go flying, but it rather soured my initial experience with this aircraft.

Hi, What is the difference between GNSS and NAV mode on the DFC90? It seems either will track GPS or NAV based only upon GPS mode. I'm using the RXP 750/650 GPS.

Reduce AA. Try just FXAA rather than something more intensive.

You're welcome!

+1

Thank you to you as well.

LOL. Seriously? Insufficient? It tells you exactly where it crashed and why. You clearly know nothing about software development or debugging. Yes, it is the latest build. Log file attached (but there is nothing else of use). If you followed my reproduction steps, it would crash 100% for you, too. Log.txt

The pertinent part is already quoted. I need to crash it again to generate the log file, but there is nothing else useful. It will happen with any airport/runway. Here is the original report:

Hi, I get a CTD when I do any of the following: * Enter only a destination airport ICAO then select a takeoff runway or * Enter only a destination airport ICAO then select an arrival runway (this is OK), then select a departure runway (CTD). I don't get a crash dialogue like before, but just the X-Plane crash reporter. I reported this after initial release. Seems it was never fixed. [code] 2022-05-21 02:30:18 CL650[fpl.c:1064]: assertion "fpl->origin_arpt != ((void *)0)" failed: Backtrace is: 0 00007FFAE2403E49 C:\Windows\System32\KERNELBASE.dll+0000000000023E49 () 1 0000000080326842 D:\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000336842 (insert_origin_leg+392) 2 000000008032E7C8 D:\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000033E7C8 (fpl_set_origin_rwy+138) 3 00000000803E0FB7 D:\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000003F0FB7 (dep_arr_key+687) 4 000000008039609E D:\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000003A609E (fmc_main+35e) 5 0000000080507937 D:\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000517937 (runpool_worker+1207) 6 00000000804FFCBF D:\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000050FCBF (_lacf_thread_start_routine+f) 7 00007FFAE3166FD4 C:\Windows\System32\KERNEL32.DLL+0000000000016FD4 () 8 00007FFAE473CEC1 C:\Windows\SYSTEM32\ntdll.dll+000000000004CEC1 () 2022-05-21 02:30:19 CL650[fdr.c:465]: frame skipped 0-4 --=={This application has crashed!}==-- [/code]

Hi, Could we get a maintenance feature whereby we can call maint to fix parts of the aircraft or service bottles, etc.? A bit like we already do with the de-ice truck?

Get a faster hard disk or more memory. I fly over high-res ortho (I have terrabytes of the stuff). The hard disk is non-stop over those areas but XPL never hiccups.

If you look carefully she isn't making the rated thrust. There is quirk with this aircraft in that if you fly too slowly in cold temps, the FADEC believes the air density is higher than it is, so reduces thrust. The problem is the air is not that dense, so it is no longer producing the *required* thrust. Consequently, you decelerate, which causes it to further reduce thrust. By flying faster, you increase TAT, which makes the FADEC think it is warmer, and so it increases thrust on the engine enabling it to maintain higher speeds at higher altitudes. I found it better to climb at 280/0.76. If SAT is very low (ISA-10 or lower) I find it beneficial to cruise at Mach 0.8 rather than anything faster as it doesn't have the thrust. I had a TAT of -48 the other night (ISA-18).

Hi, I didn't say the landing lights didn't work. I was very specific: the NOSE lights do not illuminate the ground. My XPL settings are maxed.

With a flight plan entered, ensure you entered a cruise altitude in the PERF page (PERF x 2, LSK1L). Check the flight plan shows climb (increasing crossing altitudes to cruise) and that the altitude selector is set above the current aircraft altitude. Press VNAV on the FCP, then press FLC, then in the FMS press PERF x 2 and select "RESUME xxx". VNAV will now control the speed as per the VNAV speed schedule.

You can only select it. If you select it, FMS VNAV will control the speed. If you want manual control of speed, just select a different speed with the speed selector knob on the AP control panel.

There may be a broader issue with chart display. Even the FAA charts do not work at the moment. It appears it is something to do with SSL certificate handling in the sim.

Hi, I noticed earlier that switching on the nose landing lights doesn't actually illuminate the ground? Is this WIP?

VNAV button remains lit when valid. All vertical modes become VNAV modes with exception of VPATH which auto-arms at ToD. FLC = VFLC (follows VNAV profile in either climb or descent) ALTS = VALTV (respects crossing restrictions regardless of set altitude) VPATH = auto-armed at ToD and will commence descent if altitude selector is lower that present altitude (double chord sound at path intercept) Ensure the option (PERF x 2) is set for "ENABLE ADVISORY VNAV". It will draw the vertical diamond on the PFD when the vertical path is near. Also ensure to "RESUME VNAV SPEED" (PERF x 2) to get it to follow the VNAV speed schedule, otherwise the selected speed takes precedence.

This is a known issue. Toto himself spotted it in a stream when he was trying to demo stuff.

...everything FLEX is supposed to avoid!