DwightP980

@LKN I ran across something similar yesterday, but it happened about five hours before updating to v1.1.6 and it was all my aircraft logs which I suddenly noticed were gone. The only log entry I had was for the flight I had just finished and I suspect it was some issue with X-Plane rather than the TBM loading. I back up my X-Plane to portable hard drives about every two days, so I had a fairly up to date Output folder with all log book copies saved, and it was not that big a hassle to get everything back up and current. Anyways, as I said may be completely unrelated, this was well before updating to v1.1.6 Blue skies to you, Dwight

@Barton W. I updated to v1.1.6 a couple hours ago and flew from KPGD to KMIA with no problems. I was very happy that the Charts are back in the MFD, and I gave my TBM a pretty good workout with no failures of any systems during the flight, and I was also able to setup a VNAV profile using a STAR to KMIA after flying the VOR inbound to KPBI ,and ILS approach to 26L at KMIA. All my altitude assignments I set were spot on, on both the climb to altitude and the descent profiles I loaded were followed with no problem. As far as the ground handling problems you speak of, try the following which I posted in another posting and it will likely help you tame the beast, which is now absolutely a pleasure to taxi and take-off in, 1. Power the TBM-900 up. 2. Turn the Auto-Pilot On (switch located the overhead panel righthand side) 3. As soon as the PFD's and MFD have powered up go to the TRIM section of the MFD (lower left corner) and move the RUD trim to the center (white tick mark) and the ELEV to the T/O white tick mark. 4. Toggle the Beta Prop switch located under the Power lever on the left side to enter Reverse and the Taxi power range. 5. When you have aligned with the runway for Take Off bring the power up to 40% - 50% prop torque indicated (or very close) stabilize power and on the takeoff roll easy power to takeoff power. By playing with the above settings my TBM is very much so controllable for Take Offs and Taxi. My preference for the Control Sensitivity for my controls are set to 50% for both Control Response and Stability Augmentation. The RUD trim (#3 Step) is likely the biggest culprit as I was lining the tick mark up with the BLUE mark. Mine handles best when trimmed to just touching the right side of the WHITE mark. Your mileage may very as they say The only issue I have is listed as: Something reinstalled our exception handler, replaced it with 0000000000000000 which I have determined is due to a file by the name of X-Life Traffic by JARDesign Ver.2.2 and would likely go away if I were to remove this file which provides airport scenery and live traffic. I will also attach three files which you will find in your X-Plane folder, and if you post with a bug or problem may help in the diagnosis of it. Regards, Dwight GizmoLog.txt Log.txt TBM900_Log.txt

@RobW05 Thank you sir! I will go ahead and update, as I've backed everything up and should be good to go. I kind of thought the issues may of been with the MAC's and Linux, maybe even Steam systems. I do hope you submit for reimbursement to Daher-Socata for the mechanics labor if any Blue skies to you! Dwight

@Fabbi Thanks for the update! I haven't tried the v1.1.6 up date as it looks as many people have reported issues so far. Most are saying it doesn't work, but their not bothering to attach gizmo, log, TBM900_log files so I'm not sure as to what type systems might have the issue. Starting to see a few report it's working so I'll hope my Windows 64-bit, i7700 Intel works. I've backed everything up, and can always fall back. Regards, Dwight

@Jalio You are welcome! My thought is the ferry pilot that delivered our TBM's failed to observe the V-LO and V-LE published speeds and caused to loss of the gear cover on one of the delivery legs. Well, that's my story and I'm sticking to it Regards, Dwight

@Jalio You are correct it does not look correct, and it was reported back on February 10th just prior to the last update in a earlier posting on this site. This should be corrected in a later update according to the developers, but for the time being it is more of a visual issue than a performance issue. Blue skies to you! Dwight

@TimC Hello Tim, Glad to hear the tips are working, and with the more time you put into this aircraft, the payoff will be immense. By the way, I see you are flying circuits at KMCO. This is home base for my TBM (I always park around the Signature ramp area) and I normally fly from KMCO to KLAL, KTPA, KSRQ, KRSW, KMIA. After downloading some custom scenery, and airports, spending some time watching YouTube on how to setup the custom scenery files X-Plane, it is awesome. Blue skies to you! Regards, Dwight

@Raylemus Ray, are you still having this issue? I don't own RealScenery Florida, but have l ran across this same issue when installing other scenery and it was due to the order the files are laid out in the X-Plane 11 > Custom Scenery > scenery_packs.ini file. If it's still an issue for you let me know and I may be able to help. Regards, Dwight

@Shinjo 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.

