FSX & SLI

[Nick N]

*Bump*

FSX is up and running...and blurred.
This is not a new problem to me (been fighting them from the tests on), but I just can't seem to get rid of the ground textures blurries, no matter what kind of values I set in the .cfg. Autogen doesn't have anything to do with it. I could set numbers as low as 2000/1000 and still get them.


Numbers producing less blurries than Black ZR-1's:

TBM = 320
FFTF = 0.36
AG density = 3

Autogen still at 3000/1500...I think I'll fix this as my lower end.

I assume your frame lock is 20?

[Nick N]

I am going to put a hold on going into calculations further...

I will make some suggestions for those who have asked thus far and will continue to work with Heretic. Mil, Black, Arnaage and macca22au however I have a bit of an announcement to make...


I have just returned from a visit where I reviewed SP1 for FSX


I think all these calculations may very well go out the door as of SP1 release.


I can confirm that SP1 will in fact address performance problems and I must say I am quite impressed with the changes.

Those of you who may read into that and are running low end hardware, please do not assume a 128mb 9800 Radeon card on 1 gig of memory is going to run FSX with no problems. The changes that were made are significant and will improve things for low end hardware but FS9 will not run wide open on such hardware so please do not expect FSX to either.



I can not say any more about it but I do think spending hours at this point in tweaking may mean starting over after SP1 is installed



I will continue to make suggestions to those who have asked thus far but I am going to hold off on posting a guide to calculating hardware to FSX settings as it will be obsolete within 3 weeks or less.

[Black ZR-1]

I am going to put a hold on going into calculations further...

I will make some suggestions for those who have asked thus far and will continue to work with Heretic. Mil, Black, Arnaage and macca22au however I have a bit of an announcement to make...


I have just returned from a visit where I reviewed SP1 for FSX


I think all these calculations may very well go out the door as of SP1 release.


I can confirm that SP1 will in fact address performance problems and I must say I am quite impressed with the changes.

Those of you who may read into that and are running low end hardware, please do not assume a 128mb 9800 Radeon card on 1 gig of memory is going to run FSX with no problems. The changes that were made are significant and will improve things for low end hardware but FS9 will not run wide open on such hardware so please do not expect FSX to either.



I can not say any more about it but I do think spending hours at this point in tweaking may mean starting over after SP1 is installed



I will continue to make suggestions to those who have asked thus far but I am going to hold off on posting a guide to calculating hardware to FSX settings as it will be obsolete within 3 weeks or less.

I had a feeling that would happen...

Do you recommend we put everything back to default settings, including the autogen file, before we install SP1?

[Nick N]

I am going to put a hold on going into calculations further...

I will make some suggestions for those who have asked thus far and will continue to work with Heretic. Mil, Black, Arnaage and macca22au however I have a bit of an announcement to make...


I have just returned from a visit where I reviewed SP1 for FSX


I think all these calculations may very well go out the door as of SP1 release.


I can confirm that SP1 will in fact address performance problems and I must say I am quite impressed with the changes.

Those of you who may read into that and are running low end hardware, please do not assume a 128mb 9800 Radeon card on 1 gig of memory is going to run FSX with no problems. The changes that were made are significant and will improve things for low end hardware but FS9 will not run wide open on such hardware so please do not expect FSX to either.



I can not say any more about it but I do think spending hours at this point in tweaking may mean starting over after SP1 is installed



I will continue to make suggestions to those who have asked thus far but I am going to hold off on posting a guide to calculating hardware to FSX settings as it will be obsolete within 3 weeks or less.

I had a feeling that would happen...

Do you recommend we put everything back to default settings, including the autogen file, before we install SP1?

You will need to make sure all files are default, including the terrain.cfg file that some may have replaced to combat the rocks-in-rivers and other issues.

If all you did was the autogen description file change, its just a matter of replacing the file with the original you saved

[justpassingthrough]

I am going to put a hold on going into calculations further...

I will make some suggestions for those who have asked thus far and will continue to work with Heretic. Mil, Black, Arnaage and macca22au however I have a bit of an announcement to make...


I have just returned from a visit where I reviewed SP1 for FSX


I think all these calculations may very well go out the door as of SP1 release.


I can confirm that SP1 will in fact address performance problems and I must say I am quite impressed with the changes.

