Hi folks,

I have been using a (Min,Mag,Mip) all Linear, in my effects file. With a ps_2_0 compile option, can I assume that my GPU will always be capable to support Anisotropy? I know that it's always safer to define an alternate 2D sampler for anisotropy filtering, and use that technique when GPU caps indicate the anisotropic support. But isn't ps_2_0 already sort of ensuring those capabilities?

On a side note, I am observing a pixel-wide edge on top and left of my rendering window, which kinda looks like some sort of noise that is imitating the main window. Is this some filtering related issue or something else?

I am using direct3d9 APIs for rendering.

Thanks for the response Niko. About the Anisotropy deal, I am much more convinced about my approach to the filtering schemes, as per your suggestion.

For the side note, well I am simply rendering the local cam capture frames in windowed mode. There is no "blitting" involved, I am simply picking up the texture from the channel which is the one on which the captured frames are being delivered. As for the render target dimensions, I am doing a GetClientRect for calculating the backbuffer dimensions.

This one is a real puzzle for me now. I have been at it since months now, but can't seem to understand that why I am getting these noisy edges only on windows, but not on Mac (using OpenGL there), when my rendering flow is exactly the same for both platforms.

Btw, this issue got solved. I found out that pixel offsets were not being calculated properly for Vertices. Used the standard +1/height, -1/width correction logic and works well now. This thread may be marked as solved and closed now.