After checking seems like my core 0 is at 100%...

Interesting thread.  I have an 8086K and a 1080ti and with the PMDG 777 at the gate with FBs KSFO and mid to high settings the best fps I can get is in the mid 40s.  Now this with twin monitors both at 4K (one for P3D and the other for ancillary stuff) and Orbx NoCal but if dropping a 9900K or 9900KS onto my ASUS Extreme XI MB would give me a boost to 60 fps I would be tempted.  However I suspect there may more to it.

Bruceb

My two year old rig seems like something out of the dark ages compared to you folks. Argh!

19 hours ago, Le Français said:

After checking seems like my core 0 is at 100%...

Go into task manager go into affinity mask for P3d and uncheck core 0 then check mark it again.

Old  trick that works.

but you have to do it each time you run the sim.

44 minutes ago, mikeymike said:

Go into task manager go into affinity mask for P3d and uncheck core 0 then check mark it again.

Old  trick that works.

but you have to do it each time you run the sim.

I find this doesn’t really work. There’s nothing wrong with high core 0 usage. P3D is designed for that because the first core is assigned the heaviest hitting task for rendering. I find messing with the affinity after the program is started is a good way to get blurries and instability (crashes). If your framerate is ok but core 0 usage is high, this is fine. When performance is suffering and it’s pegged at 100% then that means you are asking too much from the sim and need to lower settings or you are just at a poorly optimized scenery which you can’t do anything about.

3 hours ago, JasonPC said:

I find this doesn’t really work. There’s nothing wrong with high core 0 usage. P3D is designed for that because the first core is assigned the heaviest hitting task for rendering. I find messing with the affinity after the program is started is a good way to get blurries and instability (crashes). If your framerate is ok but core 0 usage is high, this is fine. When performance is suffering and it’s pegged at 100% then that means you are asking too much from the sim and need to lower settings or you are just at a poorly optimized scenery which you can’t do anything about.

I have tested and found that it works for me.

as It eliminates the slight stutter.

 

 

2 hours ago, mikeymike said:

I have tested and found that it works for me.

as It eliminates the slight stutter.

You might want to check your affinity mask as it may mean your core 0 has another process running causing the stutter and by unticking core 0 you have just moved the task to another core.

I use process lasso to make all apps beside P3D not use core 0. I set P3D’s config file so that the affinity is only using physical cores and not HT cores as I find this splits up the load inefficiently on Core 0 though it does make loading times slower.

Edited December 27, 20196 yr by JasonPC

2 hours ago, JasonPC said:

 

You might want to check your affinity mask as it may mean your core 0 has another process running causing the stutter and by unticking core 0 you have just moved the task to another core.

I use process lasso to make all apps beside P3D not use core 0. I set P3D’s config file so that the affinity is only using physical cores and not HT cores as I find this splits up the load inefficiently on Core 0 though it does make loading times slower.

I do use process lasso

will give that a try, thanks for the feedback.

Locked fps on the slider is like unlimited in that as soon as one frame is made it starts on the next. It makes look-ahead frames. So to make three look ahead frames 60fps would make setting 20fps on the slider pretty good. We can set 30 fps if we see more than 30 with unlimited VSync=off. However small fluctuations mean that the look ahead is always depleted and the expense of the look ahead is wasted making it hard on the system. So locked is more often good for setting at for example 20-24fps when we set Unlimited VSync=Off we can see more than 40 fps. Otherwise locked might not work too well. With a fast system and 4k monitors Locked and VSync = on can create stutter. If we keep VSync=Off we might see some shifted areas of the scene instead of stutter.

Alternatively we use Unlimited VSync=On which steers output frequency to the refresh rate of the monitor.

So when we see discussion of FFTF and AMs we know that these make a difference. The way the sim works should be considered that there's an fps part coupled to a back end part that is paralleled to complete loading file more quickly. Windows resources are highly multithreaded and respond in such a way as to for example load files quicker as we add cores. Up to a point since the system can only deliver its own maximum. If we use too many cores or LPs, where we don't see much of an improvement loading files, then we could be using too many when we have the fps part still expecting access to maximum resource throughput.. It's a starting point, a reasonable metric to bear in mind. The sim fills in to a certain point each frame and when there is overhead in the system this fill in can be more efficient. So with an 8 core we might find it works smoother on 6 and set so that there's a little overhead. Even though all 8 will load the scenario more rapidly it might detract from the smoothness.

Edited December 28, 20196 yr by SteveW

11 minutes ago, SteveW said:

Locked fps on the slider is like unlimited in that as soon as one frame is made it starts on the next. It makes look-ahead frames. So to make three look ahead frames 60fps would make setting 20fps on the slider pretty good. We can set 30 fps if we see more than 30 with unlimited VSync=off. However small fluctuations mean that the look ahead is always depleted and the expense of the look ahead is wasted making it hard on the system. So locked is more often good for setting at for example 20-24fps when we set Unlimited VSync=Off we can see more than 40 fps. Otherwise locked might not work too well. With a fast system and 4k monitors Locked and VSync = on can create stutter. If we keep VSync=Off we might see some shifted areas of the scene instead of stutter.

