http://bugs.freedesktop.org/show_bug.cgi?id=12054
------- Comment #13 from [EMAIL PROTECTED] 2007-08-19 04:11 PST ------- (In reply to comment #12) > It seems to me like WoW tried to use pbuffers (which aren't supported, you can > see some wine errors in the beginning about that), and somehow didn't notice > it never got a context handle for that... Does r200 need to support WGL_ARB_pbuffer, then? fglrx doesn't support any kind of pbuffer extension at all (unless it's core 2.0 functionality?). And I have no idea what a "WGL" extension is - I just read it from a list generated by "strings WoW.exe" :-). > It is possible that it simply needs pbuffers, or maybe it could alternatively > use fbo's but those aren't supported (with r200 driver) neither. And btw even > CopyTexImage2D alone would kill performance (currently not accelerated on > r200), unless the area to copy is _really_ small... It is a small area - but maybe not small enough. What would need adding to the r200 driver to accelerate CopyTexImage2D? (Please don't say "hardware" ;-) ) -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
