Coop

Since the release of the Take Command! SR22 Series, we have been hard at work adding features, fixing bugs, and making general improvements throughout! We are preparing to enter a Public Beta in the coming days (if you are interested in being a part of the Public Beta, you can sign up for a spot here – Note: spots are limited), followed by a general release to everyone once it is ready! Here are some of the key features we have implemented: G1000 Terrain Profile Indicator We have integrated a custom terrain profile indicator on the MFD. This will help for situational awareness, especially in mountainous terrain, and help prevent CFIT incidents. The custom system is entirely multi-threaded to prevent any performance penalty. Visual Icing Effects We have been hard at work adding custom visual icing effects to the aircraft! This will help with situational awareness surrounding the use of TKS during icing conditions, as the simulated ice can now be seen on the wing, inlets, windshield, spinner, and other relevant surfaces! Engine and System Model Improvements There have been many improvements made to the engine model and system model. Here are a few highlighted findings from our debugging and fixing: SR22TN Power Fluctuations There was an issue leading to potentially severe fluctuations of engine power during takeoff and climb at high ambient temperatures and altitudes, on the SR22TN only. The cause of this issue has been eliminated. However, there may still be minor residual fluctuations on takeoff and initial climb under such conditions, largely attributed to mixture being slightly too rich for such higher density altitude takeoffs. It can be further amplified by too quick movements of the power lever. To get rid of any remaining fluctuations altogether, embrace the following steps when setting takeoff power at high temperatures and/or density altitudes: Advance power slowly until the point where RPM rises above 2500 RPM (around 80% lever travel) and wait for manifold pressure to stabilize. This will take a few moments at altitude and is particularly important up there. Start your takeoff roll and simultaneously advance power slowly to maximum. Procedures allow you to lean the mixture to 34GPH for takeoff on hot days. It is suggested to follow this step at OATs in excess of 30-35°C to eliminate any residual power fluctuations. Advance the mixture to full rich after obstacles are cleared. Also keep in mind that it is normal for the turbo-normalized engine to slightly fluctuate for a few moments after power changes before all parameters stabilize. Thus it is generally recommended to make power changes slowly on such engines, so even during go-arounds better take 2-3 seconds to advance to full power. Random engine cutout during taxi There was an issue leading to seemingly random engine quits during taxi. A fix is in place that has proven to work in internal tests. Engine starting The fuel-injected IO-550 engine can be challenging to start at times, so video tutorials to prepare you for all kinds of cold, hot and flooded starts you may face. We have also seen the most typical cause relates to mispositioning the power lever for engine starting (some even at maximum), keep in mind to set the lever to about 1/4” (i.e. at or slightly above the letter R in POWER). We have determined that there is no issue with the custom engine model. Engine cutout after landing When landing at higher density altitudes with the power lever at idle on rollout, it is to be expected that the engine may not be able to hold its idle RPM due to an excessively rich mixture. Lean the mixture to the appropriate X-T letters in MIXTURE immediately after landing and try to keep the power slightly higher than low idle to prevent the engine from quitting in such situations. We have determined that there is no issue with the custom engine model.

Hm, I am not seeing anything that is catching my eye in the log. I will dig into it a bit more, we have a bunch of stability fixes with 1.1 coming really soon that should also help if it is being caused by the SR22.

Hi Paul, We are in the middle of getting the G5 main installer updated to the new G5 1.2.0 that comes with the Islander. It should hopefully be ready in the next few days (you will get an email).

Hi Paul, Contact X-Aviation support directly and they should be able to process that. https://www.x-aviation.com/catalog/contact_us.php

The X-Plane G1000 uses the installed Nav-data (we don't touch the G1000's navigations components). I would make sure you are updating using the X-Plane 11.50 Version nav-data (there were modifications made to the format).

The trim speed will be faster in the next update

ESP is not equipped/simulated on our variant (it was optional equipment)

Starting with engine running will override any persistence settings and set all the switches to a generic flight configuration.

The holding functionality of the LR G1000 is not fully featured, we don't have a customization of the navigation system, so any features in that regard would need to come from LR.

There is a command to open/close all doors in the BN-2B Plugin menu item in the top bar of X-Plane. The click-spots are located at the interior door handles, they swing out with the door.

The Islander just uses the X-Plane engine model, there shouldn't be anything on our end that could stop this (unless Gizmo is not activating the plane, I would need to see the log.txt to know). You can try deleting the file "BN-2B Islander_prefs.txt" in the main Islander folder, and "persist.cfg" and "settings.cfg" in Islander plugins/is_systems/settings. These should reset the plane to the as-installed condition.

Yes, the older versions of XGS are the typical cause of the Error 127 preventing our plugin. Glad its working now!

Hi David, Can you upload your log.txt file?

This functionality is provided by X-Plane itself. Adding some sort of internal slew mode is not currently on our short list, something we might consider down the road. For now, just imagine that the FBO line workers moved your plane around to the spot they want it at

Thanks for the report! We are looking into it

Hi Jean, I just tested and I am not able to replicate this issue. Can you confirm that the Avionics switch was turned on? The audio panel is one of the few things that is actually on the Avionics bus.

Thanks for reporting. We have this fixed for the next update which should roll out shortly.

I will reach out to RealSimGear to see if perhaps there is something in their config files.

Thanks for the bug report! The G1000 state tracking system should be getting an overhaul soon with the coming updates.

Not currently, but I will let you know if we need anything @wired521 Thanks!

Pressing and holding CLR on the GCU should reset the MFD after a second or two. Are you able to replicate the series of button presses required to get the Engine page to disappear? If that is happening something is missing in our state tracking system somewhere that we need to address, but currently I can't replicate it.

The X-Plane GCU frequency integration seems to be a bit finicky. From my testing, it seems to require the trailing zeros that are in the number before hitting enter.

We are still working on tracking it down. @wired521 Are you on a Mac as well?

I'll look into this, though it isn't as high of priority as other more critical fixes.

Sadly, it does not appear that LR's G1000 supports ADFs.