egon_cr

1 minute ago, Sesquashtoo said:

Ten THOUSAND votes for this!  I'd be content with this in operation. I would have chosen to stay with RTM MSFS...and sit in the bush watching the comments of adopters of the updates, as I do with XP11 updates....

Same, for me the best state was with the last patch before this one and I would have gladly stayed there for a while. I was really enjoying the sim and learned to ignore or work around the minor bugs as I did with previous MSFS's. Never had any CTD until now.

Let's try to make this happen:

https://forums.flightsimulator.com/t/please-add-an-option-to-defer-patches-updates/

I think most of us would agree with this. Even for those of you who have a perfectly smooth experience with MSFS right now, the risk of breakage is high given the precedents.

People who want to "beta test" the latest patch can do so while the rest wait until things stabilize. Some things like the tall buildings are probably caused partially by Azure changes and not local patches, but we shouldn't be exposed to mediocre patches with high CTD potential, among other things.

On 8/30/2020 at 4:16 AM, Colonel X said:

The periodic CPU spikes are eliminated when using the Process Lasso trick. Search it on the forums.

I found that very same post shortly after posting here and installed Process Lasso, which completely got rid of the stutters. Those claims that this sim should run on 8+ core CPUs are clearly not true since it can perfectly run on a 9600k, the software is just badly optimized at this point for some processors.

PD: I didn't have to set Windows to prioritize background processes nor change the flight sim task to low priority. Process Lasso is enough. Just stick to the instructions in that post.

Thanks all for chiming in. Hopefully we won't need this after a future patch.

On 8/19/2020 at 4:03 PM, cwburnett said:

So, I'm really interested in nailing this down and have been doing some testing. I'm curious what others are experiencing, though, because I think we might be talking about a few different things. BTW, I'm looking to compare solutions and settings, not bash the sim. Each sim has required settings finesse to get a smooth experience. It took literally years to understand P3D well enough to run smooth with good visuals. I hope for a shorter learning curve here!

So, I'm experiencing periodic stutters, maybe 5 minutes of smooth and then 5 seconds of stutter, that feels like a version of what we experienced in P3D v4.5 - the so-called Orbx scenery loading pause... So for most of the time, I have smooth 30fps performance. When watching the FPS counter in developer mode, I can see that normally my FPS is solid at 30fps and limited by the GPU, which is expected on vsync at 30 hz. However, when I encounter the period of stutter, it shows in the low/mid 20fps and indicates limited by the main thread.

I *think* that this is actually impacted by the Terrain LOD setting, but could be the objects LOD also...I was surprised that Terrain LOD was CPU intensive, but it appears to be... below is what the stutter looks like from a performance perspective....curious if this is what anyone else is seeing... don't mind the screenshot quality, it is an HDR issue I guess...

 

Hey pal,

Did you find a solution for this? I have an almost identical system as you, same exact CPU (also overclocked @ 4.9Ghz) and an RTX 2060 (instead of a 2070) and I also suffer from the exact same issue you have/had (we are not that many with these symptoms). The performance is fine and what I would expect like 90% of the time, but the other 10% is heavy stuttering which drops me to single digits and all 6 cores shoot up to 100% utilization (it normally stays at around 50% average). I have screenshots that show an identical behavior:

Could it be something specific to the 9600k? I have tried everything short of going back to stock clock speed (which I'm seriously considering) but the fact that every single other game I have doesn't exhibit this issue makes me think it's simply FS2020.

Wondering if you found something? I haven't. Even potato low settings don't help. It happens less, but still happens.