xpst

Hi Gregg, thanks for that explanation! I gave it a try with the TBM. Of course you do always need to activate the approach at some point. That's a normal step you generally do not take too early just in case there are last minute changes (ATC, etc). Because of those left turns, I did it just before POKKR, and despite the sharp turn the TBM turned to PRINO and followed the approach. Then the glideslope became active so normally you don't need vnav mode any more. But I couldn't get the AP to use the GP and flew down by hand too . That may be because the arrival is plain RNAV and the approach is ILS/LOC so I needed to switch over. I'm not sure, and I need to do a few more tries. I'm still learning, so this may not make sense. I also need to figure out how to update my X-Plane/TBM nav database. My approaches, arrivals and runways aren't up to date at all (SUNST3, ILS25L) although they're close. BTW that runway is endless !

Hi Goran, I didn't know that, I always do it through the maintenance manager. I tried the walkaround now, and touching doesn't do anything... I'm sure I don't have the right touch ?

A question on top of yours, Gregg: do you know for sure that the real G1000 does it automatically in all cases ? Also, do you mean "Direct To, Activate the Approach or vector..." or "Direct To, or Activate the Approach, or vector..." ? Just asking because I sometimes experience the sequencing stopping and I haven't been able to figure out why yet . Looking through the docs and videos hasn't provided an answer yet.

I definitely still see OBS in 1.1.7. Maybe the mode you were in at this time does not allow OBS ?

> Settings and change Reflection Detail from minimal to low, Ghislain found it. Same for me, and minimal fixes the problem on my "original" installation too.

I expected you would ask me to remove all plugins ... OK, I did it, only Gizmo and TBM left, unfortunately no change. I can live without the AoA thingy. But 1.1.7 definitely broke it, this didn't happen before. Log.txt (yes Goran, the yellow circle is added by the video recorder)

Yes, no change with 419.35 driver for me either. OpenGL Vendor : NVIDIA Corporation OpenGL Render : GeForce GTX 1060/PCIe/SSE2 OpenGL Version : 4.6.0 NVIDIA 419.35 (460/0) With power on this time, side/menu bars flash in sync with AoA device. Outside is OK : 41935 117flashing.mp4

Log.txt attached with video now.

Here is a video, hope it works... I'm on W10, GTX 1060. 117flashing.mp4 Log.txt

1.1.7: This side/menu bar flashing phenomenon starts when AoA device is on/up and stops when it's is off/down (for me at least).

Yeah, I'm testing on a BIG runway too. After a few more landings and analysis of the replays... watching the way the plane behaved when landing... it looked there was much more lift than I would expect in a real plane, which is why it's so hard to put down. But I was alone in the plane, with little fuel. Taking on a full load of BIG passengers, copilot, cargo and a lot of fuel, and landing went as stevo1kinevo would do it . Another try in a very light plane, taking off and landing, with no flaps felt easier too. But that's probably not realistic. Maybe I'll understand how it works in the end.

Sure RobW05, I read all those posts and they help. I like the Hot Start TBM a lot. It's a great plane. Glad you've got it under control. I know all planes in real life or in sims have their quirks which you need to learn about and practice, practice, and practice. And I do. And there are factors such as PC hardware, X-plane settings, personal perception of things, ways planes are implemented, and many others. So before making any remarks, I did a lot of testing and my personal perception is that before 1.1.6 my TBM landings were a lot easier to succeed. Then I compared to other planes, and my experience (in for example the Epic 1000 which is a comparable beast, but others too) is that the simulation is a lot smoother in most other planes, which make the landing unrealistically difficult in the TBM. Again, the TBM is great, I'm sure it wil become even more fun.

> The latest update (1.1.6) has improved ground handling. I've said it before, yes, it's better (except that now it's harder to land than before). In my opinion, handling is still not good. I've been doing a lot of tests with other planes, smaller/slower or larger/faster, and including the Epic1000 G1000 to do comparisons. I continue to find that the TBM handling just can not be considered "normal" while landing, when sim timing is probably most critical. The response to trim inputs for example, is visibly much faster and smoother on other planes. So there is probably also too much delay in the other controls, including throttle and braking, which is why landing, toe braking, steering on the ground still makes you look drunk and uncoordinated (well, me at least). Sorry to say, no way I'm going to be able to do Steveo1kinevo-like landings if Hot Start doesn't do more optimization/tuning :-) Phew, new airframes are for free ... ;-)

Hi Goran, To help bump this up : yet another "Something reinstalled our exception handler, replaced it with 0000000000000000". In 1.1.6 I experienced one before on the tarmac, this time during landing. And I previously had several others with 1.1.4x. I have the feeling they don't help, but I attached one more log.txt. I really hope you can find why this problem occurs. I don't think I repeat some action in particular when the CTDs occur, it seems quite random. As I already said before, I only have XPUIPC/XPWideFS and the TB900 plugins. Only standard laminar scenery. Log.txt

