getalife wrote..Errrr no. Game engines don't move your crosshair over by screen pixels. They change the angle that you're facing. Again, this is just math that you never see.
guys its cause in low res when you move your mouse you have less pixels to cross over.
gg
Jessica wrote..Living proof! Amen to that.
If low res made you better, then Dice would be the best CS player ever.
Exo wrote..erm blatent boasting
it's so unfair trying to snipe at 1200x968.
I could use 1600x1200 with my ti4600..but I don't because I can't see anything useful on the scores board, plus I can read the text better at 1200.
Sublyme wrote..Read LuftWaffle's post. Pixels are simply a output issue. The game is MORE accurate than what is displayed on screen. All the values are 32-bit floating point values.
WRONG
LuftWaffle wrote..Arrogant loser.
Uhm. Everyone do yourselves a favor, skip over sublyme's post and go back to mine for a better explanation
LuftWaffle wrote..Ok pixels or no pixels its easier to aim at lower res. More control over your movement so post all you want and waste as much time as you want the game will never change.
Mmmm ok. Resolution doesn't change your accuracy at all, because the HL engine doesn't look at what pixel you're aiming at to determine if you hit the enemy. It's all done with bounding boxes and math that you never see. Even if the head was 70 times the size it is now that doesn't mean you'll hit it, in fact, you have less likely of a chance because you could be aiming at areas that aren't covered by the bounding box.
Errrr no. Game engines don't move your crosshair over by screen pixels. They change the angle that you're facing. Again, this is just math that you never see.
As far as whether or not this article is correct... well let me explain. Say your resolution is like, 100x100 and you draw a triangle on your screen. In this low of a resolution, you'll see jaggies on all of the edges. These jaggies actually poke outside of where the lines that bound the triangle actually are (mathematically). It's an approximation because of the low resolution. At higher resolutions you don't see the jaggies as much because the approximation is much closer to where the lines actually are. So, there COULD be a pixel out of place, but your eyes aren't sensitive enough to benefit from this, I believe.
Remember y = mx + b? Since mx could be a fraction of an integer, but there's no such thing as a fraction of a pixel, it has to be rounded one way or the other which results in out-of-place pixels. Of course this is just an example, game engines don't typically use y = mx + b anywhere in their code, but the same situation arises.. fractions of pixels that have to be approximated.
Comment