Those of you who may read into that and are running low end hardware, please do not assume a 128mb 9800 Radeon card on 1 gig of memory is going to run FSX with no problems. The changes that were made are significant and will improve things for low end hardware but FS9 will not run wide open on such hardware so please do not expect FSX to either.



I can not say any more about it but I do think spending hours at this point in tweaking may mean starting over after SP1 is installed



I will continue to make suggestions to those who have asked thus far but I am going to hold off on posting a guide to calculating hardware to FSX settings as it will be obsolete within 3 weeks or less.

now that's GOOD news!



I made backups of everything and I can uninstall the traffic if necessary.


The settings you posted worked. They got rid of all the stutters in overcast no matter how thick and even the ones in the city over car highways in heavy weather I was getting before but the autogen was not as pronounced in the distance. Guess I just have to deal with it. I was able to raise the frame lock to 17 without any problem. @ 18 the blurs started creeping in here and there.


I think I am tweaked at this point. Even New York and LAX is flyable although they really do slap the system silly  :)

[Black ZR-1]

I am going to put a hold on going into calculations further...

I will make some suggestions for those who have asked thus far and will continue to work with Heretic. Mil, Black, Arnaage and macca22au however I have a bit of an announcement to make...


I have just returned from a visit where I reviewed SP1 for FSX


I think all these calculations may very well go out the door as of SP1 release.


I can confirm that SP1 will in fact address performance problems and I must say I am quite impressed with the changes.

Those of you who may read into that and are running low end hardware, please do not assume a 128mb 9800 Radeon card on 1 gig of memory is going to run FSX with no problems. The changes that were made are significant and will improve things for low end hardware but FS9 will not run wide open on such hardware so please do not expect FSX to either.



I can not say any more about it but I do think spending hours at this point in tweaking may mean starting over after SP1 is installed



I will continue to make suggestions to those who have asked thus far but I am going to hold off on posting a guide to calculating hardware to FSX settings as it will be obsolete within 3 weeks or less.

I had a feeling that would happen...

Do you recommend we put everything back to default settings, including the autogen file, before we install SP1?

You will need to make sure all files are default, including the terrain.cfg file that some may have replaced to combat the rocks-in-rivers and other issues.

If all you did was the autogen description file change, its just a matter of replacing the file with the original you saved

Is it better to just delete the fsx.cfg file and create a new one or just delete the added lines in it?

[macca22au]

Nick after reading your comments about SP1 I am happy to wait for it to be released before we tweak further.  If it is on time we have only a couple of weeks to go, so I can fly comfortably as I am.  Seeing I have only recently done a clean install, I am likely to repeat it for SP1 so that I needn't worry to much about backups although I have them all on disk.

By the way, I wonder whether you could help me with a curious phenomenon that has entered my FSX.  With almost any complex aircraft I frequently get an excellent commencement to the flight and then suddenly it begins to slow down, jerk, jump and stop. All I can do is get out of the game and restart.  It is as if the system has choked.  If anyone has experienced this I would be grateful for advice.

Ian

[Nick N]

I am going to put a hold on going into calculations further...

I will make some suggestions for those who have asked thus far and will continue to work with Heretic. Mil, Black, Arnaage and macca22au however I have a bit of an announcement to make...


I have just returned from a visit where I reviewed SP1 for FSX


I think all these calculations may very well go out the door as of SP1 release.


I can confirm that SP1 will in fact address performance problems and I must say I am quite impressed with the changes.

Those of you who may read into that and are running low end hardware, please do not assume a 128mb 9800 Radeon card on 1 gig of memory is going to run FSX with no problems. The changes that were made are significant and will improve things for low end hardware but FS9 will not run wide open on such hardware so please do not expect FSX to either.



I can not say any more about it but I do think spending hours at this point in tweaking may mean starting over after SP1 is installed



I will continue to make suggestions to those who have asked thus far but I am going to hold off on posting a guide to calculating hardware to FSX settings as it will be obsolete within 3 weeks or less.

I had a feeling that would happen...

Do you recommend we put everything back to default settings, including the autogen file, before we install SP1?

You will need to make sure all files are default, including the terrain.cfg file that some may have replaced to combat the rocks-in-rivers and other issues.

If all you did was the autogen description file change, its just a matter of replacing the file with the original you saved

Is it better to just delete the fsx.cfg file and create a new one or just delete the added lines in it?

