4 hours ago, Dreamflight767 said:

Interesting observation if someone could please test.

Installed an AM into my p3d.config.

Whenever I add/install a new paint for FSLABS, I always get a box that says "restart P3D" after I try to open P3D.

I opened my p3d.config today to look at something and noticed a ";" in front of the AM line.

Does FSLABS turn-off/disable AM settings?

Thanks.

Yes, if you don't stop it.

How can we stop this ?

 

 

Edited June 28, 20214 yr by f.skywalker

"Optimise FSLabs products CPU usage policy" is extremely vague. I would not be amused at all if an external program changed my AM settings.

How do they know "optimising" is suitable for all CPUs irrespective of whether Hyperthreading is enabled or not?

1 minute ago, f.skywalker said:

How can we stop this ?

Untick the option.

Untick the two boxes and click on Continue. You will only see this once. Advice from another user is always good.

Edited June 28, 20214 yr by Reader

The window is not more showing by me.

I buy the FSLABS 2 days ago.

 

 

Frank

Edited June 28, 20214 yr by f.skywalker

18 minutes ago, f.skywalker said:

The window is not more showing by me.

I buy the FSLABS 2 days ago.

 

 

Frank

Goto <Where you pointed the FSLabs installer> \FSLabs\A320\Data and delete the file UMPolicy.

24 minutes ago, Ray Proudfoot said:

"Optimise FSLabs products CPU usage policy" is extremely vague.

From the Installation Guide: 

Optimise FSLabs products CPU usage policy – This option optimises the CPU core usage of the A320-X software according to the CPU configuration available. This will only affect FSLabs own files and will not change any P3D settings.

@SierraDelta, still vague. Why don't they say precisely what settings they are changing?

[JOBSCHEDULER], AffinityMask is a setting in the prepar3d.cfg file so if they're changing something in that then they are manipulating your cfg file.

This discussion really should be taken to their forum.

The question was asked about fps limit at 28fps or 29fps vs 30fps or 31fps for 30 or 60Hz refresh, and whether 60Hz or 120Hz could be better than 30Hz.: 

 

Overall it is better to set the GPU to output frames just below the refresh frequency because you see the same amount of frames without wasting extra CPU throughput. unless you really do want a higher fps then you use more throughput to see more frames anyway. 

 

A problem with external limiters is that they cannot maintain accurate fps because each frame takes a different time to complete, so by setting a limit of 28 I will actually see a wobble around perhaps 26 to 30 or wider.

Only the internal target frequency slider outputs at a predetermined interval that is not concerned with time to build frames, even then it would be better to limit to 29 for 30Hz refresh to be sure we do not lose frames.

 

Let's leave the monitor at 60Hz or 120Hz and limit the fps to 30fps:

The maximum wait time for the next buffer to display is half at 60Hz and a quarter at 120Hz so more of those buffers uploaded are displayed. So with faster refresh the monitor will always have less time before it displays the next uploaded buffer.

 

In more detail, let's look at what 28fps and 29fps limit gives us vs 30fps:

With 28fps 1/28 = 0.0357s interval, 1/30 30fps = 0.0333s interval = 0.0024s difference which is very small.

30/28 x 100 = 107%. 7% more throughput is required to do 30fps compared to 28fps so if we have a 5GHz CPU, at 28fps we are making 5 x 107% equivalent to 5.35GHz, or roughly 0.93 x 5 = 4.65GHz required to do 28fps. A free CPU boost of 6 to 7%.

At 29fps that's around 3% gain of throughput available, giving higher settings or more overhead keeping our fps up above the refresh.

 

...and looking at 29fps vs 31fps for a 30Hz refresh:

At 31fps limit we are sending extra frames which are all lost because the monitor is already showing the last frame for the 1/30s, the frame arriving early is ignored and the wait is now for the next frame. so the wait is 1/30s + the time remaining from the last frame interval

At 29fps no frames arrive early so all are displayed, however the the maximum waiting time after the buffer is uploaded is 1/30 x 1/30 = 0.0011s, a very small wait for the next buffer, or at 28fps 2/30 x 1/30 = 0.0022s still a small wait.

Overall there will be less long frames setting the GPU to output at or just below the monitor frequency. If the fps limit is set beyond the refresh frequency to 32, the uploaded frame is showing in the next refresh so we are now limiting at 31fps anyway using up 3% bandwidth.

 

 

 

 

 

1 hour ago, Ray Proudfoot said:

I've just run this test and compared it to my 30Hz setting. With 60Hz and an internal frame rate limiter set plus the FIBER entry 30fps was maintained throughout my circuit around EGCC using UK2000 Manchester in a Carenado PC12. But there were lots of micro-stutters and it was definitely not as fluid as 30Hz. The fact that core0 stayed on 100% throughout was probably the reason.

In contrast, flying the same circuit with 30Hz and unlimited and no FIBER entry the core0 averaged in the high 50s / low 60s. 30fps was maintained of course and it felt a lot smoother especially during turns but straight line flying was also as good as it gets. Smooth as a baby's bottom! 😁

That suggests a lot of work is being done internally to maintain 30fps rather than letting the hand brake off in P3D (unlimited) and controlling the fps externally with the monitor refresh rate.

I've turned TripleBuffering off as an experiment and haven't noticed any deterioration in performance. If you're in the market for a new monitor I really would recommend one with 30Hz.

Thank you for your test!  A 100% load on core0 was expected, because this is how it usually works with limiting the fps internally. I am not sure if it is correct to conclude that this load causes microstutters (because there are many other users who have smooth running sims while limiting the fps internally), but if it runs well on your system, then it shall have power!

2 minutes ago, Afterburner said:

Thank you for your test!  A 100% load on core0 was expected, because this is how it usually works with limiting the fps internally. I am not sure if it is correct to conclude that this load causes microstutters (because there are many other users who have smooth running sims while limiting the fps internally), but if it runs well on your system, then it shall have power!

Yes, I've seen 100% on core 0 with smooth performance. But this was different and if you'd sat here and seen it yourself you would have noticed the difference. Are you considering a new monitor?

15 minutes ago, SteveW said:

The question was asked about fps limit at 28fps or 29fps vs 30fps or 31fps for 30 or 60Hz refresh, and whether 60Hz or 120Hz could be better than 30Hz.:

So :

30 hertz / Vsync On / NVCP limiter to 29 or 30 ?

Edited June 28, 20214 yr by Ray Proudfoot
Long quoted post mostly removed.

16 minutes ago, GSalden said:

So :

30 hertz / Vsync On / NVCP limiter to 29 or 30 ?

I would try 29! Or even 28 first ))

9 minutes ago, GSalden said:

So :

30 hertz / Vsync On / NVCP limiter to 29 or 30 ?

If your monitor is 30Hz refresh with vsync the monitor is showing each frame at intervals of 1/30second. Then every frame sent ahead of that interval will be ignored since it is still showing the last frame. Setting to 29 can reduce the number of frames ignored and gives you 3% bandwidth on average. However, the actual frame to frame time is not consistent, you may see 34 or 26 on the display from time to time, you get an averaged result slightly better overall.