A new tweak against blurry ground textures

[justpassingthrough]

NickN mentioned that depending on the graphics card/drivers being used the setting will work but upon closing the sim it may be erased from the config file and must be edited back in. Some cards/drivers will allow the setting to remain written to the config where others may not. He also said if graphics detail sliders are changed it may reset the edit.

I'm just going to confirm this. I put in this tweak and then changed settings, it is no longer there.

And what is all of this talk that "0.9 brings a system to it's knees" I'm running a fiber of 1.00, I get 10-20 fps but it is constant and little to no "popping". The odd pop is worth it though, my textures are always crisp.

Well

Its possible the value must be between .01 and .99

A value of 1.0 may very well be ignored and default to the .33 value the system recognizes without the entry in the config file.

I do know that if a value is placed in the config file that is out of range of what the sim understands, the sim will default to its pre-programmed value

Set it to 0.90 and see if you still have a frame rate. If not, the 1.0 value is no good and you are actually running .33

Also make sure the syntax is correct and there are no misspellings or spaces in the line.

FIBER_FRAME_TIME_FRACTION=0.90

[kilotango]

Well, again.
I've been over a lot fiber frames changing. From .001 till .4. I dont see much good or bad in flight.
But what makes a diff. is the mesh, tex and auto gen balance! (Ok, admit the traffics has a lot to say. Mine is at 40%).
Sorry to say it again, but miltestpilot, i think youre right.
When the tex a.o. are set specific (higher), then fiber frames are out of work. I can set it to 3.0 without truble.
Now i think wee are approaching something!
Will be back.

[Wingo]

NickN mentioned that depending on the graphics card/drivers being used the setting will work but upon closing the sim it may be erased from the config file and must be edited back in. Some cards/drivers will allow the setting to remain written to the config where others may not. He also said if graphics detail sliders are changed it may reset the edit.

I'm just going to confirm this. I put in this tweak and then changed settings, it is no longer there.

And what is all of this talk that "0.9 brings a system to it's knees" I'm running a fiber of 1.00, I get 10-20 fps but it is constant and little to no "popping". The odd pop is worth it though, my textures are always crisp.

Well

Its possible the value must be between .01 and .99

A value of 1.0 may very well be ignored and default to the .33 value the system recognizes without the entry in the config file.

I do know that if a value is placed in the config file that is out of range of what the sim understands, the sim will default to its pre-programmed value

Set it to 0.90 and see if you still have a frame rate. If not, the 1.0 value is no good and you are actually running .33

Also make sure the syntax is correct and there are no misspellings or spaces in the line.

FIBER_FRAME_TIME_FRACTION=0.90

Oh ouch, you're right.... A value of 1 isn't recognised. Just set it to .99 and I couldn't even fly the plane. I think I'll set it a little lower

EDIT - Scrap that, It as a bung Pool size value... i dont think 100,000,000 is a good value Just tested again and 0.99 works fine, I'll have a look at .90 just in case

[justpassingthrough]

pool size for 512 cards can be 5000000. a value of 10000000 is easy for any 8800 series card. Most prefer 2500000

What video card and system are you using? A fiber frame of over .60 makes mine crawl like a turtle. Are you using hacks of some type?

If you are not running a 8800 video card and are able to run a .99 fiber frame I have to question if the line is either typed incorrectly or in the wrong place in the config file. Even with an 8800 series card, a .99 fiber frame means the sim is placing twice the resources into scenery than it is into developing frames which makes no sense.  :-? I assume you are running with sliders fairly high?

[kilotango]

I've just removed my post here.

[M.R.Maiornikov]

What pool size and fiber_frames you guys think i should use for my 7800GT vid card?

[justpassingthrough]

I cant speak for other cards but I would try a fiber frame of 0.25-0.27 and a pool size of 2500000. If your running 512mb on the video memory you may be able to increase the pools to 10000000.

Setting fiber frame is a to-taste thing. Some people prefer sharp ground scenery where others could care less and prefer frames. Lower than 0.21 is probably going to give muddy ground textures IF the sliders are pushed up for autogen and other items. Its all about tweaking based on the system and how high the sliders are set.

What I learned was to get the visuals to where I want them first, then work the other numbers to bring frames up. I also have to be realistic in that and know that my components will only do so much so if its not possible to obtain a visual scenery slider setting and trimthe frames to where it works I have to drop the scenery/autogen sliders and retweak.

Its best to tweak in a medium size city area such as Seattle because once you have that dialed in, flying outside in the country or airborne at altitudes is prettly much always smooth. Larger cities such as New York are going to choke it anyway unless you have a monster video card.

I can post what I use but it probably not work for lesser systems.




