Hi,hope that someone here can help me with a strange issue I'm facing since I had to reinstall FSX after to have changed my MOBO and CPU (i7-2600K) and never faced before.After to have reinstalled all my FSX pieces, I have tweaked my FSX.CFG: one of the tweaks I use is to eliminate the TBM entry.Well, since the reinstallation and even if FSX is closed, everytime I open the FSX.CFG after to have run FSX I find the line TEXTURE_BANDWIDTH_MULT=40 back in my cfg an so I have to delete it everytime.What am I doing wrong or what could be changed in my FSX to have this *** issue?Anyway I use Win 7/64.Any suggestion and hep will be really appreciated.Thanks and best regards

Hi,Pretty sure that is a default line in FSX and cannot be permanently removed. You can disable the line with \\ at the beginning of the line.

Hello:Have you experienced an improvement in FSX performance when you delete the "TEXTURE_BANDWIDTH_MULT=" (aka 'TBM') entry in FSX.Cfg and save that file BEFORE starting FSX ? :( FYI: the TEXTURE_BANDWIDTH_MULT="X" is a default parameter FSX normally expects to find present in FSX.Cfg when it starts up.FSX automatically attempts to add / edit FSX.Cfg to restore certain parameters to a 'default' value when FSX exits.Different FSX 'TBM' numeric values have been proposed for "X" ranging from 40 to 80 (and sometimes more) depending on one's individual FSX system configuration of hardware and software.Most often a value of TEXTURE_BANDWIDTH_MULT=80 has been purported as the max feasible for use in FSX (unlike in FS9 which seems to respond differently to TBM parameter numeric values of ten or more times as large (ex: 400 to 800), and even as large as 25600 as discussed in this thread (about FS9 only !):http://forum.avsim.net/topic/329728-possible-new-tweak-for-fs9/I have not yet tested starting FSX without having a TEXTURE_BANDWIDTH_MULT="X" parameter present, but it sounds interesting in light of prior threads here at AVSIM describing parameter statements used to "disable" hidden FSX "default" bufferpools values in performance tweak testing scenarios.IIRC, FSX still uses certain parameters based on internal defaults even when a parameter is not explicitly listed as a line of text in the FSX.Cfg, and in the latter discussion on bufferpools values in performance tweak testing scenarios, a particular value reportedly minimized or disabled entirely the internal FSX default allocation of bufferpools.It might be interesting to see if this can be done with other FSX parameters in a comprehensive set of tests to see if it produces a genuine performance benefit (without inducing other detrimental consequences to FS functionality and/or over the time of longer flights with varying scenery/autogen/AI Traffic density settings etc.). B) I'd be interested to know more about your experiences starting FSX without a TEXTURE_BANDWIDTH_MULT="X" parameter present in FSX.Cfg. :( BTW: To prevent FS from automatically restoring / editing "default" parameters and their numeric values during tweak testing and/or in between flights, one must "lock" the 'active' FSX.Cfg file by setting its file attribute to "read only".Alternatively, one can or open the 'active' FSX.Cfg in a text editor (ex: Windows NotePad) and minimize it to the Windows taskbar BEFORE starting FSX, and keep that file open until you have fully exited FSX, and the FSX "task" has disappeared from the Windows taskbar.Or, as Jim alluded to above, one can add 2 "/" ('slash') characters at the beginning of a line to force FS to ignore all text to the right of the double-slash as a "comment".One can also add an extra line in the FSX.Cfg file below an active parameter line being tested as a "backup" and/or numeric value reference (ex:):

[DISPLAY]//------------------------// Improving shadow detail as posted in Phil Taylor's ACES / FSX Blog: http://blogs.msdn.com/b/ptaylor/archive/2008/06/23/yaft.aspx//-------------------------// Note, it is possible to tweak the shadow quality somewhat. Try adding this to [DISPLAY] section of FSX.cfg file:// ShadowMappingQuality=n// where n can be 0,1,2,3.// The 1st 2 values affect the size of the shadow map. The 2nd 2 values affect the filtering algorithm.// In the D3D9 code path, this affects the external model shadow maps.// In the D3D10 code path, this affects the external model as the interior model ( VC ) shadow maps are hardcoded// to the highest quality level.//You may be able to make the ground shadows look a bit better by tweaking this (may reduce aliasing / "jaggies")ShadowMappingQuality=1UPPER_FRAMERATE_LIMIT=0TEXTURE_BANDWIDTH_MULT=80// TEXTURE_BANDWIDTH_MULT=40WideViewAspect=True[TERRAIN]

Hope this info helps ! :( GaryGB

Hi,thnaks a lot: putting the double slashes to comment the row solved tghe issue.I got the suggestion to delete the row on the bojote's tweak tool: effectively after to have deleted it I'm experiencing less micro stutters, even if it seems that i have some more blurries at low altitude.Still working on the FIBER_FRAME to try to solve that.Thanks again and have good flights

Hi,Thanks a lot: putting the double slashes to comment the row solved the issue.I got the suggestion to delete the row on the bojote's tweak tool: effectively after to have deleted it I'm experiencing less micro stutters, even if it seems that i have some more blurries at low altitude.Still working on the FIBER_FRAME to try to solve that.Thanks again and have good flights

Please let us know what tested numeric values you used for your "FIBER_FRAME_TIME_FRACTION=" tweak in combination with a deleted "TEXTURE_BANDWIDTH_MULT=" parameter ...seemed to produce a (good or bad) change in FSX run time performance. :( Thanks for sharing the ideas being explored in your testing scenarios with the rest of us here ! :(PS: You're testing with FSX SP2 and/or Acceleration, correct ? (IIRC, "FIBER_FRAME_TIME_FRACTION=" reportedly still works on SP2) :( GaryGB

Hi,i was wrong: even with the double slashes to comment the row, i still get the cfg modified with the TBM row added when I close FSX. I do not understand what I have to do: I never had before the reinstallation of FSX.By the way, actually I have the best results with FIBER_FRAME_TIME_FRACTION=0.30: no autogen popping, no blurries at all until I reach more or less 500ft during landing and only when I am in the wing side views (also the stuttering is really low).Next test will be to increase the value to 0.35.Yes i'm using FSX with SP2, GEX,UTX Europe, FEX or REX.

i was wrong: even with the double slashes to comment the row, i still get the cfg modified with the TBM row added when I close FSX. I do not understand what I have to do

The TBM parameter will default to 40 if you omit that parameter, and when FS saves the CFG file before termination it simply includes this fact. Deleting it before the next reload of FS does nothing whatsoever for you if the value you are deleting is the default, as the omission simply tells FS to use the default value.What exactly are you trying to accomplish? If you want to CHANGE the value, include the parameter with that different value. But there's simply no such thing as "no value"! It always has one!RegardsPete

The TBM parameter will default to 40 if you omit that parameter, and when FS saves the CFG file before termination it simply includes this fact. Deleting it before the next reload of FS does nothing whatsoever for you if the value you are deleting is the default, as the omission simply tells FS to use the default value.What exactly are you trying to accomplish? If you want to CHANGE the value, include the parameter with that different value. But there's simply no such thing as "no value"! It always has one!RegardsPete

Peter is totally correct. If you want to make it nothing then do it this way:- TEXTURE_BANDWIDTH_MULT=0You need to go back over the past year and read the Bojote series of tweaks and enhancements, because this and the Fibre_Frame_Time_Fraction have ben discussed ad infinitum. From his notes:-TEXTURE_BANDWIDTH_MULT=10 // Useless.. its simply a multiplier, what you REALLY want to tweak is [DISPLAY]TextureMaxLoad.TextureMaxLoad=21 // You can try 12, 15, 18 and 21 (it will make texture loading faster)You can use any multiple of 3.The default for FIBER_FRAME_TIME_FRACTION is .33, and the difference between .33 and .30 is hardly discernible. To make the graphics smoother - drop it to .25, then .2, then .15. Somewhere below .2 your road and some ground texturs will become a blurry mauve/purple "muddy" texture, and that number will depend upon how fast your gpu/cpu figures are. My rig, right now, with a 2600K/GTX580 combo at 4.8gig I'm using an FFTF of .1 and a TEXTURE_BANDWIDTH_MULT=110 over OrbX PNW/Portland scenery with the BN Islander at 800' and have no blurries nor stutters, but your results will depend upon your horses AND a couple of other parameters in the cfg file. I would suggest you send you .cfg in to :- http://www.venetubo.com/fsx.html and see what comes back.