Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=8250          
     




------- Additional Comments From [EMAIL PROTECTED]  2006-12-13 02:51 -------
(In reply to comment #56)
> - Wait for Blizzard to do something - although its last patch made things 
> worse,
> not better, and so I'm not expecting anything to happen any time soon.
> - Scan the WoW executable / data files for the slim chance that the vertex
> programs are in clear-text, and then hack them myself somehow - which might 
> just
> break Blizzard's EULA.
It's not the vertex programs as such which really make problems, so it wouldn't
work. And I'd bet they'd have some anti-cheat code in there anyway.

> - Run without GL_ARB_vertex_program enabled (which is what I do now),
> effectively downgrading my R200 to an R100 or something.
> 
> I happen to have a Radeon 9550 card lying around, but even if Mesa did support
> this card as well as the Radeon 9200 series, the r300_dri.so would surely 
> choke
> on the vertex programs as badly as the r200_dri.so driver does. And similarly
> for any i965-based hardware too.
Indeed. To give some background why it's problematic to fix up, the vertex
programs really aren't all that hard to fix. We already have that small hack to
just ignore the error if a vertex program tries to use the weight input. That's
basically all that's needed, the drivers just need to make sure this input gets
routed correctly. But the trouble really is with how the data gets into mesa. To
make use of that vertex weight, the application _has to_ now call one of the
vertex blend functions to supply the data (either glWeight or more likely
glWeightPointerARB). Mesa simply doesn't have any code to deal with those, there
are not even entries in the dispatch table.
Oh, and I'm not sure how this works on other hw. ARB_vertex_blend seems to be
implemented _only_ by ATI (at least announced only by ATI drivers), Nvidia
implements EXT_vertex_weighting, but unless I missed some other extensions it
can't be used since the VertexWeight functions accept only 1 value, and the
vertex programs show it's using 4 components. Intel has no support for either
extension. No idea what the heck WoW is doing there, I hope for them they don't
use different code solely based on renderer string...

          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to