For instance, Scenery Compleity is really Image Complexity and Normal is really 2 and dense is 2.5 or 3 and all the remaining 100 or so. Someone, somewhere must have documented this. LOD is Level of Detail and Large equates to 3.5 or something, etc.Can someone point me towards this? Thanks. Yes, I did the search, again and again with no results, zilch. :( s/b for fsx.cfg fileRayM

I wasn't aware of such document. To be honest, if you are tweaking for a while, you will come by to knowing those. Without, you are probably better off without tweaking :(

For instance, Scenery Compleity is really Image Complexity and Normal is really 2 and dense is 2.5 or 3 and all the remaining 100 or so. Someone, somewhere must have documented this. LOD is Level of Detail and Large equates to 3.5 or something, etc.Can someone point me towards this? Thanks. Yes, I did the search, again and again with no results, zilch. :( s/b for fsx.cfg fileRayM

You can download this old program http://www.wolfgang-picheta.de/ "FlussiFix" for FSX and change settings in all the cfg files and I think it explains them all from BP=0 to Light scale sizes, its a bit long in tooth (06-07) but maybe a good start, Not that you should use all those tweaks, but you can run the exe and click on the options and read up on the myrids of them!

You can download this old program http://www.wolfgang-picheta.de/ "FlussiFix" for FSX and change settings in all the cfg files and I think it explains them all from BP=0 to Light scale sizes, its a bit long in tooth (06-07) but maybe a good start, Not that you should use all those tweaks, but you can run the exe and click on the options and read up on the myrids of them!

Thanks for the link, Player2. I will give it a look.

I wasn't aware of such document. To be honest, if you are tweaking for a while, you will come by to knowing those. Without, you are probably better off without tweaking :(

Thanks for the comments, Word Not Allowed. It is not necessarily for tweaking as much as for reading and understanding - what happens - when - kinda stuff.

Quote:'I am doing this and I figure it will be ready in about 3 years. I have already done 2 years into the 'spreadsheet' so far. In the mean while use 'Default' settings and only mess with the 'AutoGen' slider, a/c casts shadow (off), and the weather (with special attention to 'Visibility' tab of advanced weather.' (by 'Unknown').JUST KIDDING: I just thought I would rub some fun into your quest/request. Do you realize how many combinations there would be if you logged each different one in a spreadsheet? 10,000 combinations? More? That's just the fsx.cfg values and equivalent 'settings' comparison(s)-right?.So I 'smell' a FPS improvement project and/or complete revision on how FSX does things-like render LOD when 'x=2' vs when 'x=3.5'. You'll be there till most of us are dead and burried. 'Correct me if I am wrong' would apply (if you want to argue). But I am pretty sure you DON'T want to know what it takes to achieve what your are asking and what it takes to make a 'graph', or log, or spreadsheet, of all the cfg settings and their permutations and variations/combinations. But then 'I could be wrong' also applies? How about learning some aeronautical engineering and forget the graph. I buy THAT.CBNapamule

HI, JUST MY TWO CENTS.... WOULD IT BE INTERESTING IF ALL THIS DATE COULD BE GATHERED AND PUT ON A SPREAD SHEET AND SOME HOW APPLIES DIRECTLY TO THE PROGRAM ( FSX) AND NO ONE WOULD HAVE TO FIGURE OUT WHAT MAKES THE PROGRAM TICK. THIS WAS SUPPOSED TO BE A FLYING PROGRAM NOT AN EXERCISE IN SPREAD SHEET KNOWLEDGE ! OR WOULD THAT BE ASKING TO MUCH OF MICROSOFT !TONY

HI, JUST MY TWO CENTS.... WOULD IT BE INTERESTING IF ALL THIS DATE COULD BE GATHERED AND PUT ON A SPREAD SHEET AND SOME HOW APPLIES DIRECTLY TO THE PROGRAM ( FSX) AND NO ONE WOULD HAVE TO FIGURE OUT WHAT MAKES THE PROGRAM TICK. THIS WAS SUPPOSED TO BE A FLYING PROGRAM NOT AN EXERCISE IN SPREAD SHEET KNOWLEDGE ! OR WOULD THAT BE ASKING TO MUCH OF MICROSOFT !TONY

uh.... 1). read NapaMule's comment.. and 2). Why are you shouting? It was nice and quiet around here! :(

uh.... 1). read NapaMule's comment.. and 2). Why are you shouting? It was nice and quiet around here! :(

I don't see it as 10,000 combinations. That is not what I am looking for. The main or most used sliders have a max of say 6 positions. Each of those are respresented by a number in the fsx.cfg file. Some have only three positions, Some are just numbers already. That is what I am looking for.If I am reading my fsx.cfg file and and I see a line is set to 2.5 or 3.5, I wouldn't have to wonder or guess is that Normal or above normal, or dense or very dense. Now, if I move a scenery slider and close up fsx the fsx.cfg file is updated with that slider position ane of course the number changes. That's all - not brain surgery, well maybe brain surgery for a few of the posters, but mostly just a little info that can be collected for reference. Surely you don't have all this minute stuff in your active memory banks all the time.I'm thinking if the data doesn't exist or the ones that have it choose not to share, then, I will probably take some screenshot of the settings menus with the sliders and use a graphics program to overlay the available position names above the line and the fsx.cfg number below the line. Or something like that.RayM

