https://bugs.winehq.org/show_bug.cgi?id=51611
--- Comment #5 from reserv0@yahoo.com --- (In reply to Fabian Maurer from comment #4)
I see. Could you do a regression test? See https://wiki.winehq.org/Regression_Testing
I'm afraid not...
I mean, to get Wine (and especially Wine32, which is required to run this Poser 7 version I bought back in the old Windows XP days) to build on my distro (PCLinuxOS) is not something you can do straight out of the untouched git sources... This is "rpm" doing its magic in the build steps of its *.spec file.
It would require to rpmbuild a gazillion of different Wine versions in order to manage and bisect down to the culprit commit, and I have no free time to do this.
The RPM sources (and the patches and spec file I'm using to rebuild newer Wine versions) are available from this site: http://linux.developer.free.fr/ (because, sadly, PCLinuxOS' official Wine package is largely outdated, and its 32 bits libraries compatibility package does not allow to rebuild Wine 32 bits from scratch: at least, that site got working ia32libs[-devel] packages and allows to rebuild Wine).
This said, I would guess that simply looking at what commits touched the mouse cursor (and/or 3D rendering) code between Wine v6.9 (last working version) and Wine v6.10 (first broken version) would allow you to find the culprit/bogus changes...