Well, not good news gents. I ran another session tonight with EA off and unfortunately, got the stuttering after 1 hour in the sim. Again, this was with EA off.  I did not notice any frame rate fluctuations though; they stay in the upper 20's while the stuttering occurred. I know we thought it was tied to EA being on but apparently that is not the case it would seem. Something is seriously buggered for sure. I work many hours and don't have the time to test this further. I will be rolling my client back to 5.2. Hope LM can get it figured out. 

Sorry to hear. Do you have to go back all the way to 5.2. Wouldn’t pre he 5.3 work?

56 minutes ago, micstatic said:

Sorry to hear. Do you have to go back all the way to 5.2. Wouldn’t pre he 5.3 work?

Latest 5.2 client, keeping 5.3 content and scenery. 

3 hours ago, B777ER said:

Well, not good news gents. I ran another session tonight with EA off and unfortunately, got the stuttering after 1 hour in the sim. Again, this was with EA off.  I did not notice any frame rate fluctuations though; they stay in the upper 20's while the stuttering occurred. I know we thought it was tied to EA being on but apparently that is not the case it would seem. Something is seriously buggered for sure. I work many hours and don't have the time to test this further. I will be rolling my client back to 5.2. Hope LM can get it figured out. 

Could this be related to the Nvidia Driver (497.29)?

30 minutes ago, mpo910 said:

Could this be related to the Nvidia Driver (497.29)?

No, this was reported before the release of 497.29

50 minutes ago, mpo910 said:

Could this be related to the Nvidia Driver (497.29)?

I think not. I had it with 496.13.

Just "updated" to 496.49 (need to do it step by step cause with newer versions all my games are unsharp) and did 2 flights without the issue.

I remember that I read that for some with 5.3 (without HF) this did not happen. Its the question wat has change between those 2 version what can potentially cause those behaviour.

I thought I had solved the issues after several days of no issues and then on final approach into Zurich just now in the FSLabs A320 using EA and vol clouds 5.3 HF1+1 I got the slide show frame rate followed by a CTD. Windows event viewer shows a terrain.dll fault.

29 minutes ago, simfan1983 said:

I thought I had solved the issues after several days of no issues and then on final approach into Zurich just now in the FSLabs A320 using EA and vol clouds 5.3 HF1+1 I got the slide show frame rate followed by a CTD. Windows event viewer shows a terrain.dll fault.

If you have AutoSave in a paid version of FSUIPC try loading the earliest saved flight if you think it would have been before the problem started.

If it is earlier keep everything the same and see if the problem is repeated. Always tricky as data stored in RAM won't be the same on a reloaded saved flight as the original. But it's worth a try.

5 hours ago, mpo910 said:

Could this be related to the Nvidia Driver (497.29)?

If that is the newest one, I don't have that installed. 

9 hours ago, B777ER said:

Latest 5.2 client, keeping 5.3 content and scenery. 

I hear you.  I'm just saying that these problems (atleast for me) started with 5.3HF, not 5.3.  So it would seem we could go back to 5.3 client instead of 5.2. 

1 hour ago, Ray Proudfoot said:

If you have AutoSave in a paid version of FSUIPC try loading the earliest saved flight if you think it would have been before the problem started.

If it is earlier keep everything the same and see if the problem is repeated. Always tricky as data stored in RAM won't be the same on a reloaded saved flight as the original. But it's worth a try.

I do have an autosave but I've decided to re-fly the flight after clearing shaders and appdata\local\temp folder. Prior to the flight I did tweak some graphics settings and the other difference from my normal routine was that I started all my secondary apps before P3D. Usually I start P3D first - I don't know if that makes a difference (using Process Lasso) but will see if I get a recurrence. It's a bit annoying but the first issue I've had for 40+ hours of flying.

51 minutes ago, micstatic said:

I hear you.  I'm just saying that these problems (atleast for me) started with 5.3HF, not 5.3.  So it would seem we could go back to 5.3 client instead of 5.2. 

it started with 5.3 here - strangely enough i am still not able to replicate it with the FSL with HF1 and 1+1.

I do have some Chaseplane minor stutters on takeoff roll and when moving camera in cruise but this is not the issue at all.

btw i just switch to FSUIPC 6.1.7 as i was on 6.1.2 it seems

Michael Moe

Edited December 28, 20214 yr by Michael Moe

35 minutes ago, simfan1983 said:

I do have an autosave but I've decided to re-fly the flight after clearing shaders and appdata\local\temp folder. Prior to the flight I did tweak some graphics settings and the other difference from my normal routine was that I started all my secondary apps before P3D. Usually I start P3D first - I don't know if that makes a difference (using Process Lasso) but will see if I get a recurrence. It's a bit annoying but the first issue I've had for 40+ hours of flying.

Not a long flight I trust. Doesn't PL alter your AM settings? Check prepar3d.cfg as the ones inserted by P3D should be your reference.

Starting supporting apps before or after P3D shouldn't make any difference.

14 minutes ago, Ray Proudfoot said:

Not a long flight I trust. Doesn't PL alter your AM settings? Check prepar3d.cfg as the ones inserted by P3D should be your reference.

Starting supporting apps before or after P3D shouldn't make any difference.

Flight duration is 2 hours 46 minutes and it was on short final that it all went haywire. I was too fast and trying to slow down and I've seen these symptoms before in 4.5 in the FSLabs where you disengage autopilot and are not properly configured so it may be nothing to do with 5.3.

I've always found that starting P3D first was better - not sure if it's to do with memory allocation or whatever - I know it shouldn't make any difference but if I don't do that I seem to have more issues. Usually I start Chaseplane, then P3D, then everything else.

@simfan1983, ouch! Are you sure you don't want to try a FSUIPC saved flight option?

I use SimStarterNG to launch related apps. It's configured to start most when P3D is fully running. But that's not your problem. That's why I suggested reflying from a save. You know the problem was generated at some point in that flight.