http://bugs.winehq.org/show_bug.cgi?id=35624
Bug ID: 35624 Summary: 3Dmark 2001 SE: Brkoken "Fill Rate (Multi-Texturing)" test Product: Wine Version: 1.7.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: wylda@volny.cz Classification: Unclassified
All the test are displayed correctly except "Fill Rate (Multi-Texturing)". Fast way to reproduce click "Change" (under Selected Tests) -> (tab) "Custom" -> Clear -> choose "Fill Rate (Multi-Texturing)" -> click "Benchmark".
Currently the wine lower than 1.7.8 can't be configured&compiled on Debian Jessie due to newer libraries. After backporting pathces for freetype, x11, lcsm2 i was able to make wine happy with configure/make down to 1.7.0/1.6.0. Anyway i endup with non-vannila wine.
If anyone is able to make the regression test, go ahead. It will take me some time to prepare another machine with Debian Wheezy for regression testing below wine-1.7.8.
http://bugs.winehq.org/show_bug.cgi?id=35624
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression URL| |http://www.futuremark.com/b | |enchmarks/legacy
https://bugs.winehq.org/show_bug.cgi?id=35624
--- Comment #1 from Henri Verbeet hverbeet@gmail.com --- For what it's worth, it seems to render correctly here. In what way is it broken?
http://bugs.winehq.org/show_bug.cgi?id=35624
--- Comment #2 from Wylda wylda@volny.cz ---
Hi Henri, as that bad-case screenshot is a noisy, thus bigger, i could not attach them here. For sure, i did not reduce the resolution nor used JPEG lossy-compression. Screen shots taken from wine-1.7.12 & nvidia v319.82.
here is a Single-Texturing Fill Rate test (GOOD): https://www.dropbox.com/s/dv3mmqfnyebzekv/ok_fill_rate_single_texturing.png
Multi-Texturing Fill Rate test (BAD): https://www.dropbox.com/s/mth0q76t3jvb8z1/bad_fill_rate_multi_texturing.png
https://bugs.winehq.org/show_bug.cgi?id=35624
--- Comment #3 from Henri Verbeet hverbeet@gmail.com --- It looks like the good screenshot for me (r600g, AMD CEDAR), so I guess there could be a driver specific component to this. Unfortunately that also means I can't help much with the bisect.
https://bugs.winehq.org/show_bug.cgi?id=35624
--- Comment #4 from Wylda wylda@volny.cz ---
Sorry, i don't know if i undrestand that correctly. On your PC, you see the Multi-Texturing the same as me and you consider it as a correct screenshot?
For sure i made a WinXP MultiTexture screenshot:
https://www.dropbox.com/s/fcijsm30s0unj2a/ok_fill_rate_multi_texturing_winxp...
Now i tried latest git wine-1.7.12-213-gb0b6728 and 32bit only wine version (not wow64), but the same result... I already prepared parition for older Debian and i'm going to install it on the same HW for regression testing. Based on AppDB it was OK on Dec 18 2010 & wine-1.3.9.
https://bugs.winehq.org/show_bug.cgi?id=35624
--- Comment #5 from Henri Verbeet hverbeet@gmail.com --- (In reply to Wylda from comment #4)
Sorry, i don't know if i undrestand that correctly. On your PC, you see the Multi-Texturing the same as me and you consider it as a correct screenshot?
No, it looks like the XP screenshot for me. Your "BAD" screenshot does look clearly broken.
https://bugs.winehq.org/show_bug.cgi?id=35624
--- Comment #6 from Wylda wylda@volny.cz ---
It is caused by wine-1.6-rc1-64-gffc9f53:
ffc9f535eb7817ea4cd0d0657471e61a9813debd is the first bad commit commit ffc9f535eb7817ea4cd0d0657471e61a9813debd Author: Henri Verbeet hverbeet@codeweavers.com Date: Fri Jun 14 09:07:12 2013 +0200
wined3d: Handle pre-transformed vertices in the GLSL vertex pipe.
This also avoids a fallback to drawStridedSlow().
Verified by revert. Is any trace/debug channel needed?
https://bugs.winehq.org/show_bug.cgi?id=35624
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.7.12 |1.6-rc2 Regression SHA1| |ffc9f535eb7817ea4cd0d065747 | |1e61a9813debd
http://bugs.winehq.org/show_bug.cgi?id=35624
--- Comment #7 from Wylda wylda@volny.cz --- In advance... https://www.dropbox.com/s/q5ebbm7fierwvr8/3dmark_logs.tar.bz2
https://bugs.winehq.org/show_bug.cgi?id=35624
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-d3d
http://bugs.winehq.org/show_bug.cgi?id=35624
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hverbeet@gmail.com Summary|3Dmark 2001 SE: Brkoken |3Dmark 2001 SE: Broken |"Fill Rate |"Fill Rate |(Multi-Texturing)" test |(Multi-Texturing)" test
https://bugs.winehq.org/show_bug.cgi?id=35624
--- Comment #8 from Henri Verbeet hverbeet@gmail.com --- Created attachment 47635 --> https://bugs.winehq.org/attachment.cgi?id=47635 patch
I think the attached patch should help.
It looks like this is NVIDIA specific, and essentially the same issue as bug 32485. When GL_MAP_INVALIDATE_BUFFER_BIT is set, the r600g driver only creates a new buffer if the current one is busy, while it seems the NVIDIA driver always does that. There's probably something to be said for both approaches. This didn't show up before commit ffc9f535eb7817ea4cd0d0657471e61a9813debd because we ended up in drawStridedSlow(), and the buffers would stay on the CPU.
https://bugs.winehq.org/show_bug.cgi?id=35624
--- Comment #9 from Wylda wylda@volny.cz --- (In reply to Henri Verbeet from comment #8)
I think the attached patch should help.
Sure thing, the patch fixes the problem :) Many thanks Henri.
https://bugs.winehq.org/show_bug.cgi?id=35624
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
https://bugs.winehq.org/show_bug.cgi?id=35624
Henri Verbeet hverbeet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |c1032e977bb9f850e3aea28dd79 | |e3d7c2244cd6c Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #10 from Henri Verbeet hverbeet@gmail.com --- Should be fixed by commit c1032e977bb9f850e3aea28dd79e3d7c2244cd6c.
https://bugs.winehq.org/show_bug.cgi?id=35624
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.14.
-
wine-bugs＠winehq.org