[Display]
BLOOM_EFFECTS=0
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=80 //250 works well if i drop autogen and other sliders a notch. try betwen 80 and 250
UPPER_FRAMERATE_LIMIT=18
WideViewAspect=True// only works for widescreen, set to FALSE for non widescreen displays


[Main]
DisablePreload=1
FIBER_FRAME_TIME_FRACTION=0.25
UPPER_FRAMERATE_LIMIT=18 //note.. FSX has a problem with the frame counter I was told it can be off by as much as 5 frames (reads lower than it actually is) set to 20-22 if not flying in city areas

[GRAPHICS]
SHADER_CACHE_PRIMED=1
TEXTURE_MAX_LOAD=1024
NUM_LIGHTS=8
AIRCRAFT_SHADOWS=1
AIRCRAFT_REFLECTIONS=1
COCKPIT_HIGH_LOD=1
LANDING_LIGHTS=1
AC_SELF_SHADOW=1
EFFECTS_QUALITY=2
GROUND_SHADOWS=0
TEXTURE_QUALITY=3
IMAGE_QUALITY=0


[SCENERY]
SmallPartRejectRadius=1.0// can be increased at the cost of distance buildings but better frames (per pixel / whole number)
LENSFLARE=1
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=5 // 4 reduces big buildings and airport buildings

[TrafficManager]
AirlineDensity=20
GADensity=20
FreewayDensity=15
ShipsAndFerriesDensity=25
LeisureBoatsDensity=25
IFROnly=0
AIRPORT_SCENERY_DENSITY=2

[TERRAIN]
LOD_RADIUS=4.500000
MESH_COMPLEXITY=100
MESH_RESOLUTION=22 // Lower to 21 if you do not use FSX 10m mesh from FSGenesis
TEXTURE_RESOLUTION=25
AUTOGEN_DENSITY=3
DETAIL_TEXTURE=1
WATER_EFFECTS=4
TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=3000 //also try 1200 for lesser cards
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=800

[BufferPools]
PoolSize=2500000 // 500000 works too but can cause stutters on my system. Experiment to see what works best

I run the FX detail at 100% too

[ATI_7500]

TEXTURE_BANDWIDTH_MULT=80 //250 works well if i drop autogen and other sliders a notch. try betwen 80 and 250

Mh, the info on that one is confusing. Still fiddling around on that one. Got it set at 500 at the moment.

FIBER_FRAME_TIME_FRACTION=0.25

Sidenote: I have to apply something between 0.38 and 0.50 (not sure yet) on my system, since I cranked the autogen all the way up.

UPPER_FRAMERATE_LIMIT=18 //note.. FSX has a problem with the frame counter I was told it can be off by as much as 5 frames (reads lower than it actually is)

This is interesting. It could explain why FSX is still running quite smooth at 8 FPS.

AIRCRAFT_REFLECTIONS=1

Are the refections on a/c real-time ones?

MESH_RESOLUTION=22 // Lower to 21 if you do not use FSX 10m mesh from FSGenesis

Or even 19 if you think 76m mesh is accurate enough.

[justpassingthrough]

TEXTURE_BANDWIDTH_MULT=80 //250 works well if i drop autogen and other sliders a notch. try betwen 80 and 250

Mh, the info on that one is confusing. Still fiddling around on that one. Got it set at 500 at the moment.

FIBER_FRAME_TIME_FRACTION=0.25

Sidenote: I have to apply something between 0.38 and 0.50 (not sure yet) on my system, since I cranked the autogen all the way up.

UPPER_FRAMERATE_LIMIT=18 //note.. FSX has a problem with the frame counter I was told it can be off by as much as 5 frames (reads lower than it actually is)

This is interesting. It could explain why FSX is still running quite smooth at 8 FPS.

AIRCRAFT_REFLECTIONS=1

Are the refections on a/c real-time ones?

MESH_RESOLUTION=22 // Lower to 21 if you do not use FSX 10m mesh from FSGenesis

Or even 19 if you think 76m mesh is accurate enough.

you are running an 8800 card. Most people including myself cant touch that. Fiber frame can be tuned up for those cards.

I was told 400 is the max Tex bandwitdh multipler. If set higher it defaults to a low number and therefore 500 is doing nothing. Here is the math that was descibed to me:

Textures in kb x 3 (base number not available in the config) x Tex band multp = total memory bandwidth reserved

application: average of 3 1024x1024 textures in KB multipled by the multipler. So if average texture is about 500Kb then:

500Kbx3=1500 x (in example) 240 tex bandwidth mult = 360MB to the video memory. If you have a moster 8800 you can go the full 400 but it depends on what else you are rendering via the sliders.