hmar: Could you please upload the renumbering utility? Thanks.

Hugo, with that terrain.cfg I see a quite remarkable improvement in the texture loading times of the small grid of tiles immediately around the aircraft. Still have some blur in the distant tiles, however I can now fly 600kts+ over photoscenery with the close tiles becoming sharp in an instant. If there was a way to increase the size of this primary grid of tiles then the problem of fs9 blurries would now be 100% solved. Even if not, this is still a whole lot better than before.Cheers!

Well now we could be on to something here.As stated I'm not the creator nor the guy that found it - but now I wish I was :) but glad I'm helping to spread the word on it as it seems to be helping people out.People are catching on to it more here then the other two forums I posted it on at flightsim.com and fs2004.com (flightsimworld.com)A few of tried it but not very many - at least those that posted to inform me they did.Well yes lets keep testing and hope this helps us all eh.Ya Hugo that renumbering routine might be useful to us - i'd had to manually change all those numbers. ;)ThanksPaul.

Hi,All the previous has lead me to something that makes me much happier. Modify the terrain.cfg so that the texture numbering starts by 4096 instead of 1024. I'f written a very primitive program, which runs only in DOS mode (DOSBox) to make the renumbering, I have used starting numbers 2048, 4096 and 8172, but 4096 is the most satisfying on my system Dual Core E6750 @ 2666MHz and with an Nvidia 8600. Next in FS9.cfg, change the number in the [Graphics] section to "TEXTURE_MAX_LOAD=4096".On my system this gives really results. Let me know what's your result!I've included the modified terrain.cfg

OK, but AFAIK, FS9 uses the Texture id number in terrain.cfg to select what texture to use for vector terrain. So, what you are doing is stopping your vector terrain from displaying.scott s..

OK, but AFAIK, FS9 uses the Texture id number in terrain.cfg to select what texture to use for vector terrain. So, what you are doing is stopping your vector terrain from displaying.scott s..

Sorry, guys, I've created a hoax. Like Scott said, it prohibits the displaying from the vector terrain, like roads etc :( .Hugo

Hello all:I found this 'possible tweak' for FS2004 on flighsim.com posted by ZION in a thread called terrain.cfg and blurries.If you guys have already heard about it and/or tried it then my apologies.I've tried it and it looks promising for visuals anyways. I didn't notice any great improvement in FPS's but it definately didn't hurt them either.So here goes.First make a backup of your terrain.cfg file found in your main FS9 directory. The change isn't a big one so it shouldn't be hard to remember how to change it back :) but getting into the habit of making a backup of files before you change them is always a good one.Now at the very top of the file you will see a line under the [General] section that reads DefaultTextureCount=238Now to determine what to change this number to, keep scrolling down your terrain.cfg file and you see headings of [Texture.####] where #### is numbers used to represent textures used in the sim and they usually start at 1024 for the first one.So keep scrolling down the file to find the section with the highest number. Mine was 1261. It should be right before the sections for autogen.So now take that number, again in my case 1261, and replace the default 238 in the line I mentioned at the top that read DefaultTextureCount=238 to read DefaultTextureCount=#### (your highest number).Then save it and then go fly around a bit and report back on the success or no change or worse results that you find.Like I said it was NOT me that found this possible 'tweak' so remember don't kill the messenger. That's why i asked you to make a backup :)So let us know if this works out as we could possibly have a bunch of happy simmers if it does help us out.Again this is for FS9 / FS2004 and the terrain.cfg file found in the main FS9 directory.Thanks and waiting to hear your results.Paul.

Thanks for the info,I've tried it and I may well be imagining it but there appears to be a very significant improvement for me. :( regards jim

Sorry, guys, I've created a hoax. Like Scott said, it prohibits the displaying from the vector terrain, like roads etc :( .Hugo

Not entirely a hoax as I'm still seeing a dramatic difference for some reason. As I do 90% of my flying over photoscenery, I can live without the roads elsewhere. Roads in FS look ridiculously unrealistic anyway.

I tried it. And it feels to me that ground textures go in and out of sharpness/blurriness much quicker than before. So far it's a keeper. Thank you.

Great to hear.I'll have to keep trying to tweak it even further.So nice to be able to spread the word of a possible tweak to people even though it doesn't seem to help everyone - at least it is helping some and they are very please by it.Keep flying.Paul.

Interesting to see this info in the FS9 forum. :( For several years, I've been researching about a dozen tweaks that made a dramatic change in how FS9 runs on my older FS beta testing computer.Although the other 9 or so tweaks are interdependent with other factors such as computer hardware speed and system wide tweaks made to the BIOS, Windows OS, hardware driver settings etc., these 3 may still be of interest for testing on "nearly all" FS9 computers.I make no claim to their applicability to all users, nor do I intend for this info to be utilized for individual commercial gain; it's simply research that I'd like to see others have a chance to test for possible enhancement of FS9 texture appearance and overall performance on their own FS computers.NOTE: These are NOT intended for use in the FSX.Cfg file, which requires different parameters and/or values.Remember... Y M M V ! :( These tweaks should be safe to test; however, to be "doubly safe", make 2 or more ZIP backups (...to be kept in more than 1 "safe" location ?) of your existing "active" FS9.Cfg.FYI: The "active" FS9.Cfg is located in Windows XP Pro at:C:\Documents and Settings\[current user account or profile name]\Application Data\Microsoft\FS9\FS9.CFGNOTE: For performance reasons, I do not run FS on Vista or Win7, so the location of one's "active" FS9.Cfg file may be different under Vista or Win7.The existing FS9.Cfg in that folder can then be edited for purposes of testing the following "Ten Test Tweaks".NOTE: To restore the original FS9.Cfg, I would un-ZIP the backup with permission to over-write the edited working copy of FS9.Cfg in:C:\Documents and Settings\[current user account or profile name]\Application Data\Microsoft\FS9\FS9.CFGThe following "3 Test Tweaks" are listed under FS9.Cfg sub-sections where they should be inserted if not already present.There may, of course, be other parameters already in place between the sub-section heading and an existing parameter to be tweaked, so the examples below show the parameters to be tweaked immediately below the sub-section heading for the convenience of this guide.If a "test" tweak parameter does NOT exist, I suggest inserting it at the bottom of the specified sub-section under existing parametersIf a "test" tweak parameter ALREADY exists, I suggest doing this when editing:1.) Position mouse cursor immediately after the "=" sign2.) Hit the space bar two or more times, hit the "/" character twice, hit the space bar twice moreNOTE: This saves the existing number to the right of the "//" double-slash as a reference "comment" which will be ignored by FS9Example result after 1st edit:[GRAPHICS]TEXTURE_MAX_LOAD={blank space} // 2563.) Position mouse cursor immediately after the "=" sign4.) Enter the new "test" tweak numberExample result after 2nd edit:TEXTURE_MAX_LOAD=262144 // 256NOTE: Do NOT 'add' commas to long numbers, and always keep same number of trailing zeroes in decimal places of parameter numbersThe "3 Test Tweaks":[GRAPHICS]DETAIL_TEXTURE=2 // 1 <-- Tweak #1TEXTURE_MAX_LOAD=262144 // 256 <-- Tweak #2 (may vary with video card VRAM size in MB)[DISPLAY]TEXTURE_BANDWIDTH_MULT=25600 // 400 <-- Tweak #3 (may vary with computer hardware speed / configuration)NOTE: For "Tweak #3", try multiplying size of VRAM on video card (ex: 256 MB) x 1024 to get this "test" parameter valuePS: FS9 may take longer to start up with these tweaks, as more textures are loaded into RAM and the Windows memory cache. B) Hope this proves helpful to other users after proper individualized testing on their own FS9 systems ! :( GaryGB

