Cross-regressions between wine and mesa: how to handle them?

[Stefan Dösinger]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 2014-01-26 14:08, schrieb Ruslan Kabatsayev:
> For end user this looks like failing software, and moreover, it's
> not easy to understand which software does have bug. Wine
> perspective: On the one hand, wine seems to use what Mesa exposes.
> On the other, why use shaders for games which don't need them?
There are some corner cases in the d3d fixed function pipeline which
we can't handle properly without shaders. Unfortunately, once we
detect such a corner case it's too late to turn on shaders.

A possible workaround for the user is to set UseGLSL=disabled. It's
not a good long-term fix though.

> Mesa perspective: On the one hand, it wants to advertise more
> support for latest OpenGL standards. On the other, why do it for
> very old HW which doesn't support it?
Does the "slow" mean that Wine hits a software rendering fallback and
Mesa emulates vertex shaders with the CPU? I hated it when OSX
advertised features the card didn't have, and I think it's a very bad
idea for Mesa to do the same thing.

The GL errors should be fixed though. Can you try to find the commits
in Wine and Mesa that started those errors?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJS5mTVAAoJEN0/YqbEcdMwViwP/3iPmbKEtH/5BBcNLg/IqxGJ
sie+Qn2Yibp+LBf2iYPqshjDKAHBNXiaiMKqTKG8GWzGC235K/Nqc0QoV2sFRRJW
EiroXisQlG6AupmWKqzqldSVYC93tehCQdp982Rk3XYENQmmsuE+OSwMwXAg32ji
8gKSrZ7EYwT2b4NYy79o7p/KiR5+nO/Mwm7m8wNYLoYPPjQ3yk95pxPxlNlsuAZw
eEeDRNU7lXtIGrYsO+xpA4saCW93vZp2rUqXLlQjAMdOi2HU3F5R7jmsLn/pqvJV
rIawm53PMP7bauUcB926StXYwW8yLeEHAbGtER4t2nJKf9tHNrNNKD0Q8CwrpE1F
fKwMJDHx5YVkeftADm2OiX4PNKflvwfeKTeib9ChCP7ApXbulbRi3Qx/n7Al+ZWv
6THEBaSS9PlxvPQQ1zwSduATfAMKsMulxDz6I0SPclVTnFTmMcfLxcNtFIHsjkCR
US7Q6hKGHfqLO/OQEdpiJ/4KlQmXrkQkWj0VOwnsBmWjBFv02Q/8Xoj4i50f7Qev
7KadSvgpgAg5Yu468jBbiVwxibxaxNQZNuJgFUnDfMyMdwBYXD613Ngnm1GriOUO
F+MWvaCKpMK4zsAYIZg366GTjH7XqANVZ1vaCruoAdmB6r39A3/mMiS5kmPoPLP5
/6tpS/N9eJfBOVyzv9Au
=q+e8
-----END PGP SIGNATURE-----