Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


oldflyguy last won the day on April 1

oldflyguy had the most liked content!

Community Reputation

46 Excellent

About oldflyguy

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @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?
  2. FWIW I haven't experienced any problem with or without SMP/RWC.
  3. Hi @F1le! The green trim position for the rudder is correct for the actual aircraft. However, use the center position - or just offset a bit to the right - for best control of the Hotstart model. A bit of trivia - the initial release of this model did require the rudder trim to be at or near the green mark. An adjustment to the flight model in a later version made that trim setting "incorrect".
  4. Hello @lorema! Just to make sure. You are setting climb with FLC and selecting the proper speed for each segment of the climb, correct? I've not experienced any hiccups with climb or descent with autopilot since initial release.
  5. @MindyourstepHi! Just a reminder that disabling plug-in's using the menu often has no effect on the plug in as it's already loaded. You have shut it off true, but conflicts may still occur. Better to move them out of the plug-in's folder to a temp folder you have created in Resources. Glad you got it sorted.
  6. @Tonfly74 I certainly don't want to step on @Goran_M's toes here but although I posses little expertise I think this is the way to go. You correctly removed all 3rd party plug-in's to a safe place then re-installed the TBM and it operated correctly. You should have added those plug-in's one at a time to find the one that is causing you this issue. Adding them all back together accomplishes nothing. Please try this. I know it's time consuming but worth the trouble. Understand there are some plug-in's that just will not work with a certain combination of aircraft models, scenery and other
  7. Yes, I would have expected some response by now. I did not see a log.txt attached to your posts - may have missed that. Why not attach one. The community may be able to offer some assistance.
  8. @Maverick51Hi! It is the weekend. I'm sure you will get a response to this. In the meantime why not post a log.txt from a flight where this occurs. Not that I'll be able to tell anything but it might help the community here solve your issue. While I do get different types of cloud types in the same area from time to time I never got the black effect in the 2nd shot.
  9. @jason74SMP/RWC may have that performance cost if you are using the new volumetric (not sure if that is the correct term) cloud art / high AA settings and/or a high res monitor. Have you tried 1 - the fast cumulus setting? 2 - turning down AA? SMP settings are completely adjustable and this app runs just fine on my creaky old rig. It could be you just have a lot settings - SMP and XP graphics - too high. Post a log.txt if you will so the experts (not me) here in the community are able to offer assistance.
  10. Sounds like icing. Or very heavy rain. In these conditions you should reduce power and engage the inertial separator. Definitely do not leave it off. This kind of procedural stuff aside have you tried removing all of those 3rd party plug-in's to a safe place? Then try a flight. You know the TBM model has a lot going on under the hood and it's possible there is a plug-in conflict. The latest version of the TBM has given us even better performance (resource wise) than the previous versions. So flying in heavy weather should not be such a performance killer. I don't know if you are using
  11. @garyhNot having the horsepower to effectively run the PT19 is one thing. And I think that can be addressed. However, not spending any real time figuring out how the various levers, switches and dials work is quite another. This model is not one you jump into and go fly somewhere. The entire preflight thing is a work of art. Enjoy it or don't but please do not rant about your inability to do so. If you would just take a breath and learn the model you would be much happier. And if I understand correctly, you are simply lacking in RAM. Not a big issue these days. Purchase more. It's ch
  12. @tbarry That's good news. Just be aware attaching a log.txt file might get you some answers from experts (that's not me by the way) as to why this is happening.
  13. HI @tbarry! So many possibilites. First please attach a log.txt (XP root folder) from a flight where this issue occurred. Next, specifics. What "cruising altitude"? Are you maintaining torque as you climb? Did you shut off the inertial seperator? Dumb questions, I know but you provided no information except that this happened. Have you checked the maintenance report after a flight (or before the next attempt?). Clearly, "everything wasn't good". Please start with the log.txt file and we will go from there...
  14. Hi @jarekp! Please take the following with a grain of salt. I claim no expertise in XP or with the TBM. I do have extensive hands on (user) experience with both of these. So here goes... The TBM is a complex model. There's a lot going on under the hood. This can be an issue with an XP installation that also has a "ton" of plug-in's (yours). I do think the solution is simple. Temporarily remove all 3rd party plug-in's to a safe place. I use a "plugins_DISABLED" folder in my Resources folder. Makes it easy to just move the stuff around if there's an issue with anything. Fire up t
  • Create New...