Some feedback on 1.1.6. I've been flying around quite a bit to try it out since yesterday. - Unless I'm imagining things, driving it around the airport seems easier, and I'm able to balance toe braking a lot better without swerving as much as before. - I had one "exception handler , replaced it with 0000000000000000" CTD on the taxiway a few minutes after starting up. Just about in the same spot as one of the previous ones I had but that's probably a coincidence. - I've just been doing a lot of test landings, and to me they definitely seem much harder to succeed correctly. My landings weren't beautiful, but now they're horrible even at the airport I've landed on relatively easily with the TBM many times before. Anyone else have this impression ? Or is it just that my flying got even worse this weekend ? (This is probably a very embarrassing post ;-) )

Aaarg, there it is. And now I see it in the manual too. Thank you !

Hmmm, I looked at all my G1000 docs (X-plane, Gamin, and Socata !), but in the sim I can't get the calculation to display. How do you see it ? (Note, I was on the ground, engine off, that may be wrong) Thanks for any hints... !

I had this a few times in the beginning too. I changed or recharged (don't remember) the battery. Never had the problem since then, so make sure the battery is full enough, or use a GPU.

@shinjo: > Unfortunately the TBM 900 has a unique throttle mechanism that doesn't really match up 1:1 with what we have in the sim world. Flipping switches to set idle statuses may be immersion breaking but I don't know of a way around it unless you 3D print a custom throttle quadrant. Yeah... I use a yoke left handed and a Thrustmaster TWCS throttle right handed to make things as real as I can. Using the TWCS right handed is not really what it's designed for but it's great for the TBM 900. I assign the up button as flight idle lockout lever for going to taxi/reverse, and two buttons for moving the throttle from flight idle <-> high idle <-> low idle <-> cutoff . Works out really well.

> The toggle switch on the left side of the throttle is the beta switch in the TBM assignments, to cycle from flight to taxi/reverse mode. Hi DwightP980. Unless I misunderstand you: the switch on the left side is actually the TOGA button. To go into Taxi/Reverse, there's a flight idle lockout lever in front of the throttle to lift the lever back over a gate. To simulate that, assign a button to "sim/engines/thrust_reverse_toggle". With 3 buttons, set to "sim/engines/mixture_up", "sim/engines/mixture_down" and "sim/engines/thrust_reverse_toggle", it all works really well to power the engine up/down and to taxi/reverse thrust.

Hi Goran, FYI, as you suggested on Saturday, I removed all AI planes to see if that helps. Unfortunately, I just had the "TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000" again, a few instants after powering up. I only have one add-on plugin : XPUIPC/XPWideClient.

Sure, done. Removed all plugins (I only had one, and FWIW, never had FlywithLUA). Then I set set gear/comp/3/brake_disc/wear = 1.000000000000000 in the airframe state file (which is what you get if you wear it down), and got the crash as soon as I clicked on maintenance manager -> landing gear. Log.txt

Hi Goran ! > details about the flight before the crash The "flight" was fine. I killed a brake during my braking "training" on the ground (I got myself some rudder pedals, but I just can't manage to apply equal pressure on the pedals when landing, and keep having to pay for repairing the grass). This plane is costing me. A lot. The brake failed pretty fast, I'm not sure how realistic that is, but then the plane simulated the failed brake perfectly (swerving to the correct side, etc.). For me it's easy to reproduce : 1) either kill a disc by blocking your airport for 15 minutes, powering up to 90 knots and braking, powering up and braking, etc. or set gear/comp/3/brake_disc/wear = 1.000000000000000 in the airframe state file and start X-Plane. 2) Go into maintenance manager -> landing gear

I get a crash which looks like a maintenance manager bug when handling a worn brake disc state. (I was testing my toe braking skills by zipping up and down a long airfield, and finally killed a disc). Now, as soon as I go into maintenance manager -> landing gear, X-Plane crashes with : 2019-02-19 22:45:28 TBM900[fail.c:932]: Component right gear brake disc has failed due to excessive wear (worn: 100.000000%, slope 1.0). You can prevent this by observing performance limitations and servicing the aircraft regularly in the maintenance hangar. 2019-02-19 22:45:28 TBM900[fail.c:935]: Failure impact: sim/operation/failures/rel_rbrakes 2019-02-19 22:46:15 TBM900[maint.c:2039]: assertion "fail->fail_name != ((void *)0)" failed: Workaround which worked for me : I set airframe state file value gear/comp/3(or /2)/brake_disc/wear value to < 1.0, then maintenance manager access worked again, and I could pay $$$ for fixes. Log.txt

> ... if you have AI, to get rid of it and that CTD no longer happens. OK, I have deleted the three AI planes that were there by default, to see what happens. Thanks Goran !