skiselkov

The "before starting engine" checklist calls for the avionics to be OFF for most of the checklist. It wouldn't really make sense to have it in the G1000, if you need to have the G1000 off to complete the checklist.

They've changed the behavior of the XPLMGetAllMonitorBoundsGlobal function in Beta 5 and flipped the way it represents the top and bottom screen coordinates. This is what's messing up our window positioning. I'm hesitant to go change our code, because who knows if they won't revert it back to the older behavior in Beta 6.

They've changed the behavior of the XPLMGetAllMonitorBoundsGlobal function in Beta 5 and flipped the way it represents the top and bottom screen coordinates. This is what's messing up our window positioning. I'm hesitant to go change our code, because who knows if they won't revert it back to the older behavior in Beta 6.

That's a Laminar G1000 "quirk" of sorts. When zooming out past the 37NM range ring, the MFD switches map projections and needs to redraw the underlying map. While it does this, any further commands are ignored. This is not something we can fix, unfortunately.

You have enabled DISPLAY BACKUP mode (this mode is used in case the MFD or PFD fails - it compresses all information onto a single screen and makes all screens display the same image). You should be able to get out of the mode by pressing the red button on the bottom of the intercom panel to the left of the PFD. Aileron and rudder trim indications aren't available in backup mode, only elevator trim.

Did you perform any maintenance? That resets component temperatures to a zero state to simulate the aircraft having been sat in a hangar for a long time while maintenance was being performed. The earlier checklist bug - we're aware of it. It's a background rendering issue, where the checkmark isn't drawn quickly enough until the cursor leaves that subwindow and it stops being redrawn. If you scrolled up again, it would refresh itself and the checkmark would appear. We'll get it sorted soon.

Manually entered holds aren't supported by the underlying Laminar G1000 yet (it was absent from real G1000 software for a surprisingly long time as well). Until Laminar implement this feature, please use the following procedure to flying manual holds instead:

We use X-Plane itself to determine when icing occurs, so if it's not showing icing, that's something you need to either take up with FSGRW or Laminar. In any case, X-Plane internal conditions to get icing accumulation are approximately: Precipitation present (the more, the stronger the ice buildup). OAT between -5C and -20C. Any warmer or colder and you won't get ice accumulation.

The easiest solutions are to either climb higher, pick a different navaid that's closer, or use a different method of navigation (e.g. GPS). VOR navigation in mountainous terrain is a challenge in real life too. In your case I was able to confirm that solid KTM reception at 70 miles was possible only from 19,000 ft and higher. Any lower and the mountain tops around Kathmandu start interfering with the signal considerably. If you absolutely need a lower flight altitude, you can always try to use a secondary navaid for positional triangulation (the screenshot below you can see I used VTN NDB to get a station bearing - this can be used to confirm your along-radial position).

We use a custom VHF and HF navaid modeling algorithm that is not based on X-Plane's service volumes. Instead, we use the NTIA Irregular Terrain Model to estimate radio wave propagation between the navaid and the aircraft. We also properly model terrain obstruction. The reason you lost DME and could still see the VOR radial was because DME and VOR signals use different frequencies (DME is at approx 1.1 GHz, VOR at around 100 MHz) with different propagation characteristics. VOR signals are more resilient in partially masked conditions due their longer wavelengths having a greater propensity to diffract over knife-edge mountain tops. You can observe the radio model at work in real time by tuning a frequency, and from the simulator menu choosing Plugins > TBM900 > Debug > Navaid reception profile. The pick the navaid you wish to analyze from the drop down menu and the systems simulation will show you a terrain relief of the terrain along the path from you to the navaid:

We use standard X-Plane G1000 commands on the MFD keypad. See Resources/plugins/Commands.txt - you'll want to look for commands starting with "sim/GPS/g1000n3". Those are the commands understood by the MFD.

Framerate dips when panning around is indicative of texture swapping taking place. Can you provide a screenshot of GPU-Z's Sensors tab? Also, what is your texture quality set to. Did you make scenery changes between 1.0.5 and the latest version? What I suspect is that the texturing setting is set too high and with the extra load of orthophoto imagery can overflow your available VRAM, forcing the driver to swap textures in and out of VRAM on the fly, especially when panning around the scene (the driver swaps out textures that are not in view and tries to replace them with new textures that have come into view).

Your Mesa version appears to be quite old. Tested with Mesa 18.2.2 and the airplane loads without issues. We require at least OpenGL 4.2 compatibility in our shaders for AMD GPUs (your driver only advertises version 3.0). Here is an article that explains how to get Mesa updated: https://www.linuxslaves.com/2018/10/mesa-1822-released-how-to-install-in-ubuntu-1804.html Should be a simple matter of adding a PPA and running dist-upgrade.

Seems to work just fine: Also no freeze on sim exit. The freeze is indicative of a connection issue or a very slow connection. The chart loader tries to download the chart for 5 minutes before giving up - if you quit the sim during that time period, it can block on the background thread to finish.

Mistake in publishing, the update should have been named 1.0.9b from the start. That is by design. When the flight is complete, the passengers get off the airplane. The conditions are simple: the sim has been properly shut down (i.e. not a crash) and the aircraft is stationary.

We will be looking into that in the near future.

Build 1.0.9b should fix these issues. Found the crucial piece in the failure simulation code which was triggering too eagerly.

Please try in version 1.0.9b, especially check the maintenance manager. We have added a bunch of fixes to systems not displaying as broken when they are broken.

Unfortunately no, we do not support version downgrades. When on a programmed ILS approach, the aircraft initially flies in GPS mode, then when inbound to the final approach fix it will switch over to LOC mode and start tracking the localizer. Prior to 1.0.9b, we used to have a condition there that the horizonal deflection (HDEF) of the CDI had to be less than 2.5 dots before automatic LOC tracking on the autopilot would be enabled. That condition was causing trouble, as the G1000 would sometimes switch to LOC mode before less than full CDI needle deflection was detected (happened on very steep turns to final - around 90 degrees). So we got rid of that condition. It's not realistic, but it's the only way to work around this bug in the underlying G1000 simulation.

Thank you @danhenri and @fireone!

Yes, there was a regression in 1.0.9 where we inadvertently broke persistent files created in earlier versions on Windows machines. Recreating those state files should address the issue.

@argonius Thank you for testing, will update the data.

Can you please post the Log.txt from the crashed run. Unfortunately Windows Event Viewer isn't really usable, as all it says is "Crash in the TBM code, somewhere, for some reason".

IRL there is ambient light scattering going on inside the cockpit, which helps brighten things up quite a bit. That doesn't happen in the sim due to lighting engine limitations. So if we were to just make the surfaces color-accurate as they are IRL, they'd look unusable in the shade. We've tried to strike a balance here, but we might need a somewhat more drastic approach. We'll be looking at some more workarounds for the lighting model in the next update.

The fix will be out tomorrow for everybody. You will be notified via an e-mail to your X-Aviation e-mail account, and we'll also put an announcement in our Discord group.