Word Not Allowed,

 

I noticed that even without the AffinityMask14, it seems that the 4 cores are under similar activity in the task manager.... hence, do we really need this tweak ?

 

thanks

Don't know, I only know that running 14 on the 8core machine (HT active on a quad) is wrong. Very wrong.

You're saying Bojote is wrong? Because that's the value I get from his site.

I tried 84 or 85 (can't remember) and even turning off HT but it didn't even change my FPS by 1.

 

What is MAX internal FPS?

What's BP_TOOLS?

FFTF how much?

I use Unlimited FPS in FSX, with UsePools=0. Not sure if I use FFTF or not. Should I?

 

Generally or yours?

Mine. I used to use external limiter with d9d3.dll, but since my FSAA injector uses another .dll, i'm not using it anymore. It works fine since FPS never are that high

I'm always willing to listen.. It's obvious you've been at this longer than I have so until I'm in your shoes I'm just a student.

 

Just did the Learjet test myself. 3,000ft 212kts and not a blurry in sight within the lod radius. :LMAO: With the limiter on the game was barely bothering to load the textures correctly. Like you I saw the blurries happening far out in front of me and would say "Yep, they aren't loading"... Then that area would be right under me and yep.. Still blurry.

 

This is beautiful and I'm still doing fine w/ framerates. I could probably tone it down a notch but all things considering in this very crowded area it was running and looking great.

 

 

So eventually are you using the Nvidia FPS limiter of the FSX one ?

You're saying Bojote is wrong? Because that's the value I get from his site.

I tried 84 or 85 (can't remember) and even turning off HT but it didn't even change my FPS by 1.

 

Not saying "Bojote is wrong". I am only saying that 14 is wrong for 8 threads CPU.

84 is correct.

It won't change the FPS in the slightest. Man, do I just love to repeat my explanations about everything - in every 2nd thread, I get to repeat each thing, over and over again. :Waiting:

 

I use Unlimited FPS in FSX, with UsePools=0.

 

Not the optimal combo, it's gonna work, but cause more stutters (at least for me) and blurries, as already confirmed by someone else (read the thread).

 

Not sure if I use FFTF or not. Should I?

 

Carefully, yes. But only if you decide to lock in the FSX. Not externally.

 

So eventually are you using the Nvidia FPS limiter of the FSX one ?

 

It doesn't matter. Both work the same way, both have absolutely same impact on FSX.

Not saying "Bojote is wrong". I am only saying that 14 is wrong for 8 threads CPU.

84 is correct.

It won't change the FPS in the slightest. Man, do I just love to repeat my explanations about everything - in every 2nd thread, I get to repeat each thing, over and over again. :Waiting:

 

 

 

Not the optimal combo, it's gonna work, but cause more stutters (at least for me) and blurries, as already confirmed by someone else (read the thread).

Okai I just find it weird that bojote's tool explicitly asks for the amount of threads, and then assigns affinitymask=14 for it??

What about affinity 85?

Well I guess you're right it won't affect FPS but might give more smooth gameplay. I haven't noticed many stutters though if my FPS is above 20.

 

I don't think I need to limit FPS since it's not going above 30 anyway. Or what would you recommend usepool, fftf, limiter, affinity wise? (specs in sig)

thanks

Ask Bojote on that one. I really can't answer that.

85 is not really optimal, as at supposedly puts main thread on the same core with windows threads, possibly causing little stutters. The reason for 84 is offloading main thread onto Core1.

You lose one texture thread though. Not a big problem though.

 

It's all about texture loading.

If you want, do following test:

Make a test flight which you are going to reload. A static one, not flying like default.

Then open FSX and load it once. Close FSX.

Set AM. Press load flight and measure seconds it takes to load it. Do that for each AM you wish to measure. I bet that fastest loading is going to be with 85 with HT on, and slowest with 14.

 

I don't think I need to limit FPS since it's not going above 30 anyway.

 

It's imperative to limit the FPS in FSX. For more info, read the thread and if you wish use what I recommended. Or search for hundreds of threads on discussions on affinitymask.

3000' over Vancouver Plus, with PNW, "Building Storms"

 

Silk...

 

[Graphics]

TEXTURE_MAX_LOAD=1024

 

[bufferPools]

PoolSize=0

 

[JOBSCHEDULER]

AffinityMask=14

 

[Display]

TextureMaxLoad=6

UPPER_FRAMERATE_LIMIT=27

TEXTURE_BANDWIDTH_MULT=87

 

[Main]

FIBER_FRAME_TIME_FRACTION=0.12

 

[TERRAIN]

AUTOGEN_DENSITY=5

DETAIL_TEXTURE=1

LOD_RADIUS=4.500000

MAX_DETAIL_TEXTURE_LEVEL=21

MESH_COMPLEXITY=100

MESH_RESOLUTION=22

MIN_DETAIL_TEXTURE_LEVEL=21

SWAP_WAIT_TIMEOUT=2

TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=907

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1376

TEXTURE_RESOLUTION=28

WATER_EFFECTS=6

 

[TrafficManager]

AIRPORT_SCENERY_DENSITY=1

AirlineDensity=29

ChangeTime=4.000000

FreewayDensity=14

GADensity=29

IFROnly=0

LeisureBoatsDensity=17

ShipsAndFerriesDensity=12

TransitionTime=4.000000

 

[sCENERY]

DAWN_DUSK_SMOOTHING=1

IMAGE_COMPLEXITY=5

LENSFLARE=0

MAX_ASYNC_BATCHING_JOBS=3

 

 

[DISPLAY.Device.NVIDIA GeForce GTX 580.0]

Mode=3840x1024x32

TriLinear=1

Okai I just find it weird that bojote's tool explicitly asks for the amount of threads, and then assigns affinitymask=14 for it??

What about affinity 85?

Well I guess you're right it won't affect FPS but might give more smooth gameplay. I haven't noticed many stutters though if my FPS is above 20.

 

I don't think I need to limit FPS since it's not going above 30 anyway. Or what would you recommend usepool, fftf, limiter, affinity wise? (specs in sig)

thanks

If I remeber correctly, the OLD guide does advise you to disable HT. It assumes you did. So the value would be 14. ******* migh find this thread and chime in.

Word Not Allowed,

 

PLease, what kind of settings do you have in the Nvidia inspector ?

 

as far as I'm concerned, it seems that I'm getting better results with :

 

- Limiter 35fps in FSX

- BP 0

- Fiber 0.15

- Affinity 14

 

I still have doubts on how to use the AA and especially the supersampling in the Inspector.... ( ihave a GTX 580 1.5)

 

Also, it seems that without the affinitymask 14, I still have the 4 cores running equally in the task manager.... should I still use the affinitymask 14 setting ?

 

THANK YOU

GREG

NI settings as per Ryan's thread, except I'm running 8xS + 2xSGSS.

 

it seems that I'm getting better results with :

 

I said previously something about "it seems" or "I think". Need to run controlled test scenarios.

 

In the end, if you are happy with how it runs, good for you!

 

Also, it seems that without the affinitymask 14, I still have the 4 cores running equally in the task manager.... should I still use the affinitymask 14 setting ?

 

If you have disabled HT, yes.

So, whats best HT enable or disable ?

Disable HT.

Glad I came upon this post, I have tried Kostas tip of setting the upper frame limit in the config, to 35, left nvidia inspector frame rate limiter as off but the display frame rates are still jumping over 50 for default aircraft. Shall I just ignore it ?

 

Before anyone asks I am running 2 monitors.

 

Thanks

 

Edited by mod. Please post relevant sections incl. tweaks. thx

Glad I came upon this post, I have tried Kostas tip of setting the upper frame limit in the config, to 35, left nvidia inspector frame rate limiter as off but the display frame rates are still jumping over 50 for default aircraft. Shall I just ignore it ?

 

 

[bufferPools]

Poolsize=0

RejectThreshold=131072 <------ You have no pools, so this line is redundant.

 

[GRAPHICS]

ForceFullScreenVSync=1

ForceWindowedVSync=1

HIGHMEMFIX=1

TEXTURE_MAX_LOAD=4096

TEXTURE_QUALITY=3

 

[TrafficManager]

AIRPORT_SCENERY_DENSITY=3

AirlineDensity=71 <------ This has large impact on fps, and could be reduced

FreewayDensity=20 <----- Ditto

GADensity=72 <----- Ditto

 

[DISPLAY.Device.NVIDIA GeForce GTX 560 Ti.0]

Mode=1920x1080x16 <---- Should be 32, to avoid 'banding'

TriLinear=1 <--- Good

 

[Weather] <------ All probably OK.

CLOUD_COVERAGE_DENSITY=8

CLOUD_DRAW_DISTANCE=3

DETAILED_CLOUDS=1

 

[Main]

FIBER_FRAME_TIME_FRACTION=0.1 <----- Add this line *****

 

[Display]

UPPER_FRAMERATE_LIMIT=35 <---- Reduce to 30

TEXTURE_BANDWIDTH_MULT=40 <--- This is exactly correct

TextureMaxLoad=30 <---- Important. Make this three, otherwise gpu is swamped.

 

[TERRAIN]

AUTOGEN_DENSITY=4

DETAIL_TEXTURE=1

LOD_RADIUS=4.500000

MESH_COMPLEXITY=100

MESH_RESOLUTION=25

SWAP_WAIT_TIMEOUT=2

TEXTURE_RESOLUTION=29

WATER_EFFECTS=4 <----- Make this 6

 

[sCENERY]

IMAGE_COMPLEXITY=5

 

Your TEXTURE_MAX_LOAD (4096), TextureMaxLoad (3), UPPER_FRAMERATE_LIMIT (30) and TEXTURE_BANDWIDTH_MULTIPLE (40) are inter-related and calculated using a formula, and are dependent upon values such as the target frame rate limit, that we know work.

Thanks Paul again, will give it a go.