FSX & SLI

[macca22au]

On the basis of your post I decided to hunt down every folder and file that might have been created when I unzipped and installed the landclass.  I removed every incidence except the original compressed folder, and went in and removed the bgls from the addon scenery\scenery folder, then started again.  The result is the false path has been eliminated and the landclass works perfectly.  I installed the new 158. driver for Nvidia 8800 cards today and I am unsure whether it has made smoothness any better or worse.  I almost rolled back to the previous maligned driver which now almost seems better!I can fly comfortably over Long Island with the scenery setting of Dense/Dense but any steepish turns sends it juddering.  I guess that isn't all that bad considering.  Hopefully the SP will give us a reasonable percentage lift in performance - I don't need a lot.

Now should I try that Instant Scenery utility from Flight 1 or should I leave well alone?

[Nick N]

[quote]On the basis of your post I decided to hunt down every folder and file that might have been created when I unzipped and installed the landclass.

[Nick N]

Another member here posted the file FSX KML listed at scenery.og

I had seen it some weeks ago but have not had the chance to play with it yet. It is suppose to work with google earth in creating landclass and scenery. You may want to check that one out too

http://www.scenery.org/graphical_editors.htm

[macca22au]

If I was to run autogen sparse, and complexity dense or really dense would that be likely to balance out the stutters?  I shall try it tonight.

[Nick N]

[quote]If I was to run autogen sparse, and complexity dense or really dense would that be likely to balance out the stutters?

[macca22au]

Thanks Nick, more useful tips to consider.  However, I only fly with VC because of the matrox setup in any case.  I will do as suggested on one monitor, but to be honest it is fairly academic - once you have flown with matrox three screens it is impossible to go back to one. And for me, whatever happens I will persist with the three.  Matrox are bringing out a digital version with some presentational improvements, and I also hope some reduced resource calls.  I have considered the new large screen monitors - Dell has a 27" with more to come, but they still give only 1920megapixels and are very large on the desk.   However I suspect my system is actually performing fairly well considering the resolution it is operating at.   And sorry if I wasn't clear, but I do keep scenery complexity constant and adjust the autogen slider.  

[Nick N]

[quote]Thanks Nick, more useful tips to consider.

[Black ZR-1]

Only fly VC. The 2D cockpits in FSX have rendering issues.

I knew something wasn't right when I was getting better performance in VC than in 2D.

[macca22au]

I would like to take the FSU and CPU up a little.  Enough to make a difference but not enough to push the temperature up.  It seems to make more sense to work on the CPU than the GPU given that FSX is CPU dependent.  I would be interested in how to do it, but I don't want to have to physically shift jumpers etc.  Can a first increment be gained just by tweaking the BIOS?  The tweakguides and others talk seriously about the benefits and dreadful disadvantages of tweaking. It makes me break out in a sweat. Or should I be patient and wait for the SP?

[macca22au]

And I am defragged to within an inch of my computer's life, while Registry Mechanic runs at every boot.  My machine is the equivalent of being absolutely clean shaven and with a shaved head.  I can fly out of areas with average urban autogen with the autogen slider at dense, and complexity at 100%. However the big smokes, London, New York, Seattle still require me to pull back to Normal, or if I am flying a glass cockpit aircraft sometimes even sparse.  I haven't tried it but I suspect I could fly over rural areas at 100% autogen.  But the big urban areas still bring me back to the field.  In truth though my performance is very good, I just wonder whether some minimal overclocking could improve the performance over complex areas.

[ATI_7500]

I don't know it Nick would approve, but without changing your cooling equipment, the only thing I'd do is rising the CPU's FSB to match your memory's frequency and then cut back on the multiplier to keep your CPU in the range of its original speed.

This would give you a slight boost, but nothing to wet your pants about.

[Nick N]

macca22au


I have some concerns about applying the tweak list I posted to Vista and especially the use of software such as Registry Mechanic in Vista. Also, my instructions for the use of Registry Mechanic were very specific to shut down the registry monitor when the software is first run so it does not run at Windows boot.

[macca22au]

I got your message clearly Nick.  I bought Registry Mechanic because this thread views it as useful.  The producers said that it had restricted functionality in Vista and that seems to be the case.  It only repairs a minority of the list that it comes up with after analysis.  I will leave it unused until they have a full update available or you or someone gives the go ahead. By the way, I have found Tweakguides useful for my understanding, do you see them as useful?  Also I will forget any clocking for the time being until we see how the SP goes.  By the way would my present configuration benefit from faster RAM? I have been exploring the Seattle region, and without necessarily giving away your exact location what are the airfields near where you reside?

[DizZa]

OK.

I have the same settings as before, however I have scenery radius at 4.5 (large), and cloud coverage density at max. Autogen numbers are at dense:
TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=670 <---I got this number from scenery radius numbers 4.5 \ 3.5=1.2857. 868 \ 1.2857 = 670.
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=335 <---Half above

[BufferPools]
PoolSize=2080000

TEXTURE_BANDWIDTH_MULT=108
UPPER_FRAMERATE_LIMIT=17 <---I raised it from 15 as I find 17 more fluid with little cost.
FTTF=.29

I also changed Anisotropic filtering to application controlled and upped filtering from trilinear to anisotropic ingame.

Turns out the thing that was causing my stutters were RESIZED autogen textures.

[ATI_7500]

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=670 <---I got this number from scenery radius numbers 4.5 \ 3.5=1.2857. 868 \ 1.2857 = 670.
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=335 <---Half above

Is your hardware really that bad?

I thought you could do at least a 400 (=1000/500) load on trees and buildings...