@cforker Hello Chris, I have read your posting with interest, as I've been on the fence about purchasing FS Global Real Weather, however I haven't pressed the Buy key just yet. A little while ago I watched the embedded video from Q8 Pilot on YouTube and starting around 10:10 is were he really starts getting into FSGRW and it's operation. For your flights how long would you say it takes to set-up and download for a trip? The graphics to me are hands down better than the stock weather generator in XP-11 but the trade off may be the set-up and loading time. I also learned a lot about the different weather functions, and of interest to me was the part dealing with the weather 'blocks'. Thanks! Regards, Dwight

@rafgath What are the hours that show on the new airframe? I just tried creating a new airframe and it showed about 20.1 hours. My thought would be if I bought a new aircraft the aircraft would have logged time before I took delivery of it. It would show accumulated hours for testing, ferry, and any other checkout required prior to my taking delivery of the aircraft. Just my thoughts!

@TimC Try the following: 1. Power the TBM-900 up. 2. Turn the Auto-Pilot On (switch located the overhead panel righthand side) 3. As soon as the PFD's and MFD have powered up go to the TRIM section of the MFD (lower left corner) and move the RUD trim to the center (white tick mark) and the ELEV to the T/O white tick mark. 4. Toggle the Beta Prop switch located under the Power lever on the left side to enter Reverse and the Taxi power range. 5. When you have aligned with the runway for Take Off bring the power up to 40% prop torque indicated (or very close) stabilize power and on the takeoff roll easy power to takeoff power. By playing with the above settings my TBM is very much so controllable for Take Offs and Taxi. My preference for the Control Sensitivity for my controls are set to 50% for both Control Response and Stability Augmentation. The RUD trim (#3 Step) is likely the biggest culprit as I was lining the tick mark up with the BLUE mark. Mine handles best when trimmed to just touching the right side of the WHITE mark. Your mileage may very as they say ;-) Regards! Dwight

@Goran_M I removed all plugins as requested, and all is fine until selecting Landing Gear in the MM. All Tabs will open i.e.. Engine, Electrical, Avionics, etc. but when Landing Gear is selected the CTD occurs. Have duplicated many times. Updated Logs attached. Log.txt TBM900_Log.txt

Hello @Goran_M! Okay, so this morning I read the postings for this CTD, and in the back of my mind said I might give this a try. Of note since the latest revision to the TBM-900 I have not had any type of failure. I flew a local flight at KMCO, shot and missed an ILS approach, and reshot the approach and landed on 18L. On roll-out I decided to add power, go to approx. 90 knots and abort take-off with hard braking. After two aborts I got the warning to delay TA for 15 minutes. One or two more aborts with hard braking created a warning to delay TA for 45 minutes. I then taxied to the ramp, with extremely poor braking (expected condition), parked the aircraft, and shut down the engine to do a inspection and see what the maintenance manager might say (I expected to shell out a couple hundred bucks for this abuse of my beloved TBM ;-) On attempting to open the MM I then experienced the CTB as @xpst described. I reopened X-Plane and selecting either Yes or No when the splash screen for Flight Recovery opens still leads to the CTD. Attached are my Log files and perhaps they may help you. I do not see this as a major problem as I really had to work at creating the failure, and will reload if necessary to continue my adventures with the TBM. Regards, Dwight Log.txt TBM900_Log.txt

@Rhinozherous Hello! Try the following as it is what did the trick for me: 1. Power the TBM-900 up. 2. Turn the Auto-Pilot On (switch located the overhead panel righthand side) 3. As soon as the PFD's and MFD have powered up go to the TRIM section of the MFD (lower left corner) and move the RUD trim to the center (white tick mark) and the ELEV to the T/O white tick mark. 4. Toggle the Beta Prop switch located under the Power lever on the left side to enter Reverse and the Taxi power range. By playing with the above settings my TBM is very much so controllable for Take Offs and Taxi. My preference for the Control Sensitivity for my controls are set to 50% for both Control Response and Stability Augmentation. The RUD trim is likely the biggest culprit as I was lining the tick mark up with the BLUE mark. Mine handles best when trimmed to just touching the right side of the WHITE mark. Your mileage may very as they say ;-) Regards! Edit: Also when you have aligned with the runway for Take Off bring the power up to 40% prop torque indicated (or very close) stabilize power and on the takeoff roll easy power to takeoff power.

Plus 1 vote for Shift+Wheel, if it can happen :-)