Bumped for correction: "3" NOT "10" tweaks (error editing copy of info previously sent in a private message).GaryGB

Hello,

[DISPLAY]TEXTURE_BANDWIDTH_MULT=25600 // 400 <-- Tweak #3 (may vary with computer hardware speed / configuration)NOTE: For "Tweak #3", try multiplying size of VRAM on video card (ex: 256 MB) x 1024 to get this "test" parameter value

Seem's it's something wrong there .. with your arithmetics or mine :( As 25.600 / 1024 = 25 :( You have only 25 MB VRAM ? :( Regards. Gus.

Thanks for the heads up on that other editing error in my hastily written initial post above.The VRAM calculation statement should have read "Tweak #2".< sigh > I gotta' quit trying to post to forums on my mobile phone mini-browser ! GaryGB

Interesting. Gary, my GTX580 is 1536 Mb. So what should my numbers in your Tweak#2 and Tweak#3 look like? I understand your tweaks are not related to terrain.cfg discussion in this thread? Or at least you did not connect them to terrain.cfg, did you? Thanks,Dirk.

CORRECTED Text for my post (#25) above:http://forum.avsim.net/topic/329728-possible-new-tweak-for-fs9/page__view__findpost__p__1947499NOTE: Do NOT 'add' commas to long numbers, and always keep same number of trailing zeroes in decimal places of parameter numbersThe "3 Test Tweaks":[GRAPHICS]DETAIL_TEXTURE=2 // 1 <-- Tweak #1TEXTURE_MAX_LOAD=262144 // 256 <-- Tweak #2 (may vary with video card VRAM size in MB)[DISPLAY]TEXTURE_BANDWIDTH_MULT=25600 // 400 <-- Tweak #3 (may vary with computer hardware speed / configuration)NOTE: For "Tweak #2", try multiplying size of VRAM on video card (ex: 256 MB) x 1024 to get this "test" parameter value

Interesting. Gary, my GTX580 is 1536 Mb. So what should my numbers in your Tweak#2 and Tweak#3 look like? I understand your tweaks are not related to terrain.cfg discussion in this thread? Or at least you did not connect them to terrain.cfg, did you? Thanks,Dirk.

The calculation to test would be VRAM (MB) of 1536 x 1024 = 1572864; again, this may vary as stated above, so test different MB VRAM amounts with your system to see if a pattern emerges for your particular BIOS, hardware, driver, and FS.Cfg configuration.FYI: This info is related to optimizing performance to compensate for a Terrain.Cfg that may impact the FS9 rendering engine... as "hmar" alluded to in his post #13:http://forum.avsim.net/topic/329728-possible-new-tweak-for-fs9/page__view__findpost__p__1945971.BTW: Perhaps some some forum readers here may recall that not only [FS install path]\Terrain.Cfg, but also [FS install path]\Autogen\default.xml Autogen definition files both have a significant impact on FS9's rendering engine performance.Some used to either edit default.xml to disable some Autogen 3D and 2D vector objects; others disabled it entirely by renaming it so FS couldn't find / load definitions inside that file.FYI: This autogen editing/tweaking process still works in FSX, although differently via xml compilation into a *.spb file format.Now that most of us have more capable computers, we can begin considering how to tweak multiple system parameters to optimize FS9 for better performance than we could years ago when we had much less capable computers.Hopefully these ideas may stimulate more inquiry for tweaking FS9 as well as FSX; perhaps ******* Altuve (aka "bojote") might be interested in looking into these possibilities as well ?Hope this helps ! :( GaryGB