skiselkov

In that case please check in the maintenance manager that the beacon lights haven't broken.

If you have no issues, then you're all set. For those that don't have it working, all you need to do is install the X-Plane global scenery from the X-Plane installer (choose add/remove scenery and select the regions you want to fly, then install it and you're all set).

The airport database currently filters out airports that do not have ICAO identifiers (such as "33V"). I will look into adding support for non-ICAO airports into the airport database constructor in the next updates. Not quite. The terrain loader does look through custom scenery, but it requires DSFs that contain a DEM block (Digital Elevation Map). The stock Laminar-provided mesh contains those, as do all of the HD Mesh packages by alpilotx. Unfortunately, Ortho4XP builds non-conformat DSFs which lack the DEM block and therefore the TAWS terrain loader in the TBM can't use them. The trivial solution is to install the underlying stock Laminar mesh. It won't replace your existing ortho scenery, it just allows the TAWS to read the terrain elevation data. In the future we will look at supporting non-DEM DSFs as well, although this is rather low priority (when I asked Laminar about whether non-DEM DSFs are good, their response was something to the effect that those DSFs will stop working once XP12 comes out, because it will require the DEM data as well).

You can just quit the sim with the engine running and next time you load (make sure you have "start with engines running" checked in X-Plane), the engine will still be running. So the airplane does allow for it for quick testing.

We will experiment a little with modern style window integration in the UI toolkit. Unfortunately, the beautiful and scalable modern X-Plane 11 UI is inaccessible to addon developers. So we either each have to write our own mutually-inconsistent implementations and keep redoing the same work over and over; or use the old-style widgets. Rest assured, I have tried pushing Laminar to give us an API, but they just refuse and have no plan to move forward in that department. In a distant future update we will probably have to just rewrite all the UI code using a custom scalable UI library. But for the 1.1 update that will be coming soon, we will probably simply perform dumb window scaling using some window management trickery. Rest assured, this IS on our radar and we're keenly aware this is an issue for users of high-res screens and VR.

We will be adding a Cold & Dark option to the "Flight Recovery" screen in a 1.1 update. This means that if you interrupted your flight, or the simulator crashed, you can still restart the flight cold & dark and fresh. However, if you landed and parked the aircraft, you will be forced to properly shut the aircraft down, just as in real life. We're trying to make our simulation both a study tool (and in real life you need to do these boring but necessary procedures) and at the same time a fun experience (so if a sim crash occurs, we don't want to penalize you for it). We believe the Cold & Dark option on flight recovery will be sufficient to cover all the cases where we see our current system as having shortcomings.

I apologize, but radio minimums are currently not simulated. Feel free to use the keypad digital entry to punch in a baro minimum quickly (you only need to enter the leading digits, the value is automatically entered in 10s of feet).

This was redesigned to allow the throttle to be used using only the mouse even in the normal thrust range. The reason for this is usability with VR controllers. VR users have been requesting controller-only support, so this was a compromise with them. The throttle is now split into two halves, the left half moves the throttle in the thrust range and the right half can be used to move it back into feather. Whenever in doubt or when you're having trouble identify where a clickspot is located, you can always just make the clickspots visible by selecting View > Show Instrument Click Regions from the simulator menu:

This is a bug in the simulator and there's really not much we can do to fix this. Please report this bug to Laminar at: http://dev.x-plane.com/support/bugreport.html Be sure to include the full Log with the report, as it contains a clear backtrace that traces the crash to a portion of the internal G1000 code: AIRNAV4::Geometry::StereographicProjection::convertLatLonToXY(AIRNAV4::Navigation::LatLonPair const&, AIRNAV4::Geometry::Point2&, bool) const Just FYI: the point is YULEE not YULLE. I tried inserting this exact route in Linux on the TBM in X-Plane 11.26 and couldn't reproduce the crash. So it might be something specific to your OS or simulator setup. Of other aircraft you mentioned, none of them use the Laminar G1000 avionics underneath (even the Carenado one uses a custom G1000 implementation). Can you please test this on the Laminar Cessna 172 /w G1000 and see if you can get that to crash? If yes, please report the bug to Laminar with the Cessna 172, so they can clearly see it's a bug in their avionics and not in the Hot Start TBM 900. Thank you for reporting this!

Not sure what you mean, they're still very much there for me. Are you sure you're not just moving your view outside using the internal cockpit camera? External lights are not rendered in that view. Make sure you are using one of the exterior views available via the View > Change (External) menu:

There isn't one. Those lights come on automatically as soon as electrical power is applied to the avionics.

That is a known issue, we're working to resolve it.

The next project will be .... [censored]. Don't worry folks, we'll announce the next project as soon as we have something to show you. At this point, it's all just a bunch of ideas floating in our heads. Besides, like @Goran_M said, we need to catch our breath and collect our minds before we dive back into development mode. Until then, please fly the doors off that TBM! Nothing brings us more joy than seeing you guys have fun with it!

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

Hello. Sorry to hear it's giving you trouble. Can you please verify that the screens work in the 3D cockpit? Also, are you by any chance running a multi-monitor setup with an ultra-wide monitor and/or running X-Plane on a monitor that Windows thinks ISN'T the main monitor? We've observed some users having issues when running X-Plane in full-screen mode on these kinds of display setups. As a temporary workaround, running windowed mode might work. Naturally we'll try to get it to work in fullscreen mode, so this is meant merely as a suggestion to get you up and running to satisfaction until we get this bug ironed out.

Ah now that's a mistake in the manual we gotta fix Thanks for pointing that out and for reading the guide! You're one of the few that did.

Can you provide a reference to this quote please? The manuals I have say quite a different thing.

It's stored under the X-Plane/Output/TBM900/state folder. If you just delete that state folder, that'll complete rest the aircraft to a "factory" install.

The two light clusters above the pilot and copilot are the cockpit lights, not cabin lights. Those can be turned on at any time. The CABIN switch affects the list aft of that (8 lights in 4 pairs).

Known issue. We're aware and will fix it. The CABIN light switch turns the cabin lights off. It doesn't turn them on. You need to press the appropriate pushbutton on each light to turn it on. The cockpit lights can be turned on without turning on the CABIN light switch. Known compatibility issue. XP11.30 is hot in beta, so expect issues. The LDG position of the landing lights position is higher priority than the PULSE system. To see the pulsing lights, the landing lights must be selected to a position other than LDG.

Can you please provide a screenshot of the PFD and MFD to see what atmospheric conditions you were in at that flight. Also, top airspeed will depend on component wear. Please attach your airframe state file, so we can take a look at the wear. The airframe file is located under Output/TBM900/state and has an ".aiframe" suffix.

If you have a saitek switch panel (or similar), make sure your avionics switch is ON. Something is preventing the avionics from coming up properly. Also, if possible, please test with plugins in Resources/plugins removed (except for Gizmo) and check if the issue persists.

Please use sim/autopilot/take_off_go_around (Autopilot take-off go-around).

Yep, this one looks like Gizmo acting up. I'll notify the relevant people of this. Does this happen on every license refresh for you? On the right edge of your screen is a little sidebar window with Gizmo controls. If you click on the lightning bolt (labeled X-Aviation Licensing) and click to update the licenses, does it crash? If so, we could try to trace this down.

Can you please attach a Log for such a flight?