On 15 September 2015 at 21:36, Austin English austinenglish@gmail.com wrote:
For https://bugs.winehq.org/show_bug.cgi?id=39277
Side note: I'm pretty sure I've seen this or a similar issue on my Intel/Nvidia desktop with Dragon Age 2, but didn't investigate it further at the time, so I'd really like to see this committed :).
This should probably go to winediag then.
On Wed, Sep 16, 2015 at 6:58 AM, Henri Verbeet hverbeet@gmail.com wrote:
On 15 September 2015 at 21:36, Austin English austinenglish@gmail.com wrote:
For https://bugs.winehq.org/show_bug.cgi?id=39277
Side note: I'm pretty sure I've seen this or a similar issue on my Intel/Nvidia desktop with Dragon Age 2, but didn't investigate it further at the time, so I'd really like to see this committed :).
This should probably go to winediag then.
I considered that, but all current uses of winediag are ERR that are within the user's control. I didn't want to make it an ERR, so a FIXME (which does eventually need to be fixed) felt more appropriate to me. I don't feel strongly at all about that though, so I'll resend.
Thanks for reviewing.
On 17 September 2015 at 04:21, Austin English austinenglish@gmail.com wrote:
I considered that, but all current uses of winediag are ERR that are within the user's control. I didn't want to make it an ERR, so a FIXME (which does eventually need to be fixed) felt more appropriate to me. I don't feel strongly at all about that though, so I'll resend.
I don't think we care that much about ERR vs. FIXME for winediag. Note that this isn't necessarily something we or anyone else can fix. The wined3d core context work will make d3d10+ work on Mesa and MacOS for some classes of cards, but there's also plenty of hardware that's simply incapable of shader model 4. In that regard this isn't all that different from the situation with hardware/drivers that can't do shader model 3.
-
Austin English -
Henri Verbeet