Chip Davis
Chip Davis
That's a known issue with `wined3d`. There was a [patch](https://gitlab.winehq.org/wine/wine/-/merge_requests/784) submitted recently to Wine which should fix that issue.
> Perhaps I should leave this open for the original issue with DXVK? Yes, you probably should.
> If you’d gotten this fixed after 1.7 then maybe bumping DXVK would be enough. Thinking back on it... I think it might've just been the FFXIV branch of DXVK-CX....
> I'm running a test now to check if I see any odd failures on my side. No need--I already found some. I'm working on fixing them now.
> No need--I already found some. I'm working on fixing them now. All right, I'm pretty sure I've fixed all the failures that were caused by my PR.
...How did *that* happen?? Can you give me a log with all the failures?
What platform? What compile flags? The failures are primarily in the linear case, which means that something is going wrong averaging the pixels.
> What platform? What compile flags? Also, exactly what make and model of CPU are you running this on? I sure hope it's not an erratum...
> > What platform? What compile flags? > > Also, exactly what make and model of CPU are you running this on? I sure hope it's not an erratum... @alan-baker...
So there were a few broken shuffles and an add to a wrong vector that gave the broken results you saw. These should be fixed in #1642. Are there any...