- May 16, 2011
- 1,430 (0.31/day)
- A frozen turdberg.
|System Name||Runs Smooth|
|Motherboard||Crosshair V Formula Z|
|Cooling||Corsair H110 with AeroCool Shark 140mm fans|
|Memory||16GB G-skill Trident X 1866 Cl. 8|
|Video Card(s)||HIS 7970 IceQ X² GHZ Edition|
|Storage||OCZ Vector 256GB SSD & 1Tb piece of crap|
|Case||NZXT Phantom 820 matte black|
|Power Supply||NZXT Hale90 V2 850 watt|
|Software||Windows 7 Pro|
|Benchmark Scores||Lesbians are hot!!!|
Of course.... Dual core optimiser was more of a patch that helped 'sync' some programs that had some timing issues when it came to dual core.
A good example of this would be CoD:UO - the first map in the SP stage where your in the forrest. sometimes things wont spawn or scripts that are ment to happen at a certain time dont happen at all.
It didnt really boost performance of Windows per se but when it came to programs that need to bypass Windows API for timing thus fixing some of the problems some games were having.
plus even WITHOUT the dual core optimiser patch installed, it hardly made a difference to benchmarks at all in my experience. you could live without it and never know it existed.
People are looking at this patch from M$ like its some holy grail of patches and its gonna bring balance to the force when its not going to do shit all. If M$ are truely capable of making a CPU shine just by patching it then why the hell would we need such powerful processors??? We could be any cheap ass low-end multicored CPU and just have M$ write a patch that optimises the hell out of it.
With that being said... you could put Michael Schumacher in a banged up Ford Cortina and he will drive like a boss and put on a world class performance, but at the same time. he wont win any races. because a driver is only as good as his car. and the car totally sucks at this juncture of all junctures.
What a nicely written post just to say that BD sucks and it always will suck. I already knew that though.