Jump to content

rwilsonlj

Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

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

rwilsonlj's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thanks for the update! Downloaded this morning and all seems well except that my mouse cursor displays as an up/down arrow in the entire windshield and autopilot panel areas. It is OK below the AP panel and above the windshield. It is like I am trying to do something (raise/lower?) with the sun visors in that entire area. It was probably initiated by my playing with the sun visors. Any help appreciated.
  2. Want to take a guess for the reason for this CTD? Just have to say that with the other 10+ payware aircraft I own, I have had probably 3 CTD in over 2 years. With the TBM, I have lost count. Thanks. Log.txt
  3. For what its worth, I noticed the AI traffic flashes all over the MFD screen. I think this has always been the case. It appears the G1000 simulation does not handle the AI stuff well. Just FYI.
  4. I tried twice yesterday to fly the TBM, crashed both times. I have AI planes enabled. Log is attached. Hope it helps solve the issues. Log.txt
  5. rwilsonlj

    1.1.6 CTD

    I was also experiencing CTD with the previous version of the TBM. I kept getting Exception errors in my logs. After I googled one of the exception codes in the log.txt file I found some info (unrelated to XPlane or the TBM) suggesting I had something corrupted in my windows files. I finally went to the Windows Command Prompt (CMD) in Windows 10 (be sure to run as administrator) and executed the "sfc/scannow" windows command (no quotes) to see if any of my windows files were corrupted . The scan did find something corrupted in my windows files and fixed it. I also downloaded a free registry scan and repair utility and ran it to see if I had registry errors (it found some also). Since then, I have had no crashes in the TBM. I just downloaded 1.16, so I have little experience with it, although my 1 hour flight today went just fine. I have no idea if any of this is related to the CTD errors occuring for others, but just thought I would share my experience as it seemed to fix mine. Neither of these things will hurt anything if nothing is wrong..
  6. rwilsonlj

    CTD

    XP 11 v 11.32r1, TBM900 v 1.14c, Windows 10. Also had this error. Have not completed a full flight since update. I removed all plugins except Gizmo. I have ortho, but does not span a partition. No AI planes. A few days ago I posted a XP11 log and TBM900 log in a post on another topic in the HOTSTART support forum, (forgot which one, there are so many because of CTD on 11.32 and 1.14c), due to CTD with different error message at the end of the logs. Today, I have attached a TBM log with two different flight crashes from flights yesterday and today. Different exception codes. The Log.txt is just today. I have used several of my other payware aircraft recently and yours is the ONLY one having these issues. Kinda seems to narrow it down. Just FYI, as you told another customer to do, I posted the logs I referenced above that were posted in a different topic from a couple days ago in a support post to LR yesterday and following is the reply. You guys need to talk. I have ran out of things to try to fix this issue. If others have fixed this, please post the solution. I do not seem to be the only one having problems. Hello there! We have been in direct contact with this aircraft developer and understand that he is working on a fix for this. Please contact them directly. If they are still expecting a fix from Laminar, we are not aware of it at this time. -- Jennifer Roberts TBM900_Log.txt Log.txt
  7. Sorry to be the bearer of bad news, although it takes longer to experience the crash, the crash is still happening. I have attached both log files. Also, just another dig, the exhaust particle streams are WAY to big and long. TBM900_Log.txt Log.txt
  8. Thanks for your info Goran_M. Just to clarify, I'm not trying to start the engine when the ITT is already at or above 150 degrees. This is a cold and dark start. The ITT is zero.
  9. Hello: Just updated to V1.1.4. Every time I attempt to start the engine, I get a hot start condition. All static elements are removed, GPU attached, AUX BP on, waiting for 15% NG, ITT<150 then set low idle. ITT continues up through the red line and I have to cutoff fuel (getting the hot start warning at the top of the screen as well). Not sure what I am doing wrong. I think I am doing the same as previous versions when I had no problems. I'm pretty sure it asked to update my license (email & password) after I downloaded the new version. Any help appreciated.
×
×
  • Create New...