FSX-SP1 released!!!

[DizZa]

ProcSpeed=3465
PerfBucket=5

[Nick N]

ProcSpeed=3465
PerfBucket=5

I did not elaborate enough

single or dual core? and is it overclocked? If so I need to know to BASE and the Clocked speed

[Camel_Moe]

Before I go to bed, FYI, The TBM and FFTF values Nick just listed (Max of 160 and .35) are not in the range of what I think is considered abusive use. Just wanted to mention that before someone confused my mention of points listed in PTaylors blog with a dirrect mention of my opinion of the values discussed.
In fact they seem reasonable.  More than reasonable compared to the 500 and 3.0 values quoted to me by other sources tonite in fact.
Didn't want to start any flame wars after I leave...

G'niters

[Nick N]

[quote]Before I go to bed, FYI, The TBM and FFTF values Nick just listed (Max of 160 and .35) are not in the range of what I think is considered abusive use. Just wanted to mention that before someone confused my mention of points listed in PTaylors blog with a dirrect mention of my opinion of the values discussed.
In fact they seem reasonable.

[DizZa]

ProcSpeed=3465
PerfBucket=5

Single core P4 650, default clock is 3391.5mhz and that's what it's at. What's base?

[Nick N]

ProcSpeed=3465
PerfBucket=5

Single core P4 650, default clock is 3391.5mhz and that's what it's at. What's base?

OK

I assume its a hyperthread processor. If so, use the jobscheduler affinity of 1

As for the the other numbers, see if this changes things:

ProcSpeed=2598
PerfBucket=6


I have not tested or worked with a P4 so make sure you save the original values to put them back. If that has a possitive affect, leave the PerfBucket @ 6 and lower the ProcSpeed to 2200.


Let me know what you find. Its about smooth more than frames


You may not see anything. What I found was those variables will change things if others are in place correctly such as AG.

[Keep It Simple]

It seems that with SP1 CAVU conditions are no longer possible even with user defined weather.
There is always a constant haze that can't be eliminate.

One has to assume the purpose is to help mask the "blurries".

[Camel_Moe]

has always been the MAX TBM, and still is. In SP1 it will cause major stutters above 200 if other variables are set high but it can be raised considerably more than 160 if a video card has 512mb+ and the sliders/AG are not excessively high. It will take up the slack in the balance but the visual appeal is not very good.

Up until SP1 up to 400 TBM was possible. FFTF was a great way to tweak the terrain but now that is only for single core processors. Dual Core no longer has that option

Yup, pretty much my point.

[DizZa]

Wtf? I changed my TBM from 144 to 60 and noticed no diferance. I also changed FTTF from .52 (Don't ask) to .33 and no diferance. I changed SWAP_WAIT_TIMEOUT=xx to 1.3333 times my framelock and blurries are pretty much GONE, and that was flying with loads of autogen at 300knots over a city!

Hang on Nick I'll try that now.

[Nick N]

Wtf? I changed my TBM from 144 to 60 and noticed no diferance. I also changed FTTF from .52 (Don't ask) to .33 and no diferance. I changed SWAP_WAIT_TIMEOUT=xx to 1.3333 times my framelock and blurries are pretty much GONE, and that was flying with loads of autogen at 300knots over a city!

Hang on Nick I'll try that now.

That is the other value I have not gotten into yet but you did the right thing by dropping TBM and FFTF... now it may tune in. leave those where they are and work the other areas.. especially AG numbers and try the MipBias settings I suggested

[Camel_Moe]

Sheesh, now that it looks like you guys are onto something, I can't log off. To interesting to watch.  ;D

[DizZa]

Mipbias caused the trees to flicker. Leaving it at default. Autogen is 600/300 Dense, runs very nicely.

Ummmmm. I NOTICED no diferance with the ProcSpeed=2598

[DizZa]

2200 did little or nothing. I couldn't notice anything.

[Nick N]

2200 did little or nothing. I couldn't notice anything.

Fine. That tweak may only work for AMD dual core processors. Put them back to default, however, you may want to see if raising that ProcSpeed value to 3800 causes a change. Usually if that value is too high it will cause the system to drag.


As for SWAP_WAIT_TIMEOUT=

[Nick N]

Autogen is 600/300 Dense, runs very nicely.

That seems a bit low. 600/300 was FS9-FSX before SP1.

Have you tried raising to 960/480 ? and even bump that up to very dense or 100% just to see what would happen?

By the way, I found it best to let the card handle AA but let the sim handle AF... application preference with Anso enabled in the sim