I don't see it as 10,000 combinations.

the table would result in BILLIONS of outputs.first you agree on:airport locationin-flight locationweather setting (think how many different weather outputs that can be generated!!!)now you have:each FS settingeach FS hackeach default aircrafteach addon aircraft (and some even have settings)each addon scenery (and some have settings)each CPUeach CPU overclockeach CPU coolereach MOBOeach GPUeach GPU memory sizeeach memory stickeach memory sizeeach monitoreach hard driveeach hard drive sizeeach OSeach OS biteach release versoneach hardware drivereach hardware driver release versionand ... for all hardware you would need to look at changes made (ie, all MOBO has a version type, and then you have release data as with hardware what is built one day will be different the next day, week, month, or year (if in production for more than 1-4 months))now, you need to see if setting A is, B is, C is, D is ... v. hardware type A, version B, release C, driver Dnow change one seetting and keep all others the same.repeat, repeat, repeat ....--

the table would result in BILLIONS of outputs.first you agree on:airport locationin-flight locationweather setting (think how many different weather outputs that can be generated!!!)now you have:each FS settingeach FS hackeach default aircrafteach addon aircraft (and some even have settings)each addon scenery (and some have settings)each CPUeach CPU overclockeach CPU coolereach MOBOeach GPUeach GPU memory sizeeach memory stickeach memory sizeeach monitoreach hard driveeach hard drive sizeeach OSeach OS biteach release versoneach hardware drivereach hardware driver release versionand ... for all hardware you would need to look at changes made (ie, all MOBO has a version type, and then you have release data as with hardware what is built one day will be different the next day, week, month, or year (if in production for more than 1-4 months))now, you need to see if setting A is, B is, C is, D is ... v. hardware type A, version B, release C, driver Dnow change one seetting and keep all others the same.repeat, repeat, repeat ....--

You completely are misunderstanding his request.He just wants the values that relate to the cfg file as input from the sliders i.e. when you set AG in FSX at Dense and it is at 2,3 or 4 in the cfg.Comprendo?

uh.... 1). read NapaMule's comment.. and 2). Why are you shouting? It was nice and quiet around here! :(

Sorry about shouting but at my age sometime I don't hear so good !Tony

the table would result in BILLIONS of outputs.first you agree on:airport locationin-flight locationweather setting (think how many different weather outputs that can be generated!!!)now you have:each FS settingeach FS hackeach default aircrafteach addon aircraft (and some even have settings)each addon scenery (and some have settings)each CPUeach CPU overclockeach CPU coolereach MOBOeach GPUeach GPU memory sizeeach memory stickeach memory sizeeach monitoreach hard driveeach hard drive sizeeach OSeach OS biteach release versoneach hardware drivereach hardware driver release versionand ... for all hardware you would need to look at changes made (ie, all MOBO has a version type, and then you have release data as with hardware what is built one day will be different the next day, week, month, or year (if in production for more than 1-4 months))now, you need to see if setting A is, B is, C is, D is ... v. hardware type A, version B, release C, driver Dnow change one seetting and keep all others the same.repeat, repeat, repeat ....--

I'm sorry you wasted so much time writing all this crap, just because you can't read. I just finished the project - it is the sum total of two pages in an excel spreadsheet. Wow!. Some guys just can't wait to jump over a cliff and make a fool of themselves.There is dumb and is this case dumber.RayM

I'm sorry you wasted so much time writing all this crap, just because you can't read. I just finished the project - it is the sum total of two pages in an excel spreadsheet. Wow!. Some guys just can't wait to jump over a cliff and make a fool of themselves.There is dumb and is this case dumber.RayM

Hi Ray, sounds interesting.I would be very interested to see your excel spreadsheet.Thanks

For instance, Scenery Compleity is really Image Complexity and Normal is really 2 and dense is 2.5 or 3 and all the remaining 100 or so. Someone, somewhere must have documented this. LOD is Level of Detail and Large equates to 3.5 or something, etc.Can someone point me towards this? Thanks. Yes, I did the search, again and again with no results, zilch. :( s/b for fsx.cfg fileRayM

If I get around to it I will publish my baseline tests that shows how each (popular) seeting affects a given metric. The hard part is keeping the baseline platform stable. For instance, having the mouse cursor over the FSX test window killed 15 FPS on average so I had to retest a bunch of settings.Since all the settings are zero or in effect turned off for the baseline, FSX loads in 1 second which is cool.A side note is a read on how to build a balanced platform: http://www.tomshardware.com/reviews/balanc...clock,2625.htmljja

Hi Ray, sounds interesting.I would be very interested to see your excel spreadsheet.Thanks

I need to clean it up a little to make it easier to read. PM me and I will send it to you.Ray