Thanks for the revision, and all the hard work guys! Everything appears to be working fine on my system, and I have made a backup copy of XP-11.31 so if I lose my mind in the future, and go to update X-Plane to 11.3x.x before waiting a week, and checking out possible problems that may be incurred with my TBM-900, I can go back to a stable build. Lesson learned!

@nboggs70 & @GliderPilot The problem your having is being addressed by the TBM-900 developer's, and an update is in the works and said to be a day or so out. If you want to fly in the meantime, follow the instructions as listed below: 1. Open X-Plane 11 and select a GA aircraft such as the Cessna C-172 / G1000 2. Open the FPL and clear any flight plan, or procedure shown. You should then only have the airport identifier shown for the current location i.e. Orlando, FL KMCO 3. Close the C172 /G1000. 4. Open the TBM-900 and you should be able to fly. 5. Some people have been able to load a flight plan/procedures into the C172 /G1000 and after closing have the TBM now loaded with that flight plan not CTD (Crash To Desktop). 6. Any entry made to the G1000 will likely cause the CTD when the ENT key is pressed to activate in the TBM-900. This has happened to me repeatedly since the XP 11.31 update. 7. If this works for you, go fly, have fun! It works for me and you only have to open the C172 /G1000 once provided you don't mess with the ENT key on either the PFD or MFD. For more info check out the Hotstart Forum for TBM900 Support. As I said support is actively working this issue. Good luck!

@oldflyguy Ken, thanks for the feedback! I have no doubt you experienced the problem you had, and I'm scratching my head as to what could cause such a random deviation. One thought I had was did you check the Avionics in the Maintenance Manager? Perhaps a failing component. I have started taking a look prior to each flight even on short legs at the Maintenance Manager, as in the past I've had issues pop up that I did not notice while in flight, such as a leaking left fuel tank which on prefight I found about 50 gallons of fuel had disappeared (maybe one of those ramp vehicles running around the airport tagged me, lol) and I had to repair for $22,500. I know the developers must be pulling their hair out, as it seems XP-11.31 created issues that seem to have caused havoc with the G1000 and likely it seems other systems. The TBM for me is still very flyable and I've just decided to dust off some long time not used navigation methods. Sure wish they had GPS, and all the avionics the have today back when I was actually flying. When it works it spoils you ;-) Blue Skies, Dwight

@oldguy Sir, I read your post not long after arriving at Renton, WA- KRNT. I thought I had read your post carefully so, opened X-Plane turned the weather generator off, so I'd have clear skies and visually be able to see the VORTAC building as I overflew the station at Sea-Tac Airport at Seattle, WA - KSEA, hopped back in the TBM motored the engine long enough to lower ITT to start and taxied to runway 34. Test 1: I set the VOR CRS1 to the Seattle VORTAC on Channel 116.80 and selected the 160° TO radial. I flew the runway heading 340° using the HEADING mode till reaching 3,000 msl. I then turned back towards the 160° radial and when the CDI started to move engaged the NAV mode with VOR1 selected. The CDI never perfectly centered, but was never more than 5° off and letting the Auto-Pilot control the aircraft flew me directly over the station with the CDI showing the normal wall to wall defection that would be expected passing over the station. I then flew south approximately 30 miles on the 160° heading (still flying away from the station) did a 30° right turn flew outbound for 60 seconds and then a 180° left turn. Set the CRS1 to 340° TO heading and again back over the VORTAC. About 5 miles off the 34R runway I did a 180° turn back to the field selecting the 160° radial on the CRS1 deciding to land on 16C and the CDI showed what I expected to see which was a deviation to the right of course. I then did what I likely wouldn't do if given the chance to actually fly a real TBM-900, which was just short of the thresh hold for 16C I side stepped over to 16L which the CDI then indicated I was to the left of 160° radial. At that point I landed. Now, after going back and re-reading your post what I failed to do was load a C172 and set it up first and then compare to the TBM. I had loaded the TBM set everything up in the TBM and flew the course and had results that I would expect to see if flying a real TBM with G1000, which again I've never done. Test 2: So, I just loaded the C172 / G1000 on the ramp at KSEA. From my location the Direct TO shows Bearing 253° CRS 253° and DIS .2nm on the screen and when I center the CDI I show 249° CRS. I then loaded the TBM at exactly the same location and the results are Direct TO Bearing 259° CRS 259° DIS .2nm, and when I center the CDI it's at 255° Looks like to me, and I'm no expert, that the Cessna 172 was a 4° difference from the Direct To the CDI indication, and the TBM has a 4° difference as well. I'm not sure what the allowable difference is or if this is an error but the maximum difference I show between both aircraft on my system is 4° Not sure why your system show such a large deviation between aircraft, but for mine I'm good with the results for the time being. Still can't wait till the fix is out to get back to the pre-CTD days, but for the time being I'm still flying. Test 3: Thinking about this over a cup of coffee this morning I thought perhaps the distance from the VOR station may have some bearing on the accuracy. I relocated the TBM back to KRNT and with the aircraft running on the ramp at the location I parked showed the needle centered with 211° TO the VOR and the Direct To showed Bearing 214° CRS 214° and 5.1nm. The C-172 / G1000 when parked at the same spot showed exactly the same information as the TBM. BTW, I'm using a Windows 10 64-bit desktop system, I7-7700 CPU @4.20 Ghz, w/ 16GB Ram, Nvidia GeForce GTX1070 8 MB X=Plane 11.31 and TBM 1.1.4B. I see a lot of remarks about people using STEAM and I don't know if it all plays the same as a PC based system. Regards, Dwight

