Yet another tip, ensure nothing is overheating and throttling, if it is add a fan or grab the waterhose.

 

17 hours ago, SmokeDiddy said:

So, for the past week, I've tweaked and tweaked and tweaked settings in order to stop the stuttering and pausing.  Just when I thought it's finally solved, here they come back.  At this point, I'm left hoping for a miracle with the, soon to be released, patch.  I have this sobering feeling that, for my hardware and internet connection, the outlook for me moving forward with MSFS2020 in the near term is slim at best.

Here's my dilemma:

i5 6600k CPU, 4 core, no hyper threading 3.5Ghz (stock) | GTX1070 | 32GB DDR4 3200Mhz | std 23" monitor 60Hz | Internet 20Mbps down/10Mbps up, avg ~12Mbps down.

Clearly, there's plenty to choose from when it comes to weak links in my setup.  In my mind, I'm thinking that it's fruitless if I upgrade my hardware just to have limited internet.  I'd be interested to hear from those that have high end hardware, but limited internet.

I also have to believe that with, soon to come, premium add-on aircraft, sceneries and other items we simmers gotta have.  Doesn't it make sense that the hardware requirements for these items along with the sim will increase?

I was able to get a few weeks in the seat during Beta.  I did not encounter the stutters and pausing to the level I've seen it since the release; however, I was plagued with the Internet Connection Lost error constantly when trying to fly around my location in southeast US.  When I'd fly around New York or LA, rarely did I get this error, but my FPS suffered for obvious reasons, and no noticeable pausing.

AVSIM has always been a lifeline to me and many others.  I will listen to all ideas and opinions to the quandary I find myself.  At 56 years old in November last year, I was laid off from the company I spent 32 years of my life.  It's still a little early to retire, so in March I finally landed a job at 50% of the pay I was making, so my budget has suffered as a result.  If I have to upgrade hardware, i want to do it smartly.  I live in a rural community and the fixed wireless internet service is all I can get.  I'm not trying to start a pity party for SmokeDiddy, just reaching out with my specific issues to help me try to get at a happy place with MSFS2020.  Thanks for listening!  

 

Very interesting. I have the exact same specs on my desktop though an overclock to 4.6 Ghz and the sim is unflyable. Serious second-long stutters along with microstutter.

We work in the same field. 😊

I’ve tried every plausable tweak without success. I think our processors might not be up to snuff. I tried MSFS on a six core current gen laptop (i7 9750H) RTX 2060 and it’s working great.

I’ve seen plenty of ppl at avsim, reddit and the MSFS forum having trouble with i5 processors, 6th gen and earlier.

Please let us now if you manage to sort it out.

Edited August 27, 20205 yr by TheRandomGuy

I agree, CPU might likely be part of your issue. Maybe a CPU upgrade...

Single thread rating on that CPU is 2336, so that's somewhat ok...

Issue might be overall passmark (6290), that's pretty low.

CPU I am using has a single thread rating of 2600, and a total rating of 18,000. So almost 3x more leeway than the CPU you guys are using, and even then my CPU in fact is likely still a slight bottleneck. Though in my case I think I have a fighting bottleneck between both the CPU and GPU, so either upgrade would do me a little good. Using an Nvidia RTX 2060 with AMD Ryzen 5-3600. 

The 2060 and 1070 are pretty close performance wise in this game, generally speaking.

Edited August 27, 20205 yr by SceneryFX

7 minutes ago, TheRandomGuy said:

Misquote.

Edited August 27, 20205 yr by TheRandomGuy

There is a major simconnect bug that never seems to get mentioned. If you are running anything outside the sim that uses simconnect: STKP, Spad.Next, LittleNavMap, etc. Anything! It can pretty much crash the FPS to like 15 and cause a stutterfest. 

To the OP:

My hardware is very similar to yours, and we use identical video cards (the GTX1070). You noted that there's no hyperthreading in use on your system. Like you, I was part of the alpha-beta test program and never experienced any significant issues with FPS or stuttering. Then, with the commercial release on August 18, I immediately suffered much lower FPS and, far worse, stuttering everywhere. The commercially-released sim was pretty much unplayable for me. Since I was using identical hardware and identical settings with identical internet speeds as in the alpha/beta program, I think it's fair to conclude that something, somehow, some way, got changed in the sim or the servers between the test program and the release version. I then read a tip about how to tell whether your system has hyperthreading enabled. Mine did not have it enabled, but had the capability to enable hyperthreading. When I enabled hyperthreading in the bios, the sim began running beautifully, as it had in the alpha/beta. So, because of hyperthreading, I'm now using eight logical cores instead of only four. Eight logical cores seems to be a minimum requirement, though that is not officially listed as a system requirement.

