Robert85

I noticed while flying the SR20 with autopilot and disengaging AP master with FD, YD was still activated on the autopilot display panel on the PFD. I also noticed there's no physical YD button on the center console (GFC700 AFCS), like there is on the SR22. So after playing around trying to figure this out on the ground, selecting the 2D pop out pfd and mfd panels, I noticed i can turn on and off YD. So not sure if this a bug and or feature of the SR20 and if someone can clarify this for me ? Also to note I have never been in or flown the SR20 or SR22 IRL in case this is not obvious. I'm still learning about these advanced systems related to the Cirrus aircraft, so please excuse my ignorance Thanks, -Robert

Update to my situation above. I feel silly not figuring this out and might seem obvious to many, but for those like me wondering how to get around this without a external radio stack and don't want to use the 2d popup mfd panel outside of VR. Assign nav 1 and nav 2 flip standby control assignments to any peripheral controller in control settings in xplane and you can switch at will in VC and VR At least now I can enjoy this plane in VR until TorqueSim can get these click spots ironed out in the next patch, hopefully.

Hello Folks, thanks for this fix above ^ however, the nav frequency stby transfer switch has no clickspot in VR. I fly mostly in VR and on pilotedge, so this pretty much grounds me with this model (SR20) until fixed. If possible is there something that can be added to the obj file above to get the stby transfer switch, nav right side mfd working until future ofc patch? Would be much appreciated. If this has been addressed elsewhere on the forums, please disregard this post. Love the plane BTW! You folks did a outstanding job. -Robert

Glad to hear the TBM is working out for you ! Interesting on MacOS your FPS has no problems with synthetic view. TBM has been solid on my end as well. Smartcopilot giving me some issues, but that has nothing to do with the TBM on it's own. Think I'm going to have to learn how to mess around with the smartcopilot cfg files. Other then that, nice to finally enjoy this aircraft. Something I noticed, yesterday I was using the Diamond DA62 from Aerobask; lovely plane btw and I got a crash using instant replay with it, but what's interesting is the way it crashed. Had some of the same CTD symptoms the TBM had when it was crashing on me. Example is everything fine, then a pause with a sound glitch then runs for a sec, then a hang. Only way to exit is to ctl-alt-del out. So I'm thinking maybe some of the CTD's prior to my graphics card driver re installation with the TBM, may not of even been related directly from the TBM. But rather an issue with X plane some where, never checked the log file could of been a memory thing, who knows. Just something I noticed, so credit to the TBM there. Funny, I never thought I would like synthetic vision like I do now. Always thought eh... gimmick lol but after flying with it on the TBM, I actually miss it on my other aircraft using the G1000 now. To be honest I prefer steam gauges, but I don't know, this G1000 stuff is growing on me, uh oh lol. May we have many more successful flights. Cheers, Robert

Hi again kbjackson, From my understanding I have read the malformed data relating to scenery and such can be ignored, for the most part. I don't know all the ins and outs to that but, is what I gathered from other threads. Also, I get the same errors too and to take note, I do use Ortho4K scenery. One of the things I love about X-Plane that and smartcopilot. I will say, X-Planes ground handling leaves room to be desired, but that's another topic and not limited to just the TBM. No issues with the custom scenery on my end, so far.... I read somewhere perhaps the AI can cause issues with the TBM. I'm not sure if this applies for default or other traffic addons? My understanding of this is limited. As far as the AI traffic goes, for the first time last night since I have gotten this aircraft stable, I reloaded the AI back into the mix. No crashes. (default traffic) I have also had the same errors "Tried playing a wave file that doesn't exist".... I have no idea whats that's from, or if it is even a factor with the TBM, but I have seen it. I also let my TBM sit on the ramp yesterday between flights for a couple hours in between; running in the background and started the plane back up did another short flight, no problem and for me I was impressed because this aircraft before the driver reinstall, wouldn't of allowed me to do that. I would of had several crashes in between. I'm about to start a flight from the San Diego area VFR and head to Vegas with a return trip perhaps. I'll be increasing my flight time between sessions and see if it plays out with no incident. I will also try it with smartcopilot to spice things up a bit, with a friend of mine. Maybe encourage a crash lol, should be interesting. I'll report back with my findings. Oh and that's a good idea to have separate installs for your X-plane. Is something I need to do for X-Plane and my P3D installation. Would make life easier for testing. Regards, Robert Edit: I'm also going to reload X-Camera as well I miss that plugin. I also use TrackIR for whatever that is worth.

Hi kbjackson, I know how frustrating it can be to get that dreaded exception handler error. I used to get that error at any random time, it could be 10 mins into the sim or after completing a 3 hour leg taxing to the ramp and then CTD with the same error. No backtrace can't even tell wheres it's coming from. Whats even more strange, is when I uninstalled my graphics driver and did a clean install, I have not had that error or any other random CTD's with the TBM. Of course I got rid of the errors in my logs with the graphics driver crashes, but that doesn't explain why I haven't been getting the exception handler errors. Not to mention that error has been reported for sometime, with different patch builds. Now I have only been doing short hops under an hour at a time since i resolved my issues. So tomorrow I'm going to test some longer leg trips and hopefully no CTD's. Of course like you said up above, other addons plugins etc they run fine, same for me. Only with the TBM have I noticed this issue as well. However, like Goran said in other posts, not to quote but something on the lines of, the TBM is very complex code and it could be a number of things not even related to the TBM perse, but rather conflicts with other add-ons, plugins ect. Discrepancies in the code and such with other developers even including Laminar x plane that maybe ?causes the TBM to crash. I have restored some of my plugins back into the sim with the TBM, mainly AviTab and smartcopilot that I use and no problems so far. Also to note, I'm still not 100% convinced I even solved my own problem, but so far so good. So only time will tell. I will say, before I couldn't even complete a single flight! The TBM would crash, usually after playing with the G1000, flipping threw charts especially , it seemed anyhow. Very strange... I can at least finish my flights now from startup to shutdown lol. Knock on wood..... I really like this aircraft otherwise I wouldn't even of wasted my time With that said, I hope somebody or Goran can help you out maybe identify something in your logs to get you sorted. I know you did a clean reinstall of x plane and tested between Windows and Mac, but for now I could only recommend keep only Gizmo plugin nothing else for testing and uninstall re install your graphics driver and do a clean install of that if you haven't already and see where that takes you. I have a Nvidia chip so in the install prompt there's a checkbox to do a 'clean' install. I'll keep doing tests on my end and keep an eye on this thread. If I have any problems I'll report them here. Hopefully you can make some progress like I have and get the rid of that pesky error. We shall see. Regards, Robert

