I've no idea if the order is really important or if this just hides another problem, maybe someone with databooks could answer that.
I don't remember seeing any clear information about this in the docs I have, but your patch is proof enough for me that it does matter. :)
Yes - at a certain point card behaviours cease to be documented, and we are at that point now.
On Fri, 2004-01-09 at 13:58, Felix KÃhling wrote:
Since the number of texture units is going to be configurable [...]
I thought this won't be necessary with the new t_vertex stuff?
I agree - I don't really understand why it is at all desirable to make this configurable. The only area it makes a difference is in the calculations of the maximum texture size, and I'm in agreement with Ian's proposal that those calculations be removed and we just fallback if anyone tries to bind 6 2kx2k textures with full mipmaps.
Keith
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