So here's my advice to you: Because I successfully ran the entire alpha-beta program on only four logical cores, the sim is quite capable of running well on four logical cores. We have proof of that. Why and how this was changed at the last moment, I have no idea. But it stands to reason that Asobo could therefore revert to previous code that ran the sim well on only four cores. Perhaps this "regression" will be part of the forthcoming patch. I sure hope so! You're definitely not the only person who would benefit from such a move by Asobo. If, however, there is no decision by Asobo to once again make the sim usable on four logical cores, then all the tweaking in the universe will not help you, and you'll just have to upgrade your rig.

 

Edited August 27, 20205 yr by David Mills

The only thing I would add is download and run an overclocking monitor somewhere in the corner of your screen. It will show you the 'actual' processor speed which will likely vary during playing FS. You may have it set to 4.2Ghz or something, but the Motherboard maybe is throttling it down due to heat measured on the MB. An overclocking monitor will display temperatures constantly and true processor speed in real time.

If OP does keep the same system, I hope it is watercooled. It should be. It's not too hard to install it and is safe because it is a closed system, you never have to mess with adding fluids. No need for a big fan radiator the lowly Corsair H60 or even H50 will keep things cool and therefore keep c.p.s. up, and also extend the life of the cpu.

 

4 hours ago, TravelRunner404 said:

There is a major simconnect bug that never seems to get mentioned. If you are running anything outside the sim that uses simconnect: STKP, Spad.Next, LittleNavMap, etc. Anything! It can pretty much crash the FPS to like 15 and cause a stutterfest. 

Yeah, but in my case, I don't use anything atm that requires SimConnect.  When I uninstalled P3D, SimConnect went with it.

4 hours ago, David Mills said:

To the OP:

So here's my advice to you: Because I successfully ran the entire alpha-beta program on only four logical cores, the sim is quite capable of running well on four logical cores. We have proof of that. Why and how this was changed at the last moment, I have no idea. But it stands to reason that Asobo could therefore revert to previous code that ran the sim well on only four cores. Perhaps this "regression" will be part of the forthcoming patch. I sure hope so! You're definitely not the only person who would benefit from such a move by Asobo. If, however, there is no decision by Asobo to once again make the sim usable on four logical cores, then all the tweaking in the universe will not help you, and you'll just have to upgrade your rig.

Thank you David!  I've felt for a couple of days that my cpu isn't adequate because of the lack hyperthreading in this cpu.  It's too bad MS and Asobo didn't release a technical summary (similar to a White Paper) of the hardware requirements, it might have saved a bunch of us a whole bunch of time and effort.  Nevertheless, I wanted to give it my best shot because I knew going in, it would be close.  I agree, these issues were pretty much non existent in the Beta build.

I'm a patient person and will be in a holding pattern to see what the updates flush out in the near term.  My patience only goes so far though, so if need be, I'll purchase some new hardware.  Until that time, I'll do flights in XP11, as it's all I've flown for months anyway.  Thank you for the thorough and well articulated reply.  Those are rare indeed these days.

47 minutes ago, Fielder said:

If OP does keep the same system, I hope it is watercooled. It should be. It's not too hard to install it and is safe because it is a closed system, you never have to mess with adding fluids. No need for a big fan radiator the lowly Corsair H60 or even H50 will keep things cool and therefore keep c.p.s. up, and also extend the life of the cpu.

Yes, I have the CorsairH60 in my system.  So far, so good at 4.5Ghz @1.380v.  The fully quad pipes have served me well at the stock frequency as I don't think P3D nor XP11 utilize hyperthreading to the extent MSFS2020 does.  It was just a matter of time before it was done.

22 hours ago, SmokeDiddy said:

Just when I thought it's finally solved, here they come back.

Boy if that doesn't sound like FSX.

Cheers

bs

Certainly feel for you losing your job, just got it confirmed the other day: made redundant from my job at the airport. Nice birthday present for me today huh? 🤣

Ouch - that happened to me on my birthday 2x.

bs

2 minutes ago, Chock said:

Certainly feel for you losing your job, just got it confirmed the other day: made redundant from my job at the airport. Nice birthday present for me today huh? 🤣

Awe man!  I definitely feel ya on this one and your birthday to boot.  That's a real bummer.  Good luck with the next gig.

Just now, SmokeDiddy said:

Awe man!  I definitely feel ya on this one and your birthday to boot.  That's a real bummer.  Good luck with the next gig.

Well, as they say, when one door closes, another one opens. Which is usually a good thing, unless you're an astronaut in an airlock. 🤣