When it comes to an update like this I would make sure I save a copy of the file elsewhere before the update and simply run the update. I see no reason to kill a config file that is working. At that point I would fly what I have and see if I notice any difference. Play with raising the frame lock a tad or perhaps traffic.

You can alway delete the file and start over to play around and then just drop the backup copy into the folder when ever you feel like it to compare. You may find out you are already trimmed correctly and will be greeted with a better frame lock and traffic on the same settings. 4 frames in FSX is a good leap so if you can get locked at 24 you have a heck of a boost.

Speaking of frames, I think they fixed the counter too so some of what you see will be psychosomatic. MS isn

[Nick N]

[quote]Nick after reading your comments about SP1 I am happy to wait for it to be released before we tweak further.

[Nick N]

Rofl.

My computer:
Intel 925xe
Pentium 4 650 (17x200, 3.4ghz, 2mb L2 cache)
4x512mb RAM (Dual Channel at 266mhz, 4-4-4-12 I don't know Command rate)
X850XT PE (540 / 590 37.8gb/s)

can run the settings at:
TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1150
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=575
AUTOGEN_DENSITY=3
TEXTURE_BANDWIDTH_MULT=96
UPPER_FRAMERATE_LIMIT=18
PoolSize=2575000
FIBER_FRAME_TIME_FRACTION=.28

Very smooth but I still get stutters in cities. Hmmmmm, I know I can get around this, however I am not sure how. Ingame I usually have a minimum of 15mb of VRAM so I cannot boost poolsize up much.

Nick, how high do you think my TEXTURE_BANDWIDTH_MULT=96 should be at?

On that card you are running 256MB. Its a good card, probably the best ATi other than the X1950, but I find the TBM on 256 probably wants to be between 100 and 160. That is not set in stone because its a area that you need to test fly. A sign of a low TBM is city skyscraper textures "popping" in when you change views. That can also be caused by the FFTF being too high and pulling too much CPU time from the rendering engine. A sign it is too high is microstutters or dragging that seems to be worse in turns.

As for city stutters... SP1 is coming however I can make some suggestions to try between now and then.

Since you are on a 256MB card, I think you are going to have to pull back on the Scenery Complexity slider. That is what controls much of the city tower and buildings. If you have it at 100% pull it back to 50% and see if the stutters stop. If they do, raise it to 75% and see if they remain gone.

As I said, I can throw some calculated values out to you, but I do not know how they will work with that older card and P4. Give me a day or so to look it over when I get time. I may need to know a few other things about your system, one of which is if you running 1T command on the memory or 2T. Your BIOS should have that setting available in the manual memory timing unless its some type of OEM motherboard.

Not all memory can run 1T. The system may crash using the 1T command but if you are running 2T, that change to 1T will boost things by as much as 5-10% depending on the system.

[Nick N]

It would also require I know exactly how ALL the settings are right now.. Go to this post and tell me what you are set to based on the images of the sliders and check boxes

http://www.simviation.com/cgi-bin/yabb2 ... 7609/45#50

[macca22au]

Nick: it happens almost every time with a glass cockpit aircraft.  I use only VC because I run a Matrox Triple Head2Go arrangement which I know takes framerates but gives an extraordinary experience across 3000+ pixels. I can get a basic aircraft, the 172 and 208 through the barrier into smooth flight again.  It happened to me once when I had the framerates locked too low, but it still occured when I moved frames to unlimited.  Incidentally I am a careful defragger and use Ultimate Defrag.  File/name defrag is the option I use.  One problem maybe is that after a clean install of Vista two weeks ago the system has put most files into archive against the centre of the disk.  I will need to read up on how to ensure all of FSX and Horizon are on the outer part of the disk.  Also I have adopted a 2000/1000 trees, building ratio and this may not be optimal either.

[DizZa]

Ok.

My computer is OEM with a crappy BIOS, so, as it is OEM let's just assume it uses 2T command rate.

Here are some settings out of my fsX.cfg:
[Display]

[ATI_7500]

I assume your frame lock is 20?

Yep.

Might try dropping it to 19 or 18.

[Nick N]

[quote]Ok.

My computer is OEM with a crappy BIOS, so, as it is OEM let's just assume it uses 2T command rate.

Here are some settings out of my fsX.cfg:
[Display]