started watching this like "eh I'll just watch a few minutes to get the gist, I don't need a 44 minute explanation". ended up sitting through the entire thing (though on 1.5x). amazing lecture. learnt a lot. thanks
Re: device coordinates: this is not set in stone. Hardware typically uses top left because that's where the scanning starts, and most graphics API's follow that convention I think. The more "math-like" convention is typically bottom left, a bunch of image formats use that. I think Ken uses it here because that's what students are most accustomed to from graphs in their math courses. There are a lot of these conventions that are not standardized, like are front facing triangles clockwise or counter clockwise? How are depth buffer values encoded? Do you use a left or right handed and z-up or y-up coordinate system? Etc...
for antialiasing, can't you see the two points that an edge of a polygon intersects the square of a pixel? knowing those two points you can make the triangle that the polygon is occuping or not occuping in the pixel, knowing the area of the triangle you can get how much of the pixel that point with that color occupies
If someone knows: he didn't really explained how the horizontal scan between endpoints works Like, I know how to go from an x to the other by adding 1 to x and Z-inc to z, but when do you stop? You gotta do all the divisions and calculations for the uvs, rgbs and all of that for the other edge tracker? You only use it as an stopping point! As what is said in this lecture you don't use all that information from the other side I also don't know how to increment the uv coordinates as you go across, again verticaly is easy because you got information from the begining of the edge tracker to the end, but horizontally is a mistery if someone knows, those are my 2 questions - what is the use of the other edge tracker? appart from being an stoping point - how do you increment the uvs as you go across?
started watching this like "eh I'll just watch a few minutes to get the gist, I don't need a 44 minute explanation". ended up sitting through the entire thing (though on 1.5x). amazing lecture. learnt a lot. thanks
Re: device coordinates: this is not set in stone. Hardware typically uses top left because that's where the scanning starts, and most graphics API's follow that convention I think. The more "math-like" convention is typically bottom left, a bunch of image formats use that. I think Ken uses it here because that's what students are most accustomed to from graphs in their math courses. There are a lot of these conventions that are not standardized, like are front facing triangles clockwise or counter clockwise? How are depth buffer values encoded? Do you use a left or right handed and z-up or y-up coordinate system? Etc...
for antialiasing, can't you see the two points that an edge of a polygon intersects the square of a pixel? knowing those two points you can make the triangle that the polygon is occuping or not occuping in the pixel, knowing the area of the triangle you can get how much of the pixel that point with that color occupies
If someone knows: he didn't really explained how the horizontal scan between endpoints works
Like, I know how to go from an x to the other by adding 1 to x and Z-inc to z, but when do you stop?
You gotta do all the divisions and calculations for the uvs, rgbs and all of that for the other edge tracker?
You only use it as an stopping point!
As what is said in this lecture you don't use all that information from the other side
I also don't know how to increment the uv coordinates as you go across, again verticaly is easy because you got information from the begining of the edge tracker to the end, but horizontally is a mistery
if someone knows, those are my 2 questions
- what is the use of the other edge tracker? appart from being an stoping point
- how do you increment the uvs as you go across?
@6:00 device space 0,0 is top left
James Rockford why top left is 0,0 here y coordinate changes and x is 0