FSX-SP1 released!!!

[Nick N]

I need to hit the sack

It been a long day for me and not very productive when it comes to this sim.

[DizZa]

My scenery Radius is at 4.5 or large and it runs good with the same numbers but at very dense. At the moment I am looking at fighting blurries and raising frame lock so I'm keeping it down at dense.

Thanks anyways.

[Nick N]

My scenery Radius is at 4.5 or large and it runs good with the same numbers but at very dense. At the moment I am looking at fighting blurries and raising frame lock so I'm keeping it down at dense.

Thanks anyways.

good luck


Careful with SWAP_WAIT_TIMEOUT because that one can cause stutters and drag FR down if not set right. Some find raising it is better than loweing. All my systems I keep it at default (I do not put it in the config)

[macca22au]

I have just finished uninstalling FSX and all add-ons, reinstalled FSX and the SP1.  File/Name Defragged twice which ate up time,  but the  result has been quite phenomenal.  Scenery complexity maxed and autogen very dense over the centre of New York at over 20fps and smooth.  It was never like this before.  I left the autogen numbers at the default, but on your advice inserted the Job Scheduler and numbers for the dual core, and the TTTF at the default 0.33.  There are still some hitches but none of the harsh stutters that made the experience so unpleasant before.  Negatives: I have got to fight the blurries, and yes the autogen pops up in a close radius without merging into the distance which gives a more than unreal character to a large city.  But for a start I have to report that with the 6700 CPU and the 8800GTX the lift has been quite extraordinary.  Tomorrow night I will start to add back the aircraft and scenery and see what that does to the game, but first impressions are of a much better than dreamed of improvement.

[ATI_7500]

Someone in another forum posted that setting PerfBucket= ten times his default size improved things for him.

My values:
ProcSpeed=8841
PerfBucket=7

(C2D E6600 @ 3Ghz (OC))

[Nick N]

The deal with those numbers is unknown at this point. I need to have a discussion with a few people in the loop about what does what.

The list PTaylor posted was nice but what I do not like is the lack of support with setting suggestions. To post

[macca22au]

So what would you suggest for processor speed and Perfbucket for the dual core 6700 unclocked?

[DizZa]

To post [ch8220]this may help with blurs[ch8221] settings and not explain them completely or how to use them right is just plain lazy and does nothing but make things worse.

.
I see in so many forums people recommending a SWAP_WAIT_TIMEOUT of 120. Laugh my ass of at them idiots! Phil really should of explained them.

[Pappy44]

[quote]I'm having trouble getting SP1 to install.

[Milo1272]

Pappy44,

I didn't find a fix to my problem, so I eventually un-installed and then re-installed FSX.

[ATI_7500]

Both PerfBucket=9 (or 1) and ProcSpeed=4420 didn't do anything. I also tried the AutogenDescriptions_Min, to see if that one does something, but also to no avail.

Honestly, I'm this close (->  <-) to reverting back to pre-SP1 state followed by a incredibly rude e-mail to Aces and MS.


P.S: LOD_Detail_Radius can now be more than 4.5 without crashing FS. Downsides are increased loading times and no visual advantage.

P.P.S: I want a new engine in FS XI. The FS8 (or even FS7) engine is at its limits.

[Nick N]

[quote]Both PerfBucket=9 (or 1) and ProcSpeed=4420 didn't do anything. I also tried the AutogenDescriptions_Min, to see if that one does something, but also to no avail.

Honestly, I'm this close (->

[richardd43]

Well, I reset my Bios back to default then tightened up the memory settings (4,4,3,10,T1,2.1v), set the FSX sliders to high, installed the recommended tweaks in the cfg file and the sim works flawlessly (22fps over the city and 30 over terrain).

Depending on room temperature I can sometimes set AG to dense and/or very dense and get a good flight but everytime I turn on the computer it seems to react differently to the higher settings. What works on one boot up is not guaranteed to work on the next boot.

I still get a white screen for about a second occasionally but all of the stutters are gone and I have never experienced the blurries (or did not know what to look for)

As far as dual core goes I watch the screen on my G15 keyboard and the activity is no different than any other program. 60% seems to be the average useage of the cores. Core one is the dominate core but I have seen core two go dominate on occasion.

Memory (2G) never goes above 65% so I see no need for massive amounts of RAM.

I agree with the complete re-write, this is rediculous.

When FS9 came out my old computer needed to be replaced so I built my first computer to run the sim. the only tweaking needed was to my stupid choice of GPU. Replaced that, turned the sliders up and was set to go. It is hard to believe we need all of the tweaks to make FSX work.

[macca22au]

For some reason the blurries cured themselves, why I don't know. I did nothing.  But the stutters returned.  So I started the whole routine of trying to get lower trees/building numbers in the 2:1 ratio and it all got worse.  Then I added in the SWAP routine and nothing happened.  So in frustration I ditched the lot.  I pulled complexity back to Very Dense, left autogen on Normal and I'm getting highly acceptable performance.  The Jobscheduler is still in there, TTTF is there, but at default, and I bumped TBM up to 120, but the rest is default.  And I am now quite enjoying FSX.  I know that the autogen numbers are too high, but until some more definitive understanding is reached, I'll stick to this for a while.  It is an utterly frustrating game, and it is fundamentally useless for a home user to fly out of the box.  Also I think retailers should have to put stickers on the box to tell purchasers to install SP1.  Commercially it must be real mess.

[Nick N]

Well, I reset my Bios back to default then tightened up the memory settings (4,4,3,10,T1,2.1v), set the FSX sliders to high, installed the recommended tweaks in the cfg file and the sim works flawlessly (22fps over the city and 30 over terrain).

Depending on room temperature I can sometimes set AG to dense and/or very dense and get a good flight but everytime I turn on the computer it seems to react differently to the higher settings. What works on one boot up is not guaranteed to work on the next boot.

I still get a white screen for about a second occasionally but all of the stutters are gone and I have never experienced the blurries (or did not know what to look for)

As far as dual core goes I watch the screen on my G15 keyboard and the activity is no different than any other program. 60% seems to be the average useage of the cores. Core one is the dominate core but I have seen core two go dominate on occasion.

Memory (2G) never goes above 65% so I see no need for massive amounts of RAM.

I agree with the complete re-write, this is rediculous.

When FS9 came out my old computer needed to be replaced so I built my first computer to run the sim. the only tweaking needed was to my stupid choice of GPU. Replaced that, turned the sliders up and was set to go. It is hard to believe we need all of the tweaks to make FSX work.

Richard, work the lowest latency you can and at the same time, bump the FSB to raise the CPU/FSB frequency a bit. You may need to play with mem timing a tad to allow a 220-230 clock in that area running 1T. I think your best bet is to run low latency with a just a bit of a CPU boost. I started to look over your info and ran a bit short on time between setting up my grandsons tower for SP1 and everything else going on this past weekend. I did not forget about you and will send along some things to try based on mild clock running low latency. I may even be underway before I get a chance to send it but will be available to go back and forth a bit and see if we can