1 minute ago, Sky_Pilot071 said:

What kind of analysis has been done on the Steam Overlay?  Obviously since it caused the original problem then it is the key to finding the solution.

What happens if you renable it?

Remember it holds the answer to a solution so a deep dive is necessary.

sp

Back in July I saw some posts about this which is why I disabled it and it worked.  I enabled it and it came back.

What would be point of enabling it now as I'm getting the same pause as last summer.  

5 minutes ago, Jack_Sawyer said:

Back in July I saw some posts about this which is why I disabled it and it worked.  I enabled it and it came back.

What would be point of enabling it now as I'm getting the same pause as last summer.  

Analysis.  Its the only way to solve the the problem.

Do diligence and all that.

sp

Edited February 9, 20233 yr by Sky_Pilot071

Just now, Sky_Pilot071 said:

Analysis.  Its the only way to solve the the problem.

sp

Analysis.  SP, this is what I've been doing for several days now.  Do you know of any analysis tools that are better suited to this than Task manager or ProcMon?

As I indicated above earlier today, I can send you literally pages of analysis, or steps I've taken to troubleshoot this.  It is highly reproducible yet unstoppable so far.

The difficulty lies in capturing what exactly is happening every sixty seconds.

I'd disable Steam entirely, if possible.

I don't have the Steam version of MSFS, so I do not know if it is required to have some Steam overlay process running in the background or not.

What you should be doing is running MSFS without anything else.  And I mean nothing else.  Nothing in Community folder.  No Process Lasso,  No Steam.  no nuthin'.  Pare down your system tray to as little in there as possible.

22 minutes ago, Mace said:

I'd disable Steam entirely, if possible.

I don't have the Steam version of MSFS, so I do not know if it is required to have some Steam overlay process running in the background or not.

What you should be doing is running MSFS without anything else.  And I mean nothing else.  Nothing in Community folder.  No Process Lasso,  No Steam.  no nuthin'.  Pare down your system tray to as little in there as possible.

Hi Mace.  I tried this the other day.  MSFS won’t run without Steam.  The only reason I bought it from Steam was because I had the same version of MSFS stand-alone but I couldn’t move anything at all out of my community folder without that ridiculous permission nonsense so on the word of somebody here I bought it on Steam.

Process Lasso is history, I uninstalled it yesterday.

I tried it without the TDS GTN 750, same thing, same pause. 

Jack it seems that you have tried every suggestion out there, have you tried the following:

DX11 to DX12 and test

Turn off Rolling Catch and test

Turn off Photogrammetry and test

Turn off Sound and test

Does your problem happens only while flying or it also happens while just sitting on the tarmac/runway. 

 

 

Jack, another shot:

https://answers.microsoft.com/en-us/windows/forum/all/solvedpc-stutter-every-one-minute/5bdb4103-95c4-4bb1-90b7-4dc5906e42d2

Have you got a screen saver or energy settings that might interfere?

12 minutes ago, CarlosF said:

Jack it seems that you have tried every suggestion out there, have you tried the following:

DX11 to DX12 and test

Turn off Rolling Catch and test

Turn off Photogrammetry and test

Turn off Sound and test

Does your problem happens only while flying or it also happens while just sitting on the tarmac/runway. 

 

 

Hi Carlos and thanks.

Yes.

Yes.

Yes.

Yes.

Both flying, sitting, and taxiing.

4 minutes ago, teletom said:

Jack, another shot:

https://answers.microsoft.com/en-us/windows/forum/all/solvedpc-stutter-every-one-minute/5bdb4103-95c4-4bb1-90b7-4dc5906e42d2

Have you got a screen saver or energy settings that might interfere?

Hi Tom and thanks.

I don’t use a screen saver, never have and energy saving settings are off.  I double checked these anyway the other day.

5 hours ago, Jack_Sawyer said:

Before I was to undertake such a measure wouldn't it be fruitful to be able to actually see what is causing it as something is causing this.  The problem is not having good enough tools to capture the exact mechanism of this pause.

Hi Jack, I am not sure you have exhausted this option, however frustrating it may be.

You say that it happens too quickly for you to capture the event... so..

In Task Manager, viewing processes, sorted by CPU%, do you see anything happen every 60 secs, even if it is too fast to identify? 

Since you can see the pause in MSFS, in ProcMon with flight simulator excluded to cut down on the noise, do you see anything happen every 60 secs?  And since you know the exact moment, can you examine the events around that time?

Not sure what you have tried and how far you have gotten with this..

For the ProcMon trace, we only need the few seconds that surround the event, not the entire 60 secs when nothing bad happens... If you can pinpoint it, I am sure we would love to see that section and attempt to identify.

3 hours ago, Jack_Sawyer said:

Back in July I saw some posts about this which is why I disabled it and it worked.  I enabled it and it came back.

What would be point of enabling it now as I'm getting the same pause as last summer.  

This may sound crazy, but enabling it again may actually help with troubleshooting.

Last time you had this happen, you disabled this and it was fixed, right?

What do things look like if you enable it again?  Once you have seen that, you can disable once more..

3 minutes ago, Bert Pieke said:

For the ProcMon trace, we only need the few seconds that surround the event, not the entire 60 secs when nothing bad happens... If you can pinpoint it, I am sure we would love to see that section and attempt to identify.

Thanks Bert.  I’m presently out in my wood shop ostensibly to get away from that electronic headache.

I very much like your suggestion, however I’m still not sure of the exact steps to exclude in ProcMon but as soon as I can learn it this is exactly what I’m gonna do.

1 minute ago, Jack_Sawyer said:

Thanks Bert.  I’m presently out in my wood shop ostensibly to get away from that electronic headache.

I very much like your suggestion, however I’m still not sure of the exact steps to exclude in ProcMon but as soon as I can learn it this is exactly what I’m gonna do.

When you get there, send me a PM... I am no ProcMon expert but surely we can figure this out.. 🙂

…..and once again, Mr. Pieke is ever helpful and generous with his time and talent. I remain impressed and grateful.

C