Coop

So does this crash occur when going through the G1000 PFD and deselecting Synthetic Vision? Please send your log.txt when this happens so we can see what is going on to cause this.

We have pushed 1.2.0 to the store which has this fix. The installer is being built currently and should be released very soon You will get an email from X-Aviation when it is ready.

There are three different things at play with this: There are some slight issues with the current flap behavior, which can affect speed behaviors. There are ranges to these, its not an exact % for each individual aircraft and changes with weight and balance. There are some issues that X-Plane is working on that affects L/D behavior. Experimental flight model should help in this regard.

Ah, X-Plane's failures can be a bit odd with a prop strike or something else they deem a "crash". It essentially pauses large segments of the sim exactly where they were last.

With the current G5 version, reduce the width and height (g5_w_a/b and g5_h_a/b) since this aircraft's panel space is too small. We are working on the installer for the 1.2.0 update which will have a panel-less render mode (and an option to set for it to work in non-3d cockpit views. That should be coming shortly.

Yes, the fix is in the coming 1.1 update (in Public Beta now)

For that use case, I recommend waiting until 1.2 is pushed (installer is being built) as it has a mode where the G5 panel rendering can be disabled and used only in popup mode.

There isn't an explicit way to choose the cruising altitude, there are many, many variables that need to be taken into account: Cruise performance with payload Winds-aloft Flight duration Density altitude/temperature Weather Just to name a few.

We have the 1.2 update getting prepared to ship out that includes many improvements for the popup mode, hopefully this should be coming out any day now. In the interim, inside the acfConfig.cfg file in Baron B58/plugins/G5/settings, you can adjust g5_x_a, g5_y_a, g5_x_b, and g5_y_b such that the G5 won't render over existing gauges. (The update adds the ability to disable panel drawing and have a popup-only rendering mode.

It isn't that the achievable density altitude increases with decreased power, but vice versa. As you climb, since the engine isn't turbocharged, with altitude the engines produce less and less power, hence why only lower power %s are achievable at higher density altitudes. Power % does not equal throttle location.

The popup windows are 1024x768 pixels, the height of the drawn G1000 is based upon the window width. Thus with this monitor configuration, the top of the G1000 is getting cut off with the width of that window. Making the window narrower on the monitor should fix the issue.

Here is the same file, the G1000 window should resize like any other window on your computer when popped out. g1000_nobezel.png.zip

No, you can run 11.50 in OpenGL mode and the aircraft will still work (the aircraft just needs 11.50, it doesn't care whether OpenGL or Vulcan/Metal is used)

The Terrain Profile is coming in version 1.1, which is now in a public beta. There is a form linked at the post here that can get you added to the next batch of users on the Public Beta:

Oh, if you are getting the X-Plane crash reporter, then X-Plane itself is crashing for some reason, not the SR22 (any crash caused by our plugin would prevent the X-Plane crash reporter from triggering). I would recommend trying a vanilla install of X-Plane and slowly adding back in your scenery and plugins to see if you can get the issue to replicate. Also, make sure your GPU drivers are on the latest update.

I can't replicate this issue on my side, I would imagine this is being caused by some other plugin conflict as we aren't doing anything involving the replay system.

I would think this is probably something unrelated to the Islander 1.1.1 -> 1.1.2 update, nothing significant was changed with the 3D that would have changed anything performance wise. Trying deleting (back up first) the X-Plane preferences might be a good start to try to get it working.

https://forums.x-pilot.com/forums/topic/19283-take-command-sr22-series-11-feature-preview/ There is a signup link the public beta here

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)