oldflyguy

Hi @nrey001. Your main install is awash with plug-in's - both stand alone and contained in scenery. And you scenery order is also borked although this typically does not cause a crash. I would download a second "light" copy of XP (only one scenery area) and install the TBM into that copy. If there are no issues - and I don't believe there will be - you know that one or more (it is probably more than one) of your plug-in's is not playing well with the TBM. The folks here are able to explain why the TBM - a very complex model - may have issues with other 3rd party plug-in's. On the bright side I use a good many tried and true plug-in's along with complex scenery on my aging rig and have not had a crash with the TBM al least not that I remember. Full disclosure - in my mid 70's so the not remembering thing should be taken with a grain of salt.

I only use NOAA with XP10 (obvious reasons). It's ASXP for XP11. I would still download that virgin copy (I keep one on hand at all times) and try the TBM with Python (only) on that one. This path is absolutely the best way to troubleshoot in my (totally) non-expert opinion.

@MindyourstepI may have missed this but why don't you download a "light" copy of XP (just one scenery area) and install the TBM on that "untouched" copy to see what you get. That's the first thing I would have done after just a small taste of the troubles you are having.

@ChampguyThis aircraft does not go into "crash mode" right out of the box. Or hundreds of users would be posting here. There is something else at play and it's on your "side" of things. Why not attach a log.txt from a flight where this occurred and let some of the experts here (not me) have a look.

@tomangeIt is not possible to provide any meaningful assistance without more information. Please attach a log.txt file (found in the XP root folder) from a loading attempt where this occurred. It's a good place to start.

@RatnowNo worries. No need to download a whole new aircraft. Just make a new airframe and discard the one that crashed. All "in program" - easy peasy. I agree about the automation. The new models feature auto-throttle. Pretty soon they will include a dog that will bite us if we touch anything.

@RatnowWell, "stuff" happens...LOL! You will need to make a new airframe and start over again. Wiser now. Again...LOL! Been there, done that.

Yep! Can't use "trim" to adjust pitch when in autopilot.... No issue here when selecting Auto.

@hodasphHave you updated your TBM? What version are you using? Also, do you have HDR selected in the XP graphics settings? I don't know if this makes a difference - just thought it might be worth checking.

Sounds like some progress at least. I think at this point we will have to wait until @goran has a look at your attachments. By the way, please attach an updated log.txt from a recent attempt not that you have updated the video driver.

So, update. May not mean a thing but you should try...

That is the driver version... 30.0.100.9684 7/14/2021 Correct? Window doesn't necessarily provide the "latest" drivers.

@Thebestofalltime117 This is getting (way) above my paygrade. Have you tried to update the intel integrated gpu driver? You can find the driver on the intel website to download and the install process is easily googled. I don't know if this has anything to do with your issues but since it's mentioned in the log.txt you should probably address it. Also, FWIW please wait a while for the TBM to load in completely before attempting any action with it. This may take an additional moment or two. Pushing buttons, etc. may bork the process...

Please let us know if you are able to fully load the TBM with lower graphic settings. It may be of some help / interest to other users.

Hi @Thebestofalltime117! I am not expert at this stuff and did not want to step on anyone's toes but a quick look at the attached log.txt suggested a couple of issues at least... The is a problem with the video driver. I don't have any idea of what kind of video driver an integrated GPU uses but clearly there is a problem there that has nothing to do with XP or the TBM. Additionally, you have 12GB of RAM that is being shared between your CPU and GPU. That is not a good thing with an add-on like the TBM. Have you tried reducing the Texture setting a notch or two and seeing if the TBM will load completely? The CPU is also kind of slow. However, all things considered you probably should be able to run the TBM at low settings. How well I couldn't say. Again, the one item that stands out - and it's a big one - is the video driver issue. I would start there. Make sure the driver is up to date. Even if it is you may want to re-install it.

@ecallr I don't find that to be the case. Although atmospheric conditions and weight may differ I find an IAS of closer to 190+ (at times). Again, I urge you to download the TBM900 PIM. It's free and a great addition to your TBM model. Add the Garmin G1000 manual to that as well.

@ecallrDownload the TBM900 PIM. That will provide the correct information. You will find that your numbers match pretty well. Only jets will reach that IAS. TAS for the TBM at that altitude is around 300Kts depending upon conditions...

@ecallrI don't think there is any way the TBM could reach 260Kts IAS at FL300. The numbers you provide match my results fairly closely. Even the very poorly modeled TMB940 in MSFS can't do that...LOL! Bad example I know. Just couldn't resist.

I have no doubt that the takeoff trim in the upcoming CL650 will be spot on! Sorry, just couldn't resist...LOL!

Good point @Ben Russell. Always good practice to have that default install - one scenery area if storage is limited - handy to check things out.

@Thomas NguyenJust a comment from the peanut gallery here. It's one or more of your plug-in's. An alternative to installing a second "light" copy of XP (always a good practice anyway) you could just make a new folder in XP Resources and name it "plugin's_DISABLED". Then you would be able to simply and quickly move your 3rd party plug-in's to the new folder and see what you get at that point.

Hi @stevae! I honestly have no idea what you mean by this. I've "flown" the current model since release and although my RW experience is hundreds of hours in a C182Q (GA pickup truck) I would not look forward to one less thing to do while flying an aircraft. I also cannot see how anyone would have a problem with the current throttle simulation once they understood what is being simulated. If I've missed what you are aiming at please elaborate.

My C182Q was not certified for use above 14,000'. Or at least we couldn't get there with 4 passengers and luggage. Tried to go over the top of the KORD Bravo coming back from Oshkosh. Couldn't get there...LOL!

Yep, always used the old aviation flashlight (red or green) at night in real life. By the way, an aviation flashlight is an ordinary flashlight with the word "aviation" in front. That way, it's more expensive.

@Wyskass Did you set FL300 as your cruise at any point? Set the cruise alt so it displays in "blue". Or did you just set 14000 as your target alt? I've noticed over the years of flying the TBM (and other G1000 aircraft) that if you don't configure the flight plan in this way often you will experience exactly what you describe. Various TOD alerts. As the aircraft climbs and descends a bit at cruise. I don't pay them any mind as the ACTUAL TOD will appear at the proper time and all is well. Close enough to reality for me. Haven't you noticed this?