https://bugs.winehq.org/show_bug.cgi?id=43635
Bug ID: 43635 Summary: Crysis 3: Poor, dark, and/or missing textures Product: Wine-staging Version: 2.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: jojos_band@gmx.net CC: erich.e.hoover@wine-staging.com, michael@fds-team.de, sebastian@fds-team.de Distribution: ---
Created attachment 59053 --> https://bugs.winehq.org/attachment.cgi?id=59053 Crysis 3 tutorial screenshot with poor textures
Crysis 3 v1.0.1.3
During gameplay, all textures have an ultra low resolution and dark (if there are textures at all). The entire scene thus looks very dark.
It appears that this is caused by missing implementation of multiple ID3D11DeviceContext methods for deferred contexts.
Attachments: - Crysis 3 tutorial screenshot with poor textures - Patch for wine 2.15-staging (implements missing methods for deferred contexts). - Crysis 3 tutorial screenshot with good textures (with the patch)
https://bugs.winehq.org/show_bug.cgi?id=43635
--- Comment #1 from Johannes jojos_band@gmx.net --- Created attachment 59054 --> https://bugs.winehq.org/attachment.cgi?id=59054 Crysis 3 tutorial screenshot with good textures
https://bugs.winehq.org/show_bug.cgi?id=43635
--- Comment #2 from Johannes jojos_band@gmx.net --- Created attachment 59055 --> https://bugs.winehq.org/attachment.cgi?id=59055 Patch for wine 2.15-staging
Old fashioned diff patch. Apply by calling "patch -p1 < PATCHFILE" in the wine staging 2.15 source folder after staging patches have been applied.
https://bugs.winehq.org/show_bug.cgi?id=43635
--- Comment #3 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Johannes from comment #2)
Created attachment 59055 [details] Patch for wine 2.15-staging
Old fashioned diff patch. Apply by calling "patch -p1 < PATCHFILE" in the wine staging 2.15 source folder after staging patches have been applied.
Does this patch fix all the issues? Please note that patches can be submitted at https://dev.wine-staging.com/ for review / inclusion to Wine Staging. A plain diff is not sufficient though because it lacks author information (Wine requires the use of your real name for all contribution). The easiest way to do that is commit your changes with (git commit -a -m "d3d11: ..."), and then use "git format-patch --keep-subject".
https://bugs.winehq.org/show_bug.cgi?id=43635
--- Comment #4 from Johannes jojos_band@gmx.net --- (In reply to Sebastian Lackner from comment #3)
(In reply to Johannes from comment #2)
Created attachment 59055 [details] Patch for wine 2.15-staging
Old fashioned diff patch. Apply by calling "patch -p1 < PATCHFILE" in the wine staging 2.15 source folder after staging patches have been applied.
Does this patch fix all the issues? Please note that patches can be submitted at https://dev.wine-staging.com/ for review / inclusion to Wine Staging. A plain diff is not sufficient though because it lacks author information (Wine requires the use of your real name for all contribution). The easiest way to do that is commit your changes with (git commit -a -m "d3d11: ..."), and then use "git format-patch --keep-subject".
It fixes the issues mentioned in this bug, i.e. Crysis 3 is now "usable" - right now I'm testing for stability ;) I've no experience with git, but I'll try your suggested steps on submitting it in an appropriate manner to wine staging. I will contact you by e-mail in case I fail (don't want to spam the wine Bugzilla with git instructions).
https://bugs.winehq.org/show_bug.cgi?id=43635
--- Comment #5 from Johannes jojos_band@gmx.net --- (In reply to Sebastian Lackner from comment #3)
(In reply to Johannes from comment #2)
Created attachment 59055 [details] Patch for wine 2.15-staging
Old fashioned diff patch. Apply by calling "patch -p1 < PATCHFILE" in the wine staging 2.15 source folder after staging patches have been applied.
Does this patch fix all the issues? Please note that patches can be submitted at https://dev.wine-staging.com/ for review / inclusion to Wine Staging. A plain diff is not sufficient though because it lacks author information (Wine requires the use of your real name for all contribution). The easiest way to do that is commit your changes with (git commit -a -m "d3d11: ..."), and then use "git format-patch --keep-subject".
See https://dev.wine-staging.com/patches/181/
https://bugs.winehq.org/show_bug.cgi?id=43635
K1773R K1773R@darkgamex.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |K1773R@darkgamex.ch
https://bugs.winehq.org/show_bug.cgi?id=43635
Michael Müller michael@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Michael Müller michael@fds-team.de --- The patch has been added to Wine Staging. Closing bug as FIXED. One meta bug for deferred context support in wine development should be sufficient.
https://bugs.winehq.org/show_bug.cgi?id=43635
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Closing Fixed Staging 3.14
-
wine-bugs＠winehq.org