5 minutes ago, Bobsk8 said:

Version 4 sounds pretty old, not sure when it was sold. Track IR 5 came out in 2009. Try not using it and see what happens. 

I am sure it is old, so I do not use it in MSFS anymore because of crashes. I haven’t used it for at least 2-3 months now. 

I had a period after SU5 where I got CTDs every other flight, but I haven't had an issue since WU6. The sim is finally working great! I'm having an almost completely stock sim except for the WT CJ4, flying on VATSIM with no AI.

Edited September 19, 20214 yr by wims80

Thread has turned a bit into AMD bashing.

regarding the code - maybe some serious rubber ducking is needed 😉

MS - please buy Asobo some ducks👍

1 minute ago, hanhamreds said:

Thread has turned a bit into AMD bashing.

https://www.youtube.com/watch?v=Fmj2kUk-xO4

 

2 hours ago, RobJC said:

I have been a pretty big advocate for MSFS because i can clearly see the potential for this platform. But here we are a year out still fighting crashes, and serious bugs. Regarding crashes, half the flights i have attempted have ended in CTDs, and i no longer use my CH Yoke, TrackIR, add-ons, overclocking, config tweaks, NVIDIA Inspector, etc. I really can’t go any more “stock” than i am now, and i am still getting crashes. Throw in the update issues that many users are experiencing (it is 2021!) and i think it is time for Asobo and the MSFS team to rethink how the code base is being managed. The uncertainty of MSFS between updates is really hurting the franchise, tbh. 

The first thing i would do is analyze each bug to figure out how not to repeat it. Was the bug a regression that was fixed and then broken again? If so, why? Is there a problem merging branches? Are changes being hammered because someone committed a change without merging their changes first? Something related to the process of developing and managing this code base has gone wrong.  Best practices are not being followed. Lessons are not being learned. And a lot of MSFS customers are paying for it. 

The issues here go far beyond needing more testers, or having a larger/longer beta test. There are fundamental problems with how the code base is being managed. 

The technology looks great. Super smooth performance. But what difference does it make if half the flights end in crashes? 

Not happening here so that makes it hard to troubleshoot for you.  Best of luck with it sounds very frustrating.

59 minutes ago, hanhamreds said:

Thread has turned a bit into AMD bashing.

regarding the code - maybe some serious rubber ducking is needed 😉

MS - please buy Asobo some ducks👍

My AMD GPU was a POS. If that is bashing, so be it. 

2 hours ago, Bobsk8 said:

When I suffered crash after crash, I was told by just about everyone that there was something wrong with my brand new system. After months of this, I sent my PC to the company that made it and they replaced the AMD GPU with a Nvidia GPU, because I was getting many driver time outs with the AMD card, and a new PSU for the new GPU. Haven't had one crash in 5 months after getting my PC back. . 

I agree. I had CTDs not only with MSFS but with any other game at totally random timings. After weeks and weeks of trial and error we finally found out that my PSU was the culprit. After installing a new more powerful one i havent got a single CTD since. That was about a year ago.

ermmm  I have the machine I had built for MSFS shortly after it's release as listed in my sig  (The tech is post release so I can't say since release) but since I have had the machine, I have flown every single day with it and had two CTD's...  the first was just after getting the machine and the reason was a power issue because the machine builders had used a y adaptor to power the video card instead of 2 seperate power cables,  the second was down to a known add-on that was causing CTD's, nothing to do with the hardware.

Currently, post WU6, I get a solid 60FPS on all ultra settings at 2k resolution on my monitor.   All latest drivers.

AMD is not an issue in MSFS for me.

Graham

Edited September 19, 20214 yr by Moria15

1 hour ago, sidfadc said:

Not sure what sim you have been flying but after 1 year the sim has developed ten fold.  Yes there have been issues, yes there has been bugs and yep had my fair share of CTD however a project of this size and complexity should not be taken lightly. Has it been perfect in the first year?  Defo not but honestly I’m having so much fun with this sim  and can’t wait to see what year 2 has in store!

I'm entering my fourth day with no MSFS to enjoy.  I have a Zendesk ticket in, but my own three days of research have yielded nothing.  MSFS will not open because the XBOX app will not log in or see the internet. I am dead in the water.

