So i have HT off on a 4790K OC to 4.7ghz  no AF Mask in cfg, SLI 2X gtx970.  im using process lasso to put a few addons on cores 1 & 3 keeping them off core 0, Now i do get a bit of slow texture loading , but sim is acceptably smooth with few micro stutters. I am using SimStarter NG which allows you to tweak the cfg from there, ive tried AF mask of 14 or 15 but didn't really make much difference, but would changing the FFTF make a difference to texture loading, (do find it hard to judge)  or would i be better too reduce OC & use HT on , then with a AF mask??  

  Cheers 

     Riche

So just to report back since applying SteveW's suggestion of AM=254 with HT enabled, and process lasso'ing addons to LPs 5-7. Everything seems smoothed out with just one instance of stutter on descent. This is also with FFTF at 0.2. That was a IFR flights with Aerosoft Airbus and Majestic Dash 8. Will check tonight VFR responsiveness.

I too am running 254/HT on with no problems.

Fresh install with no addons tho'.

I quote the OP :

" But one thing I noticed last night while trying out my new Orbx Norway scenery is that the tiles when flying over top load but load slow and tend to keep sharpening."

This (late switching to the highest resolution mip-map - the switch seems set to a fixed shorter distance (<1 mile) than ever before) tile sharpening problem is the issue that I noticed myself when flying through the Grand Canyon (like the Norway scenery - steep slopes nearby) low over the river. I was able to bounce between version 3.0 and 3.2 (I have a dual boot Windows system) and was able to confirm that this particular problem only started with 3.2. No amount of adjusting AM, LOD, or FFTF (etc)seems to change this particular issue in any way - it isn't quite like the normal blurries. I would categorize it as a v3.2 bug but then L-M might have a different viewpoint. Maybe some sort of mip-map bias issue??

P3D gives us full control over our use of hyperthreading (it breaks into as many threads as we have logical processors), with the jobscheduler AffinityMask being utilised exactly as we determine. FSX is different, and FSX-SE takes control unless we control it with an external app. So presently P3D is provided with a professional approach to setup, allowing us to do what we want.

 

Regarding the unmasking of more than four LPs gives us more scenery collecting threads; If we set up too many scenery collecting LPs than we actually need to support that scenery, those will instead reduce our loading performance. If we start P3D and choose to load another scenario, we can use a stopwatch to time just how long it takes to arrive at the flight, and compare with other configurations.

I quote the OP :

" But one thing I noticed last night while trying out my new Orbx Norway scenery is that the tiles when flying over top load but load slow and tend to keep sharpening."

This (late switching to the highest resolution mip-map - the switch seems set to a fixed shorter distance (<1 mile) than ever before) tile sharpening problem is the issue that I noticed myself when flying through the Grand Canyon (like the Norway scenery - steep slopes nearby) low over the river. I was able to bounce between version 3.0 and 3.2 (I have a dual boot Windows system) and was able to confirm that this particular problem only started with 3.2. No amount of adjusting AM, LOD, or FFTF (etc)seems to change this particular issue in any way - it isn't quite like the normal blurries. I would categorize it as a v3.2 bug but then L-M might have a different viewpoint. Maybe some sort of mip-map bias issue??

 

yes I noticed this too!!

Me too, especially noticable when using photo scenery. Textures become sharper the closer you get, but in v3.2 at low speed. That was better in v3.0.

On 5/3/2016 at 1:31 PM, TheBoom said:

Yet another thread describing blurries in P3D 3.2. I hope LM are taking note.

 

FFTF determines the amount of processor overhead going to scenery rendering as opposed to other tasks. The lower it is the worse the scenery loading is going to be. Hence setting it to 0.1 is the reason you think it doesn't help.

 

You will need a value of around FFTF 0.5 minimum. Using an external fps lock with the FFTF value seems to help alleviate the blurries in 3.2.

 

If you still see blurries try TML=60 and reduce if you see white flashes.

 

Do note that both the above tweaks can cause stuttering and fps loss. It's a trade off between visual quality and performance with 3.2.

 

Moving the scenery off an SSD to a HDD will increase initial loading times but should not affect scenery rendering on the go.

If I may,, could someone clarify what the TML=60 is referring to?? I'm aware of TextureMaxLoad, but not certain if that is correct.

thx,

Mike