QUOTE (GenMatrix @ Aug 4 2009, 07:59 AM)

Okay, so it uses more CPU than it should. Shouldn't really be a problem unless you're using a program that is CPU intensive such as gaming/rendering/video editing. And even still when those programs are doing their thing, you shouldn't be trying to pull resources from it anyway. The only group I could see this affecting are with people who have ancient computers with crappy CPU's.
When it comes to your "It's been 8 years WTF MICROSOFT" statement, I'm not exactly sure what your point is. I'm not extremely savvy on how making an operating system works, but I'm sure they choose to have the CPU render the GUI for compatibility rather than performance. Either way, you call it a problem yet haven't given a clear cut example like "Oh man, my program fails to function because the GUI renders so damn slow!". So I still find this whole thing meaningless nitpicking.
They choose software render because they found too difficult to combine the new graphical engine with the old one. If you want to learn more about it read this:
http://blogs.msdn.com/directx/archive/2009...in-windows.aspxGDI has dozens of functions:
http://msdn.microsoft.com/en-us/library/dd...28VS.85%29.aspxGDI hardware acceleration in Windows 7 using WDDM 1.1 drivers has only these functions hardware accelerated:
http://msdn.microsoft.com/en-us/library/dd434692.aspxI show in the video how slow is the services.msc window, and the graphical artifacts it has, but it's not the only one. Probably is one of the applications where this issue is more easily spotted but there are many others in a lesser degree depending on how they call GDI functions.
Windows 7 has several integrated solutions to circumvent the lack of 2d graphical acceleration...the problem is those solutions require full rewrite of the every single application's gui in order to use the new direct2d and directwrite, including the ones bundled with the os (file explorer, dialog boxes, management windows, etc...) and that's not going to happen in years, not from Microsoft itself, nor from 3rd party developers. I don't see Adobe porting their suite to Direct2D any soon..and anyway, the system will always stay GDI/GDI+ based. Probably until the next Windows version.
What I explain in the video is a reality, it have been already discussed for years since Vista was released (the problem started there), and many developers had complaints about. It's definetively not a false statement, and all you have to do to believe it is try it by yourself.
All of us had big expectations with Windows 7, but that doesn't mean we have to look away as if there were no problems and Windows 7 was finally the solution to all Vista problems. Windows 7 have some design problems, and the one regarding GDI is probably one of the biggests
We will not see any better results over the time other than the ones related with the improvement in cpu speeds.
WDDM 1.1 drivers makes mandatory this new "partial" GDI hardware acceleration. So any driver which claims to be 1.1 is already accelerating as much as it ever will.
Too bad, the results I got were based on WDDM 1.1 drivers (both from nvidia and Microsoft itself).
So this is all we get. Microsoft had to include this partial GDI acceleration, because those functions were way too slow in software mode, but it seems they thought the rest of them were not.....(which is not correct).
About the real world impact. I can clearly see the real world impact of this decision as soon as I boot Windows 7 and start working. There is people who's not able to see the difference between a game running at 60 fps from the same game running a 30 fps. There's also people not able to ear the difference between a 128kb mp3 and a real CD Audio.
All I can say is, there is a real difference, a difference you can meter, and at least me and some other people are able to feel in every day Windows 7 use.
Probably many people is blinded by the novelty and don't want to accept there are some problems with the new and overrated Microsoft system.
I think I will give up trying to make you people see the reality. It's really exhausting trying to demonstrate 1+1 = 2 over and over. The facts are there, I gave you the proofs, Microsoft addmited the problem, many developers complaint about, what else do you need?
bye