I think a fairer statment would be that duels run most default scenery as well as a quad, and it sure was not what we had hoped for, but when loading highly detailed landscapes and add-ons quads hang in there much better than duels delivering a steadier frame rate as well as maintaining the drawing of terrain textures when the duels just can not not keep up and the terrain starts to turn in to a blur, and there is a real benefit for more cores. - ALL testing done on SP2.Hopefully the dye-shrink and larger cache will yeild even better frequencies and a steadier bottom end to the memory subsystem..I am looking forward to trying, but am as everyone else a bit reserved about it esp considering the price.As far as the number of cores FSX has been programed to runActually both Phil and Sueng Woo Kim have siad that FSX is programed to handle up to 32 cores."As far as practical limits on number of usable cores, currently SetThreadAffinityMask onlyallows explicit scheduling of threads on 32 cores (the mask is a dword) on Win32. So that's oureffective limit on number of cores. But as soon as there is a way to explicitly schedule them, we canhandle 256 cores.

I think a fairer statment would be that duels run most default scenery as well as a quad, and it sure was not what we had hoped for, but when loading highly detailed landscapes and add-ons quads hang in there much better than duels delivering a steadier frame rate as well as maintaining the drawing of terrain textures when the duels just can not not keep up and the terrain starts to turn in to a blur, and there is a real benefit for more cores. - ALL testing done on SP2.Hopefully the dye-shrink and larger cache will yeild even better frequencies and a steadier bottom end to the memory subsystem..I am looking forward to trying, but am as everyone else a bit reserved about it esp considering the price.As far as the number of cores FSX has been programed to runActually both Phil and Sueng Woo Kim have siad that FSX is programed to handle up to 32 cores."As far as practical limits on number of usable cores, currently SetThreadAffinityMask onlyallows explicit scheduling of threads on 32 cores (the mask is a dword) on Win32. So that's oureffective limit on number of cores. But as soon as there is a way to explicitly schedule them, we canhandle 256 cores.