@casseveritt @nothings @g_truc I mean, as compared to "just a transform"... the viewport "takes the planes with it", so to speak.
-
-
Replying to @cmuratori
@cmuratori@casseveritt@g_truc The clipping planes are hardwired. The viewport is one of several transforms that get you to clip space.1 reply 0 retweets 0 likes -
Replying to @nothings
@nothings@casseveritt@g_truc But it's not, right. I mean, yes, it is a "transform" in the broad sense of the word...1 reply 0 retweets 0 likes -
Replying to @cmuratori
@nothings@casseveritt@g_truc But other transforms cannot affect where things are _after_ clipping. Does that make sense?1 reply 0 retweets 0 likes -
Replying to @cmuratori
@nothings@casseveritt@g_truc So I feel like it is disingenuous to say it is "just a transform", when it has a property others don't.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@casseveritt@g_truc No idea what you mean. https://www.opengl.org/wiki/Vertex_Transformation#Step_4_:_Getting_to_window_space …2 replies 0 retweets 0 likes -
Replying to @nothings
@cmuratori@casseveritt@g_truc I guess it's different in that happens after clipping, so you can think of it as defining space of clipping.2 replies 0 retweets 0 likes -
Replying to @nothings
@cmuratori@casseveritt@g_truc But it's better to *not* think of it that way so you can understand e.g. why it doesn't clip glClear.2 replies 0 retweets 0 likes -
Replying to @nothings
@nothings@casseveritt@g_truc I think of it as making good sense because glClear isn't a primitive, so it isn't clipped.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@nothings@casseveritt@g_truc Ie., it doesn't matter what happened in normalized space, because the clear is about pixels.1 reply 0 retweets 0 likes
@nothings @casseveritt @g_truc But, either or, "good sense" is a nebulous thing whenever 3D APIs are concerned anyway :P
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.