Your welcome Bill! For me I leave the FPL blank, and have gone back to flying the TBM-900 the way I flew most of the real aircraft I flew back in the 70's and 80's and that was by VOR, and I'm loving it. I will try loading a leg per your method, and continue on with my great adventure across the United States.

@dcowsill The trick for me was open X-Plane 11, selected the C172 w/G1000, battery on, avionics Master on. I then selected the FPL on the PFD, selected the field shown in the FPL, and hit the CLR button followed by the ENT button. After clearing the previous flight plan of all data it now showed KLAX which is the location the TBM went CTD, and was the same location I selected to open the C172. Reopened the TBM, hit the FPL button and the only entry now showed KLAX. At that point as I stated before don't enter a flight plan, or any other data into the FPL page. Since using this procedure I have flown from KLAX to currently KLLR in CA. with four stops along the way and no problem with CTD's. Touch the FPL, enter data, hit ENT and it will CTD. Your mileage may very, but for me it works!

@JYW If you haven't already found this in the previous posts, make sure you DO NOT enter a Flight Plan or touch the ENT button. I have been flying no problem with the current issues provided you don't mess with the FLT or ENT buttons. And it doesn't matter if you are doing this through the PFD or MFD, touch the buttons and you will CTD. I'm having no trouble flying or with any system until inputting a flight plan entry or location input, and pushing the ENT button. It's not ideal, but it should get you flying.

@MD111977 I notice you say that when the TBM-900 does load that "its on fire with smashed windows sitting on its tail". I too had the same problem back in the beginning which after reading through the forums I found the fix to be this: Go to your X-Plane11 file folder and open it. Now the Output folder and open it. Inside the Output folder you will find a folder named TBM900. Click on the TBM900 folder and you will now find a folder named state delete the state folder and all of it's contents. It will now reset the aircraft and no more fire, cracked windows or crashed airplane, unless we get careless again ;-) As far as the rest of your statement, me personally I love the TBM-900! Now with that being said I purchased X-Plane 11 back on June 8, 2017 and it like any other software I've purchased since 1985 when I started buying software ,was not perfect and has been revised many times since my purchase. Since buying X-Plane I have added over $350(US) dollars in aircraft an add-ons, which most have worked great most of the time, but not all the time. My purchase of the TBM-900 was on Dec. 13, 2018 at a price of $64.95(US). I spent almost two weeks reading threads about the TBM-900 before making my purchase. Is the TBM-900 perfect at this moment? No! Has it worked and performed better than any of my other purchased aircraft for almost all of the now 90+ hours I've flown it? Yes! I'm pretty sure that software developers produce the finest product they can before releasing it to the public, using a platform (operating systems and hardware) which meet the requirements to use in most current systems. Do they sometimes not play nice with other hardware or software? Yes! When that happens what do they do? Revise the product. Try removing the state folder, load the TBM, and don't load a flight plan, and whatever you do don't hit the ENT on the G1000. Have fun flying what you can with these limitations, and when this issue is resolved I'd almost bet the TBM-900 will be one of your favorite aircraft. Just my 2 cents....Regards!

@oldguy Right you are sir, as I just found out! Everything seemed fine until, I shut the XP down and reopened only to be back to square one (CTD failure). My 2 cents worth is, I think Laminar should provide a path when updating to fall back to a previous update or working point. As I said earlier today, it is a lesson learned for me. I sure don't blame the TBM team either, because I have to many hours flying the 900 with basically no issues, other than as you say trying to keep up with the moving Laminar target. So for the time being it looks like a two boot process, to fly the TBM-900 but you can bet I'll sure think twice, before I touch that update button so dog gone fast again.