Well, I really dont notice any significant change in performace than before SP1, Usually I get 20 fps in clear days and between 15 and 20 in very dense cloudy day, now I get 2 or three more frames per seconds.CPU=Athlon 64 FX 55 (overclocked at 3.2 Ghz,MB= DFI CFX3200-DR/GMemory 2 GB DDR 400Video= Ati PCI-E Radeon X1900, 512 MB (overclocked)Windows Vista Business

Me too. A marginal increase in FPS in areas that annoyed me (say from 13 to 18 FPS), but none of this 100% better hype being splattered across this forum. I can still get low teen FPS in city areas with default detected settings (global high for all). Where is this 20+ FPS others are getting with similar or lesser rigs than mine?Also while dual core is more utilised, it is only sporadically where one core runs at 100% all the time and the other core spikes up to 75% for a second or so every 15 seconds. I am certainly not seeing a constant heavy load on the second core like others are.I thought I might have patched this puppy wrong, but that about window shows SP1 and I even tried a fresh reinstall with defrags between installation and SP1 update, but no great improvement.Am I missing something?Gary

If you are truly setting things to high in all menus, then that would give you water 2x mid, which comes with a large performance hit. Anything above 2x low does. That could be the problem. Also, you might try manually setting the core affinity, as outlined on phil taylor's blog. http://blogs.msdn.com/ptaylor/default.aspx First tweak. The best thing for you to do now is to post links to screenshots of your display settings and fsx.cfg.It will be easier for people to help.:)

Anyone with "older" systems have results? I have an AMD64 3200 / 2gb Ram / Geforce 6800. So far it seems everyone reporting results has the latest / greatest anyways, just curious what people with more modest systems can expect.

Hi All,I've got no problem with frame rates (70 to 100FPS) or SP1 installation (installed on clean FSX installation, no add-ons), but has anyone noticed a problem with real world weather downloads, after SP1 update, not actually downloading real world weather? It will go through the motions of downloading with no errors, but it shows the completely wrong weather on the map for the airport chosen. Example, I live across the street from and fly out of KPTB in real life. Today was 81F and thunderstorms. In FSX, I downloaded the weather and it showed as 65F, clear and calm. All of the stations in the area including KRIC showed the same weather in the area and the barometer was also incorrect. I cleared out my temp files and tried the connection test website listed in the MS support pages and I have no connection errors to the internet. I tried all night and it was 65F, clear and calm. Anyone else notice this?Thanks, David.

Yup, Danube is one of the rivers we fixed in Eastern Europe. Vistula was the other. The UK got a couple scenery fixes around rivers too. River/harbor areas and airports were the bulk of the scenery fixes. We still missed some, it was a matter of payload size. We really didnt want to be too far over 200m, and I still get a lot of private mail complaining at that.

anyone notice the railways are "ghosty" at night?sort of translucent, and you can see the underlying texture through them?I was looking at the rail yards in toronto at night and the textures underneath come right through with a rather odd effect...just me?go to CYTZ and just a bit north west of the CN tower facing north east at night and you can see what I'm talking about...cheers!Jonas

try unchecking the detail textures and see if that does anything.

5/13 is 38.5%, right in with my guidance.I also said some configs could show more. The only thing I can say is I dont see a pattern from the people showing the great returns, to the "within guidance" to the "not at all". It feels config related, since success stories seem to be running 10:1, but if we flush out something as a root cause that would be interesting data.To those not seeing the gains, we feel for you. Its just plain hard in the PC environment sometimes; given all the variables. But if there is a community that *could* figure out what the variable causing this is, it is this one. Keep at it.

I turned down water to low 2.x and it made neglible difference. I will try the core affinity tweak that you have suggested tomorrow, although, I am surprised that multicore support is not autodetected in the first place by SP1.

Has anyone tried the current add-on planes, such as the FeelThere Citation X or the Eaglesoft Hawker? I got noticable improvements using the default planes (30 to 50 fps and smooth), but when I try either of the add-ons, I get 10 to 17 fps and sluggish. AMD Athlon64 4000+Raptor 1502G Corsair RAMNvidia (or EENVEEDIA as my french teacher pronounces it) 8800 GTX

Don't get me wrong Phil, I am ecstatic that most people are getting the big perf boost that we all wanted - I just want to be one of them ;). My son has FSX installed on his computer (A64, 2G RAM, X800XT 256M) and his SP1 experience was much more pronounced. Looks like you guys have hit this one out of the ball park for most people - well done!Gary

Hi Dave! What part of Alaska you in?

Hi all,Just wanted to chime in with my experience, and so far it's been a great one. I have a high end rig (Core 2 Duo E6600 @ 3.6 Ghz, 4 Gigs of RAM, 2x 8800 GTX cards in SLI, nForce 680i board, Vista x64) but had always experienced (somewhat) mediocre FSX performance. My settings have been, and continue to be all sliders maxed to Ultra with no special tweaks applied, except that graphics is set to Custom (ultra settings plus 1900x1200 resolution with AA enabled.) Before, I was averaging 10 fps in dense cities (NYC and Chicago for example) with 30-40 FPS most every where else (UNLIMITED cap.) With SP1, I'm averaging 15-20 in the densest cities, but more importantly the framerate never drops below 10. In other areas I've seen as high as 60. I'm most impressed.Most important, however, is that SP1 seemed to have fixed my game-ruining CTD bug in which I would get an odd out of memory error after flying for a certain amount of time (usually around 20 minutes) or while trying to land at JFK (this would trigger it almost all the time.) Neither landing at JFK or flying for two hours caused a crash. I'm ecstatic as FSX is now playable as I had always hoped it would be.Kudos to the ACES team. Excellent work on this one!Mark.

We do try :-).I think the OP with this suggestion is saying that by dropping down to 3 cores instead of 4, that may level your perf out. Its worth a go.