LanPartyPizza

I run a 30mbps internet connection and get occasional Azure voice drop outs when other people in the house are hammering the connection. However I rarely see MSFS actually use the connection besides the initial flight loads. I have hardly ever had the terrain drop out. Plainsman gave some good specs. The only suggestion I'd make is that I think most boards will get around 3600mhz DDR speeds quite easily so I'd buy for that. Do your research though because it's more important now more than ever. I'd also say get the best graphics card you can afford (or get your hands on) because if you're playing at 4k, the hardware will definitely be the limit. People say this game is very CPU dependent and it is, but don't think a fast CPU will trump the best video card on the market. It's more like a bad CPU will bring the game to a crawl even with the best video card etc. Bottleneck's and such. Depending on your final video card choice make sure your monitor supports g-sync or the AMD alternative equivalent because you'll find V-Sync a complete pain.

I don't really get it plainsman. You make some great suggestions and I'm sure also identify a lot of common problems for what is a particularly demanding game. However the hotfixes and bug reports from Asobo should be enough confirmation for anyone regarding the constant CTDs and various other issues the game has had. I'm glad it's been working for you, but I've gone through three systems personally where it hasn't worked. They have all been great systems and the two I run now work flawlessly since the latest hotfix. I'm not talking about the general bugs in game either, I'm really talking about stability which was an early deal breaker for me. I'm glad I could use the past tense earlier as well, I really do think that the vast majority of CTD bugs have been worked out. I'm now an extra 50 hours in since the latest hotfix with no changes to my system and also no CTDs. The rest of the bugs will get worked out in time, but if you look at how long it has taken to fix relatively serious bugs in the past, it's no wonder people get annoyed. For example, when I bought the game, rudder control had been broken through a patch. It took two subsequent patches for it to be worked out properly. This kind of thing just shouldn't have happened, and shouldn't be left unchecked for as long as it was. Anyway, it's not like I don't like the game, I do, but it has taken a year to get here and for most other games, this kind of stuff would have been worked out in beta testing.

I didn't want to be that guy but I've now requested a refund and as it's been denied taken this to the ACCC. I just can't stand game devs using the public as their guinea pigs anymore. Thanks for the thorough list of troubleshooting steps but unfortunately it isn't solving this for me and the game is no longer enjoyable after the last few updates. It looks fantastic, but not being able to fly for more than 10 minutes reliably has just killed it for me. The bottom line is that while all of those steps are good, we shouldn't need to do any of it. Not happy. :(

Hit and miss for me, I think this has been confirmed pretty widely by now though.

I mean, I don't know what you guys are complaining about. I for one love my new retro neon theme landing light fluro livery.

Hi, I think this is a bug. Lets see if we can repeat these across platforms? I am flying from YARM and tuning Nav 1 to 112.60 with no success. No audio signal, no update to VOR/OBS. This is the correct frequency in MSFS and on SkyVector but in game there is no result. Flying into YMLM I also get nothing on 113.3 which is what SkyVector puts as a NavAid (don't know what type, I'm not familiar enough with thing and this is a military airport used for commercial). However MSFS2020 reports a Localizer DME Navaid on Frequency 110.500 Mhz. Identification is IWM. This one works in game but this navaid is not shown on SkyVector. So, after much frustration, I think the input data MS has used is trash.