On 5/18/2019 at 1:57 AM, Nyxx said:

1) An AM to make P3D run on my main cores

Could you please elaborate?

I have 8 cores, how does this apply in practice?

 

 

If you have 8 real cores, no AM is required.

If you have 4 real cores (8 with HT on)

[JOBSCHEDULER]
AffinityMask=254

is a good choice.

I tried FIBER_FRAME_TIME_FRACTION=0.15 and it worked quite well. I've had a scenery that I downloaded somewhere, KOKC (Oklahoma City World Airport) and I normally fly out of an airport about 12 miles s. of there. (KWPA) and KOKC has always been full of black bldgs. when it comes into view. It doesn't do that since I change the fiber_frame thing. 

Using a set number like 0.15 is a nice compromise, but I'm sure that those using the FFTF Dynamic add-on are getting more efficient results because the FFTF number is changed over the course of the flight.

On 5/9/2019 at 9:22 PM, enrico10999 said:

In the past with the former versions there were useful tips here and on YT for tweaking the "prepar3D.cfg" file.

For example: 

[DISPLAY]
TEXTURE_BANDWIDTH_MULT=160 

I've found increasing TEXTURE_BANDWIDTH_MULT to the point of it no longer making a difference to the frame rate, is useful.

Surprisingly on my workstation I managed to increase the value to 960 before it no longer made any difference to the FPS.

Noting TEXTURE_BANDWIDTH_MULT and its value doesn't apply if you run P3D with a target frame rate of unlimited.

After reaching the max useful value I'm then able to set an internal P3D target of 30 FPS and have P3D actually maintain 30 FPS.

Quite a useful tweak IMHO.

Plus you can disable it by simply setting the P3D target frame rate to unlimited.

Cheers

Edited October 8, 20196 yr by Rogen