Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by skiselkov

  1. You can trigger failures using the IOS, sure, but you won't be able to see the few custom ones we have (things like fuel leaks, etc.).
  2. skiselkov

    MFD Pages Groups

    This is unfortunately a limitation with the stock G1000 integration. We can't quite freely organize the page groups and need to work within the confines of the stock avionics. As for the airport info page, that is a feature request that should be submitted to Laminar, as it's them who controls the contents of that page (this page isn't customized by us).
  3. skiselkov

    Synthetic Vision Not Working, Sometimes

    @Greaser Please make sure you have stock X-Plane scenery, or hd-mesh-scenery installed underneath any ortho tiles generated via Ortho4XP. Ortho4XP doesn't include a DEM (Digital Elevation Map) segment in the generated DSFs, which is what the synthetic vision needs to construct its terrain view (and also the GPWS and WXR read this to determine the terrain shape).
  4. skiselkov

    Plugin problem (Linux)

    I believe I've got this understood and figured out. It seems to be a libstdc++ incompatibility between Ubuntu (which I build & test on) and Debian. Fix is on the way to the reporter to verify the problem has been addressed.
  5. Below is a list of simulator performance test data of users. See below for the test methodology and raw data tables. Disclaimer: This data is provided as-is with ZERO warranty as to its reliability or accuracy. Hot Start does NOT guarantee that simply because your system matches the specifications below you will necessarily see the same framerates. This data is submitted by volunteer testers and hasn't been controlled for extra variables such as running background tasks, hardware cooling performance or slight variability in OS versions and driver versions/settings. Formatted graphic: Test methodology: Apply following graphics settings (if you move the sliders in your sim, be sure to restart the simulator, as certain settings are only applied on a full simulator restart): Load aircraft at SCIP runway 10, default cockpit view (SHIFT+9), cold & dark Set weather: CAVOK Number of AI aircraft: 0 Disable any extra plugins besides the TBM900, Gizmo, OpenWXR and OpenGPWS (these are required to run the airplane) Report the following data: Your hardware configuration: CPU + frequency (if overclocked), RAM, GPU + frequency (if overclocked), screen resolution used Operating system + version and/or patch level X-Plane version TBM-900 version TBM-900 FPS If possible, for comparison, default Cessna 172 (steam gauge variant) FPS for comparison Raw data: TBM900_fps.ods
  6. skiselkov

    What framerates are you seeing on the TBM900?

    Thank you @giaco and @Ricardo Pallavidino!
  7. skiselkov

    TBM 900 v1.1.1 Update Released!

    If you are running on XP11.30b5, then that's an issue that got introduced in beta 5. They changed the way monitor coordinates are represented, which confuses the sidebar window positioning code. Waiting on their response to see if they'll revert it back to the old behavior, or we'll simply have to re-implement that piece for XP11.30 and later.
  8. skiselkov

    X-Plane crash log

    This seems to have been a crash in the underlying X-Plane avionics code when it was constructing the STAR. The Log doesn't contain any stack frames from our code, so this likely wasn't caused by us.
  9. skiselkov

    Help with ILS approach

    @Pawel D. Very nicely explained. I'll just add that for LOC-only approaches, you wouldn't use APR, only "NAV". "NAV" is basically the roll mode, "APR" in addition also arms the GS pitch mode. So for localizer-only approaches, only use "NAV" and leave "APR" off. Little trick for achieving a constant-angle descent on a non-precision approach: Stabilize your airspeed. De-select any active pitch mode (e.g. when in VS, push the "VS" key again to de-activate the mode). This reverts the aircraft into pitch-hold mode. Use the UP<-->DN scroll wheel on the AP panel to manually adjust the pitch the autopilot will hold. Fine tune the pitch until the green FPV marker sits over the desired glidepath angle.
  10. skiselkov

    Before starting engine checklist?

    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.
  11. skiselkov

    Left hand side menu

    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.
  12. skiselkov

    Sidebar TBM900 does not appear

    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.
  13. skiselkov

    TBM 900 v1.1 Update Released!

    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.
  14. Folks, as promised, below is attached a CSL that's usable for showing other people's TBMs. Includes full animations on all flight controls, landing gear, lights. And it's PBRed to top it all off and highly framerate optimized. TBM900.zip
  15. skiselkov

    TBM 900 v1.1 Update Released!

    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.
  16. skiselkov

    very small checklist bug (and others)

    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.
  17. skiselkov

    Enter Holds

    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:
  18. skiselkov

    FSGRW and icing

    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.
  19. skiselkov

    VOR/DME distance limit?

    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).
  20. skiselkov

    VOR/DME distance limit?

    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:
  21. skiselkov

    key bindings fms and range

    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.
  22. skiselkov

    Unplayable framerates when panning camera around

    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).
  23. skiselkov

    [SOLVED] No Plugin Loaded (Linux)

    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.
  24. skiselkov

    TBM 900 v1.1 Update Released!

    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.
  25. skiselkov

    TBM 900 v1.1 Update Released!

    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.