Since Hotfix 2 SU5 I have had an almost flawless MSFS.  Zero CTDs, smooth flight etc.  My last flight was in the modded Beechcraft single, a flight at FL220 from Oceano to Half Moon bay. The scenery and weather was breath taking.  The last hotfix has shut me down completely.

I saw a few posts saying they were nervous for the new hotfix - I don't blame them!

6 minutes ago, MrBitstFlyer said:

I'm entering my fourth day with no MSFS to enjoy.  I have a Zendesk ticket in, but my own three days of research have yielded nothing.  MSFS will not open because the XBOX app will not log in or see the internet. I am dead in the water.

Since Hotfix 2 SU5 I have had an almost flawless MSFS.  Zero CTDs, smooth flight etc.  My last flight was in the modded Beechcraft single, a flight at FL220 from Oceano to Half Moon bay. The scenery and weather was breath taking.  The last hotfix has shut me down completely.

I saw a few posts saying they were nervous for the new hotfix - I don't blame them!

I did a quick google search for your problem and found a post that might be relevant for you. https://answers.microsoft.com/en-us/windows/forum/all/windows-10-xbox-app-says-im-not-connected-to/f737be60-801a-49bd-b2ed-dbc01b2d158e

 

Make sure that the 'XBox Live Auth Manager' is running 

Edited September 19, 20214 yr by wims80

Not had any problems with my AMD GPU running MSFS from literally day one of its release to the present, and I have pretty much always used AMD GPUs over the years. What puts me off NVidia GPUs is this place, where loads of people are forever banging on about this or that tweak to their config file or that file to sort out the colour or the gamma or whatever, and it was the same prior to MSFS with P3D and FSX, with everyone banging on about this and that with their NVidia inspector or whatever it is and this thing to sort out the colours. I never do any of that, never did with FSX, or P3D either, I am too busy flying around in the sim, using my AMD GPU. 

I know this may irritate some. But I have had maybe 3 CTD's since day one.

My system description is in my sig.

I use NVIDIA because it was the best in X-plane. AMD is a great product but  for some reason was not good in XP.

One thing is I use my machine only for simming, not even internet browsing, I use Macs for that. And all downloads of 3rd party stuff is done on the Mac and virus checked before transferring to the sim computer. I do use a lot of ORBX and maybe 10 non marketplace additions. 

I do not over clock and use no special NVIDIA settings, just plain vanilla so to speak.

Now 3 times I have had to mess around to get updates to work, but always solved that in an hour or so. And a few problems with third party products until they got patched. But all and all I would even give the updates a C+. Considering how young this product is.

I think it is great that it has so many improvements so often, and i am willing to put up with a few problems now and then for such a fantastic experience.

2 hours ago, wims80 said:

I did a quick google search for your problem and found a post that might be relevant for you. https://answers.microsoft.com/en-us/windows/forum/all/windows-10-xbox-app-says-im-not-connected-to/f737be60-801a-49bd-b2ed-dbc01b2d158e

 

Make sure that the 'XBox Live Auth Manager' is running 

Thanks for the suggestion.  Many of the guides out there include restarting these services but it doesn't work in my case.

4 hours ago, Maxis said:

Can you guys PLEASE STOP SPREADING "FUD" regarding AMD products?

Fine it doesn't work for you .. It WORKS for others MYSELF included and as long as you people DID NOT build your systems yourself OR stress test all your components properly everything you all are posting is PURE CONJECTURE. Enough with the Fanboyism

Back to topic...

I think it would be best if there is something in the code that can identify what aspect of the sim is causing the CTD in a crash report. (Something a bit more understandable to the average person who does not know how to read the Windows event viewer.

Agree.  I've got a Ryzen CPU paired with an RTX3060ti.  Runs beautifully.

2 hours ago, Chock said:

Not had any problems with my AMD GPU running MSFS from literally day one of its release to the present, and I have pretty much always used AMD GPUs over the years. What puts me off NVidia GPUs is this place, where loads of people are forever banging on about this or that tweak to their config file or that file to sort out the colour or the gamma or whatever, and it was the same prior to MSFS with P3D and FSX, with everyone banging on about this and that with their NVidia inspector or whatever it is and this thing to sort out the colours. I never do any of that, never did with FSX, or P3D either, I am too busy flying around in the sim, using my AMD GPU. 

Agreed that there is a lot of posts on NVidia tweaks,  but I for one, never bothered with any of it. NVidia  has been fine for me without having to tweak it.