I found some threads from last year discussing issues with Coherent GTDraw and effects on performance but they were not similar to the issue I have currently been experiencing.  I have generally satisfactory frame rate but with the A320NX I experience a repeating stutter about every four seconds.  

Looking at the FPS Display under dev mode, the stutter is perfectly timed with a red drop of the Coherent GTDraw parameter for a split second every four seconds or so.  I've tried messing with various graphical settings and while that will alter my average FPS, no setting I have messed with will get ride of this particular stutter.  I've tried low settings, high settings, adjusting various options individually, etc.  Also, when I move to an external view, the GTDraw parameter goes to 100% green with no red dips and hence I get no stutter.

Has anyone experienced this particular issue in the A320NX (or any aircraft for that matter) that can provide some possible solutions to test?

At this point, just wait for July 27th. This issue should be resolve completely. 

9 minutes ago, rjack1282 said:

I've tried messing with various graphical settings and while that will alter my average FPS, no setting I have messed with will get ride of this particular stutter.

This is because this stutter will be coming from either code within the avionics or from the JS engine itself (potentially garbage collection). The only cure is for the code to be optimized to avoid that sporadic load. The upcoming SU5 has also optimized the interop between Coherent and the main simulator threads such that these types of dips won't really affect the sim nearly as much, and has optimized other parts of the way JS instruments are run which reduce stutters. This should hopefully improve the situation without external dev work required.

-Matt | Working Title

I had this, it was driving me crazy, I fixed it by removing all addons form community folder until it gets resolved.

1 hour ago, rjack1282 said:

 I have generally satisfactory frame rate but with the A320NX I experience a repeating stutter about every four seconds.

Same here. I tried everything but couldn't get rid of the stutters. That's why I completely gave up flying the FBW A320. Instead I fly the Aerosoft CRJ now which is totally smooth.

I miss the Airbus though, so I hope SU5 will allow FBW to remove these massive stutters.

I have this often with the WT G3000.  No roads package and glass refresh to medium.  Start at 25 ish fps and finish a flight at 10 fps.

Stutters can be the result of relying too much on the cpu. Asobo is fixing that so the sim is more reliant on the gpu. I think they even cut the ram usage down from 16gb to 4.7gb in the last twitch. You need to turn up gpu intensive settings until you are gpu bound. That will help. July 27th will help even more i hope!

Both my main thread and gpu are solid green on high end settings and FPS display says I'm gpu bound already.  5800x and 2080.  The only dip is GTDraw consistently every 4 seconds.

Try turning odd Online Live Traffic and AI Traffic.  That fixed my stutter every 60 seconds problem.

My experience is not the same as the OP. This is what I have experienced a few days ago. All of a sudden on a longer flight the FPS would gradually start dropping to the low teens with stutters and with that also the GPU load to below 40 %.   Could not understand - why this all of a sudden ?.

Started by taking out some mods from the community folder and low and behold the problem was caused by a mod which I have updated a day before. It was a very time consuming process to track down the culprit. Just thought I would share my story.

Have a great weekend and July 27th is not far off !! 

26 minutes ago, SAPilot said:

My experience is not the same as the OP. This is what I have experienced a few days ago. All of a sudden on a longer flight the FPS would gradually start dropping to the low teens with stutters and with that also the GPU load to below 40 %.   Could not understand - why this all of a sudden ?.

Started by taking out some mods from the community folder and low and behold the problem was caused by a mod which I have updated a day before. It was a very time consuming process to track down the culprit. Just thought I would share my story.

Have a great weekend and July 27th is not far off !! 

Could you tell us the name of the mod you removed please?  It might help other people with the same problem.

Edited July 10, 20214 yr by bobcat999

24 minutes ago, bobcat999 said:

Could you tell us the name of the mod you removed please?  It might help other people with the same problem.

I think it was this mod

https://flightsim.to/file/14925/input-viewer

I have not notified the author, because I want to do a final test today to verify my findings. Fly same route and same aircraft.

Note : As of today the mod only has 684 downloads.

I don't use that mod.

Happens the worst in the TBM9 and C700

50 minutes ago, ryanbatcund said:

I don't use that mod.

Happens the worst in the TBM9 and C700

Was it with that mod ?.

I have tested again today with the mod installed and is 99% sure - [C208]

Left a message for the author on flightsim.to 

Quote

Posted by, virtuali

It means whatever is limiting fps, comes from one of the many things done by the CPU ( like AI traffic, road traffic,  flight model, streaming data, etc. ), not pure rendering.

Note that, if you lower the relevant settings so that you could not be limited by the CPU, it's possible the counter would then say "limited by the GPU", because that message indicates the 1st most limiting thing at any time.

The dev mode fps counter has an "ideal" target, that is 60 fps, or 16.67 ms of rendering time. If you keep an eye on the rendering times for each item ( MainThread, CoherentGT, GPU, etc. ), each one will be shown in GREEN, as long it stays under 16.67 ms. If all items are below that, the big fps counter itself will turn green, meaning you are in the ideal situation.

Coherent GT time, is the impact of 2D graphic, like glass cockpit instruments, the Vfr map, and even the overlays on screen when you go in outside view. You'll notice it goes to almost 0 if you are in "Drone Camera" mode, where no 2D elements are present on screen, no instruments or overlays.

 

 

Edited July 10, 20214 yr by Waldo Pepper