FSX & SLI

[justpassingthrough]

[quote][quote]

I'm sold...





and it fixed everything else too

[Black ZR-1]

Ok, put the FFTF back to .25 and drop the frame lock to 20

see if the textures are sharp like at .28 and it still flys smooth. If the textures are not good and flight is smooth, set it back to .28 but leave the frame lock at 20.

Ok that seemed to work

[Nick N]

Pretty neat little program. Only thing it found were a couple spyware.

http://djtaso.com/fsx/SanD.jpg

Have it as link so you can read it better.

You are running some excessive items. I need time to go over this list. This part is difficult because with some items I do not know what can be booted manually when needed and what must start with Windows. There is a way to back up the reg keys for testing however I do see some items that can go for sure....


For one, MS Messenger does not need to be booted with Windows and a shortcut to the desktop can be made so it is booted when the user needs it instead of having a network connection running to the MS servers. Network is one of the greatest resource hogs in Windows so if you do not need MS Messenger at Windows boot and for use during FS or game use, I suggest you open the program and uncheck the option to run at Windows start.

Limewire is the same. I see no reason for that software to need to boot at windows start.

I will look over the rest and comment back.

Still unpacking things here.

[Nick N]

Ok, put the FFTF back to .25 and drop the frame lock to 20

see if the textures are sharp like at .28 and it still flys smooth. If the textures are not good and flight is smooth, set it back to .28 but leave the frame lock at 20.

Ok that seemed to work

Good. I thought it would work. You and John have a similar setup right now. You have graphics power where he lacks and he has CPU/memory bandwidth where you lack. The numbers I am seeing fall in line with that assesment.

Now run the flights John posted. Use the direction and the flight levels, use the Maul and the 747 but reboot the computer between the 2

See how it all looks and feels. if you find the results are good and you like what you see, we will start looking at the hardware

[Black ZR-1]

I've been looking at that list as well and realized I have programs still running which I thought I didn't i.e. limewire (uninstalled now), msnger, fraps, etc. Making some changes now.

[Nick N]

I've been looking at that list as well and realized I have programs still running which I thought I didn't i.e. limewire (uninstalled now), msnger, fraps, etc. Making some changes now.

Thats good. Just do not delete any lines from Spybots because you can not recover once a line is deleted in that software. Shut down everything you do not need to boot the computer INCLUDING NTUNE

You do not need to uninstall, just check the preferences and disable starting with windows.

[justpassingthrough]

Ok, put the FFTF back to .25 and drop the frame lock to 20

see if the textures are sharp like at .28 and it still flys smooth. If the textures are not good and flight is smooth, set it back to .28 but leave the frame lock at 20.

Ok that seemed to work

That looks good! The lower FFTF will give you some headroom for other areas as the system gets tweaked. Mine was a tad blury at this point till the motherboard got the hot-rod treatment  

[Black ZR-1]

Ok, put the FFTF back to .25 and drop the frame lock to 20

see if the textures are sharp like at .28 and it still flys smooth. If the textures are not good and flight is smooth, set it back to .28 but leave the frame lock at 20.

Ok that seemed to work

Good. I thought it would work. You and John have a similar setup right now. You have graphics power where he lacks and he has CPU/memory bandwidth where you lack. The numbers I am seeing fall in line with that assesment.

Now run the flights John posted. Use the direction and the flight levels, use the Maul and the 747 but reboot the computer between the 2

See how it all looks and feels. if you find the results are good and you like what you see, we will start looking at the hardware

Well the 747 test flight didn't go to well. I had massive blurry spots all over the city. I did several passes at 4k & 7k feet so the cpu can have time to load them in memory but they were still there. I was flying over them too fast probably before they can sharpen up. I was going 250 - 300kts average.

And I rebooted like you said before my test flight.



EDIT: After flying around some more I've noticed the blurry spots have gone away. Only thing I see now are occasional ones from afar but quickly sharpen up when I approach them at say 6k feet.

[Nick N]

Ok, put the FFTF back to .25 and drop the frame lock to 20

see if the textures are sharp like at .28 and it still flys smooth. If the textures are not good and flight is smooth, set it back to .28 but leave the frame lock at 20.

Ok that seemed to work

Good. I thought it would work. You and John have a similar setup right now. You have graphics power where he lacks and he has CPU/memory bandwidth where you lack. The numbers I am seeing fall in line with that assesment.

Now run the flights John posted. Use the direction and the flight levels, use the Maul and the 747 but reboot the computer between the 2

See how it all looks and feels. if you find the results are good and you like what you see, we will start looking at the hardware

