> Note that different 3d apis have different requirements - ideally we > should be able to choose some state which suits all of them. > In particular, d3d10/11 have a separate filter mode for aniso (which > applies to all of min/mag/mip filters at the same time). > d3d9 also has special aniso filter, but it can be set separately for min > and mag - apart from aniso d3d9 also has some more filters like 4-sample > tent/guassian, all of them with undefined results if used as mip filter. > max aniso values with d3d can be from (uint) 1 to 16, and I haven't seen > hardware yet which could use float values for that. > > So it seems for conformant d3d9 (but not d3d10) implementation you'll > need to be able to enable aniso for min/mag separately. > Maybe we could, in addition to this change, split max_anisotropy into max_min_anisotropy and max_mag_anisotropy. That should handle any possible API (unless some cards really give meaning to an anisotropic mipfilter).
However, is anisotropic magnification really meaningful? On R300, anisotropic magnification can be set, but does it do anything different than bilinear? If so, what?
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