Ok to give an update, I have had two more successful flights KCRQ-KL35 and KL35-KRCQ with no issues. Also worth mentioning that I introduced AviTab back into my plugins and using OrthoXP scenery. No crashes... I also have done everything to try and induce a crash that would cause my TBM and sim to fail, mainly messing around with G1000 and such. So three flights successful. Knock on wood I'm surprised at all the issues reading in the previous threads about all the crashes people been having, and that I was having too, that I didn't think my issues would get resolved and kinda lost hope. Thanks to Goran, who was able to point that out for me, it was a simple fix of performing a clean graphic card driver installation, as it seems so far. I am thankful for that. Also to point out that the VOR problem I mentioned above, was a matter of selecting a VOR station that wasn't equipped with DME. I selected some different VORs with DME and had no problem getting DME readout information on my PFD. Thanks to @okidokki So that issue resolved and my bad there. Just thought I would share the update. Log.txt TBM900_Log.txt Regards, Robert

Good point, looking at the sectional chart this particular VOR station appears to not have DME associated with it. I have completely forgotten about that. Next time I fly I will choose a VOR/DME Station to test.

Just goes to show how far the X-Plane system limitations can be stretched. What you folks have done with the stock G1000 is very impressive. Thanks Goran, Robert

Ok so I updated my drivers and performed a CLEAN installation using Nvidia settings, rebooted and had a successful flight from KCRQ- KL35 (Big Bear Lake, CA). I was trying to induce a crash as well, fiddling with the garmin G1000, flipping threw charts, scrolling through nearest airports, etc.. Couldn't invoke a crash. So I got my fingers crossed I will perform more testing and inducing to be sure, and if I do crash I will post back here with the new updated logs. I must say it was very rewarding to fly this aircraft and not have it crash from startup to shutdown Had a nice landing too. Thanks Goran for you're help with this matter, I see you posting all the time in the forums helping a lot of people out and going out of your way, something a lot of other developers should take heed too. I do have another question if I may, I noticed flying VOR radial navigation using the G1000 pilot PFD, the DME option that you can have display on the screen shows NAV1 and NAV2 with the approiate frequency showing, but with not DME distance shown it's just dashed out (- -. - NM) <--- Is that a bug or am I forgeting to activate a button or setting ? Just curious. (To Note I am within bounds of the VOR and tracking VOR radial track with Autopilot, in fact even crossing the VOR station and no DME distance.) Logs: Log.txt TBM900_Log.txt Anyhow thanks again, Robert

Hi Thanks for responding Goran, No I run a single monitor setup. Hmm maybe I should uninstall the drivers and then reinstall ? I'll try that and report back. Thanks for looking into it.

Hello folks, I've purchased this lovely plane which I enjoy very much. Unfortunately I have been having problems with CTD's. I really haven't been able to complete any of my flights without a CTD. I normally do not post in the forums, but I like this aircraft so much that I felt the need to post to try and get to the bottom of this I hope. I hate to ask for a refund especially if this issue can be resolved. It's just hard to enjoy something that just doesn't work on my machine. I really do like this aircraft and I know just how much time and effort went into designing this aircraft and the code involved. I have been going threw the various forums looking for as much information as I possibly can regarding this issue. Trying different methods to somewhat debug the problem. I've been following your threads @Goran_M about CTD's and the TBM, and just have no luck. I'm using XP 11.35 and the latest TBM update. I get the famous " TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000 " messages in my log's. Frustrating because as said before in other threads hard to backtrace where that's coming from. My recent crash I just had flying from KCRQ-KL35 I've received a different log which caught my eye and thought worth uploading here below. I was using OrthoXP in this situation, but I have had crashes with it disabled using only default scenery . Maybe this log report can shed some light to the issue? I would appreciate any help with this matter. What I have tried: -Updating Graphics Drivers. (NVIDIA 1080 GTX TI) - Disabling all plugins except Gismo and XUIPC for X-Plane. -Disabled and removed any OrthoXP Scenery -Any and All AI Traffic including parked planes (only have default traffic and weather to note) -Re Installation of Hotstart TBM 900 -Removing TerrainRadar -AviTab removed To note I've tried various setups sceneries and plugins and just no matter what the TBM and X-Plane CTD. ====================================================================================== PC Specs: Windows 10 16GB RAM System Mobo Z170MX-Gaming 5 Processor Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz NVIDIA GeForce GTX 1080 TI 431.60 driver (haven't tried new driver that just launched today 436.02 will install) ======================================================================================= Log Files: TBM900_Log.txt Log.txt Thanks again, Robert Also to Note: If I have too I will do a full operating system re install including obviously X-Plane 11 if nothing can come about this log file, that will be my last ditch effort to resolve this on my own.