Well the 747 test flight didn't go to well. I had massive blurry spots all over the city. I did several passes at 4k & 7k feet so the cpu can have time to load them in memory but they were still there. I was flying over them too fast probably before they can sharpen up. I was going 250 - 300kts average.

And I rebooted like you said before my test flight.

Alright, then raise TTFT by .02 until that 747 flight sharpens up. I'll bet it works fine at .28

Is the flight feeling good? No stutters? nice and smooth?

You see now why we use the Maul and the 747. Each produces a different load based on the speed and altitude factors along with the models loading differently

No need to reboot between, just the sim between tests. leave frame lock at 20.

Did you change the TBM? or have you left it at 400?

[Black ZR-1]

I would like you to download this software:

http://www.cpuid.com/download/cpu-z-139.zip


Grab a screen shot of every tab (except the last one) and post it here. I need to see that data


Repost a screen of Spybots start list after you have removed as many items as you can through the software interfaces or by uninstalling what you know for sure do not need or want.

http://djtaso.com/fsx/SanD2.jpg

Can't figure out how to disable nview & realplayer from starting..

[Black ZR-1]

Alright, then raise TTFT by .02 until that 747 flight sharpens up. I'll bet it works fine at .28

Is the flight feeling good? No stutters? nice and smooth?

You see now why we use the Maul and the 747. Each produces a different load based on the speed and altitude factors along with the models loading differently

No need to reboot between, just the sim between tests. leave frame lock at 20.

Did you change the TBM? or have you left it at 400?

yup, it did it.

Flys smooth. Only stutters when I pan around the plane in spotview.

[Nick N]

I would like you to download this software:

http://www.cpuid.com/download/cpu-z-139.zip


Grab a screen shot of every tab (except the last one) and post it here. I need to see that data


Repost a screen of Spybots start list after you have removed as many items as you can through the software interfaces or by uninstalling what you know for sure do not need or want.

http://djtaso.com/fsx/SanD2.jpg

Can't figure out how to disable nview & realplayer from starting..

I already see a problem with the hardware. The memory SPD is not reading the sticks correctly. It has their timing completely wrong. It should read 4-4-4-12. trc is something I have to check the specs for. You are suffereing in this area and it needs to get corrected. We also need to get you running 1:1 with the processor instead of 4:5


Real player is a pain. They hide the setting so its not easy to find. Dont worry about it, we will manually delete the line in Spybots.

[Nick N]

Alright, then raise TTFT by .02 until that 747 flight sharpens up. I'll bet it works fine at .28

Is the flight feeling good? No stutters? nice and smooth?

You see now why we use the Maul and the 747. Each produces a different load based on the speed and altitude factors along with the models loading differently

No need to reboot between, just the sim between tests. leave frame lock at 20.

Did you change the TBM? or have you left it at 400?

yup, it did it.

Flys smooth. Only stutters when I pan around the plane in spotview.

a touch of pan stumble -can be- normal until SP1 is released however setting up the hardware is going to change that too

OK, I think we are ready to look at the BIOS... I am reading here so give me a few minutes to look up the JEDEC specs on the chips

[Nick N]

Before we go any further, I need to know the level of understanding you have about a BIOS. I saw earlier in this thread you do know how to over-clock however moving a slider and making changes in NTune is not experience enough for me to feel comfortable about you entering the BIOS and making changes.

Please answer the following

1. Do you know how to get into the BIOS and do you know how to set it up manually?

2. Do you feel comfortable about making changes in a BIOS you may not understand?

3. Do you know how to reset the BIOS from the keyboard (if needed) and the CMOS (if needed) (the CLear CMOS jumper on the motherboard) in case an overclock setting may cause a temporary no-boot condition?

4. If the above condition were to occur, do you know what to set in the BIOS to get the system back up and running as it is now?

5, Do you accept the responsibility for making BIOS changes?

Please understand that I am not sitting in front of the computer and must rely on you to make changes which can present unknown results. I will never suggest something I believe is dangerous but I must know if you feel comfortable starting this process and working through it.

[Black ZR-1]

Please answer the following

1. Do you know how to get into the BIOS and do you know how to set it up manually?

2. Do you feel comfortable about making changes in a BIOS you may not understand?

3. Do you know how to reset the BIOS from the keyboard (if needed) and the CMOS (if needed) (the CLear CMOS jumper on the motherboard) in case an overclock setting may cause a temporary no-boot condition?

4. If the above condition were to occur, do you know what to set in the BIOS to get the system back up and running as it is now?

5, Do you accept the responsibility for making BIOS changes?

1. Yes.

2. Yes.

3. Yes. I can also clear CMOS by taking out the battery & putting back in if I have to.

4. Yes.

5. Yes.