Alternatively we use Unlimited VSync=On which steers output frequency to the refresh rate of the monitor.

So when we see discussion of FFTF and AMs we know that these make a difference. The way the sim works should be considered that there's an fps part coupled to a back end part that is paralleled to complete loading file more quickly. Windows resources are highly multithreaded and respond in such a way as to for example load files quicker as we add cores. Up to a point since the system can only deliver its own maximum. If we use too many cores or LPs, where we don't see much of an improvement loading files, then we could be using too many when we have the fps part still expecting access to maximum resource throughput.. It's a starting point, a reasonable metric to bear in mind. The sim fills in to a certain point each frame and when there is overhead in the system this fill in can be more efficient. So with an 8 core we might find it works smoother on 6 and set so that there's a little overhead. Even though all 8 will load the scenario more rapidly it might detract from the smoothness.

So basically with my i9 9900k I should turn vsync off?

 

i have a 60hz refresh rate  4k 55inch tv 

with a locked fps at 30.5fps in inspector

unlimited fps with Triple buffer on and vsync on.

13 minutes ago, SteveW said:

Locked fps on the slider is like unlimited in that as soon as one frame is made it starts on the next. It makes look-ahead frames. So to make three look ahead frames 60fps would make setting 20fps on the slider pretty good. We can set 30 fps if we see more than 30 with unlimited VSync=off. However small fluctuations mean that the look ahead is always depleted and the expense of the look ahead is wasted making it hard on the system. So locked is more often good for setting at for example 20-24fps when we set Unlimited VSync=Off we can see more than 40 fps. Otherwise locked might not work too well. With a fast system and 4k monitors Locked and VSync = on can create stutter. If we keep VSync=Off we might see some shifted areas of the scene instead of stutter.

Alternatively we use Unlimited VSync=On which steers output frequency to the refresh rate of the monitor.

So when we see discussion of FFTF and AMs we know that these make a difference. The way the sim works should be considered that there's an fps part coupled to a back end part that is paralleled to complete loading file more quickly. Windows resources are highly multithreaded and respond in such a way as to for example load files quicker as we add cores. Up to a point since the system can only deliver its own maximum. If we use too many cores or LPs, where we don't see much of an improvement loading files, then we could be using too many when we have the fps part still expecting access to maximum resource throughput.. It's a starting point, a reasonable metric to bear in mind. The sim fills in to a certain point each frame and when there is overhead in the system this fill in can be more efficient. So with an 8 core we might find it works smoother on 6 and set so that there's a little overhead. Even though all 8 will load the scenario more rapidly it might detract from the smoothness.

So basically with my i9 9900k I should turn vsync off?

 

i have a 60hz refresh rate  4k 55inch tv 

with a locked fps at 30.5fps in inspector

unlimited fps with Triple buffer on and vsync on.

Inspector do you mean limited to 30.5? If the monitor tests to 60 exactly then use 29.5.higher puts a frame lost since it is arriving a little early. Excess frames are not shown. and you would gain 1/30th throughput.

When I mention locked FPS that's on the slider in Display Settings that's nothing to do with settings in NCP.

VSync=Off+Unlimited shows us the maximum fps capacity at that setup.

VSync=On +Unlimited gives us the refresh frequency.

Locked fps on the slider try VSync=On or Off. Depends on your setup.

 

 

It is counter intuitive maybe but, with a 60Hz monitor and VSync at 60Hz it is easier to grasp. When the monitor has a free buffer it can receive the next frame. If it is not ready that frame passes by. So if we are only a little early, call it 1/60s, that is not accepted as the buffer still has a frame in hand for 1/60s. Then the next frame from the GPU might be 59/60ths second away yet, so the monitor might even pass another frame before accepting the next frame from the GPU. When running 30 locked the 60Hz monitor shows each frame approximately twice. When looking carefully at fps changes it becomes evident that 61 vs 60 sent to a 60Hz monitor is a zigzag, but 59 is smooth and is a shorter line. If limiting at half refresh (30) then choose 29 or maybe 29.5. In fact when the monitor is checked it might be 58.78 or 62.23 anyway rather than bang on 60. So we actually need to check between 59 and 61 on the test because we can't say that a 60Hz monitor is bang on 60 therefore we do not simply set to half 60, and not faster than, or we end with longer frame waits.

 

Edited December 28, 20196 yr by SteveW

1 hour ago, SteveW said:

Inspector do you mean limited to 30.5? If the monitor tests to 60 exactly then use 29.5.higher puts a frame lost since it is arriving a little early. Excess frames are not shown. and you would gain 1/30th throughput.

When I mention locked FPS that's on the slider in Display Settings that's nothing to do with settings in NCP.

VSync=Off+Unlimited shows us the maximum fps capacity at that setup.

VSync=On +Unlimited gives us the refresh frequency.

Locked fps on the slider try VSync=On or Off. Depends on your setup.

 

 

Correct, limited to 30.5

will 29.5

slider in sim unlimited 

will try also with vsync off and triple buffer off

and test 

thank you