Originally Posted by kzinti1
If Windows is a major problem with stuttering, then why can't they develop a user-switchable "gaming mode" to make the OS prioritize the resources of the OS in favor of the games and their rendering processes?
It's not about the OS per se, a lot of dev work can be done on drivers and applications to reduce latency. This takes longer than what the average developer will deal with, so you get the "shoddy port" aspect going. You can get some really good examples of low latency on Windows, some pro audio setups can achieve some really good latency numbers. I've herd lower than 10ms can be achieved, which is pretty decent. The issue with this is, you have to have a very clean system. Disable anything non-essential, a stripped down windows (might even remove functions you may enjoy but do not require, when I mean bare bones it's bare bones).
Linux allows for things to be done in a similar way, you just have more control and an easier time getting latencies. Linux can easily get 5ms or lower, build a low latency kernel (with other tweaks). That's how OSX get's low latency setups, they do some pretty good custom work. As well as hardware control, another topic for another day I suppose. Don't listen to Collins, it can be done and could be done. The articles however aren't talking about that low of a setup, they are taking the standard desktop and probably using that as a base. So they want to shave off latency from their applications, which helps the issue regardless of a user's system.
Think of it this way, if your program adds 15ms of latency and you can shave that down to 10ms. Well, every person regardless of their system setup is going to get a performance boost. So you have done a good job as being an efficient programmer. That's what they are talking about, finding ways to use the D3D/OGL API so that you get the same result (pretty game) with a lower latency. That improves frames more. Or if you are a hardware manufacturer, the same applies. if your driver can cut out a few ms of latency you get boosts all around. Depending on the function call and what area of the driver (or software) you are trying to tighten up.
He is right about the general setups, both Linux/Windows aren't normally distributed with latency in mind. Windows especially so, Linux generally so.
 Haha, I just decided to read the article again. I guess they are including the latency issues of the OS. However as far as the desktop itself goes, when most people talk about latency issues it isn't directed towards the OS. The idea that AMD has a huge variance in latency times, instead of a constant, is what a lot of the fuss is about. You look at the Nvidia side, they comment how it doesn't vary as much. This was to indicate AMD is having some driver issues, something in the stack isn't running smoothly. Since the only difference in the stack is the hardware and drivers (assuming so), the problem should be with the variables. Meaning, AMD has an issue with the stack. Thus they have worse latency issues, should be fixed.
The whole article to me reads as an excuse for AMD to push off their driver issues. I find that displeasing, probably a PR move to save face. Lame.Edited by mushroomboy - 3/27/13 at 1:04am