On Tue, Jul 23, 2013 at 8:21 AM, Marek Olšák <mar...@gmail.com> wrote: > I think this is radically different from d3d1x, as it already can be > used to play games from Blizzard, Bethesda, and other companies > according to Christoph. I don't think this is much about what's best > for Wine, because Wine has to work on multiple operating > systems/drivers anyway. I think this is about what's best for the open > source graphics drivers, and skipping the OpenGL middle layer is > certainly not a bad idea. > > I think Wine should allow drivers, both open and closed, to implement > d3d9 by themselves. In any case, wined3d can be used as a fallback if > no compatible d3d9 driver has been found, which has already been > implemented by Christoph if I understood him correctly. > I see no problem with this. Let's merge the Wine patches, then the > d3d9 state tracker, then let the community test it and report bugs. > Once we're comfortable with it, we can enable building the d3d9 > gallium drivers by default and the user base should skyrocket. Isn't > it a good plan? >
Totally, if we can find some way for wine to pick up the dll so distros can package it even better. Like some sort of search path for /usr/lib64/dri/ or a look for winemesad3d.dll first then fallback to the wined3d.dll (or however this works). Dave. _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
