Quote:
Originally Posted by
Paratrooper1n0 
Quote:
Originally Posted by
almighty15 
Quote:
Originally Posted by
Paratrooper1n0
That is wrong? Weird, cause I have proof. Skyrim and COD are two games that do not come with 2k textures on the PC version, thus not 1080p native.
Talking about not reading properly, you just gave an example. The rest of your response is nothing be sidestepping from the conversation.
Texture resolution and rendered resolution are 2 completely different, unrelated things....
Quote:
Originally Posted by
lordikon 
You should probably stop now. Suffice to say, you're not educated on the subject in which you're trying to make a point.
Texture resolution has nothing to do with screen resolution. Texture resolution is the size (in pixels) of the texture file. The resolution that a texture renders to the screen is based on a multitude of run-time factors, of which screen resolution is only one of them.
As was previously mentioned, PC games do not up-scale the final render. The only scaling in PC games is during anti-aliasing techniques, in which the game is rendering at a resolution higher than the final render resolution, and then downscaled back to the final render resolution.
Wow, now I am being insulted by two people. I NEVER claimed render = texture. I know the difference. I know what a games native resolution means. And I know what a games render resolution means. They are completely different. Sorry to say, but you lack some ability to read. COD renders at 1080p on all platforms. But that does not make it native.
I'm not insulting you, I'm just saying that you don't know what you're talking about.
Your quote:
Quote:
That is wrong? Weird, cause I have proof. Skyrim and COD are two games that do not come with 2k textures on the PC version, thus not 1080p native.
Every game on PC renders at native resolution, regardless of what resolution that may be (with some extreme exceptions like games that may not support certain high resolutions like the retina macbook use). You mention that Skyrim and COD are games that somehow are not rendering at native resolution, and you bring textures into the conversation, when those have nothing to do with render resolution in any way.
So I wouldn't say I misunderstood what you wrote. Maybe you misspoke?
Quote:
Originally Posted by
Hukkel 
Quote:
Originally Posted by
almighty15 
How long is a piece of string? Until we know the actualy clocks they'll be running at we have no idea, but historically EVERY console ever released has been bandwidth limited towards to end of its life
But we're going off topic now. I asked if clockspeeds mattered for cards and you said nope..not a thing. Now we're talking bandwith and lifecycles. In general clockspeeds matter to performance correct? And so does architecture. So even if the hd6670 would have the same rops and whatnot the clockspeeds and architecture would still up the performance by a great lot.
Increasing clock speed only matters in cases where you're not limited by a bottleneck elsewhere. For example you'll often see CPU benchmarks for games in which the resolution is set very low, this is to force the CPU to become the bottleneck in the benchmark. If the GPU is waiting on the CPU to complete its tasks before it can start rendering, then speeding up the GPU will not net you much of a gain because it's still waiting the same amount of time for the CPU. That's just one example, often the bottleneck can be a specific part of the GPU that won't be affected by a clock-speed increase. For example if the bottleneck is that you're waiting on memory access, increasing the core clock speed will not increase your framerate by much at all, because the memory is the bottleneck and the GPU is still waiting on the memory just as much as before.
I'm not arguing whether or not there is a bottleneck in this case, I haven't done any research into the GPUs that we're talking about, I'm just explaining why an increase in clocks will not always increase framerate.
Edited by lordikon - 11/13/12 at 11:38am