https://bugs.winehq.org/show_bug.cgi?id=49812
Bug ID: 49812 Summary: FFXI: Major graphical errors when using d3d8to9 wrapper Product: Wine-staging Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: winehq@foreversmall.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 68142 --> https://bugs.winehq.org/attachment.cgi?id=68142 FFXI d3d8to9 graphical issue1
I am attempting to convert the d3d8 api to d3d9 using the d3d8to9 wrapper project(https://github.com/crosire/d3d8to9). The main motivations are to experiment with using DXVK to see if performance would be any better. There are many instances of the game that slow down for seemingly no reason. Most notably are when many UI elements are on the screen and areas with high foliage or many NPCs.
There are other projects like this one but this one is the only one I can get to launch the game without crashing in Wine. During my initial tests with DXVK, I was able to get a frame rate of 250-300fps in the title screen, additionally 130-180fps in game running around San'doria but with one major pitfall, that there are many graphical issues.
I have read that a common practice on Windows machines is to use this wrapper paired with "ReShade" to do the same thing I'm trying to achieve through wine and DXVK.
I'm unsure if the problem is with Wine or with d3d8to9 but I figured I'd start here. I'll attach a full d3d8 trace with only using d3d8to9 wrapper as well as 2 screenshots showing the issue.
https://bugs.winehq.org/show_bug.cgi?id=49812
--- Comment #1 from Algaris winehq@foreversmall.com --- Created attachment 68143 --> https://bugs.winehq.org/attachment.cgi?id=68143 FFXI d3d8to9 graphical issue2
2nd screenshot example
https://bugs.winehq.org/show_bug.cgi?id=49812
--- Comment #2 from Algaris winehq@foreversmall.com --- Created attachment 68144 --> https://bugs.winehq.org/attachment.cgi?id=68144 FFXI d3d8to9 d3d back trace
https://bugs.winehq.org/show_bug.cgi?id=49812
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #3 from joaopa jeremielapuree@yahoo.fr --- Please, attach the backtrace in this site, not a third-party site. If the file is too big, please compress it.
https://bugs.winehq.org/show_bug.cgi?id=49812
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #4 from Fabian Maurer dark.shadow4@web.de --- Does the same setup work on a windows machine? I mean, using d3d8to9 and DXVK. Unless that works, there is no Wine issue. Please test that, since you don't seem to use wine d3d libraries at all.
https://bugs.winehq.org/show_bug.cgi?id=49812
--- Comment #5 from Algaris winehq@foreversmall.com --- Thank you both for your time!
Fabian - For the d3d backtrace and the screenshots attached, I disabled DXVK in the config to use the wined3d d3d9 library to prove that the d3d8to9 wrapper successfully leveraged the builtin library before introducing DXVK. So in this case DXVK isn't in use and the graphical issues are present.
I unfortunately don't have access to a windows machine to test with currently. I may be able to get access to one to try this out though to prove that the d3d8to9 wrapper doesn't have these glitches when launching the game.
joaopa - apologies, the backtrace compressed is 30MB. I'll split it up into several files.
https://bugs.winehq.org/show_bug.cgi?id=49812
--- Comment #6 from Algaris winehq@foreversmall.com --- Created attachment 68149 --> https://bugs.winehq.org/attachment.cgi?id=68149 ffxi_d3d8to9_backtrace1
https://bugs.winehq.org/show_bug.cgi?id=49812
--- Comment #7 from Algaris winehq@foreversmall.com --- Created attachment 68150 --> https://bugs.winehq.org/attachment.cgi?id=68150 ffxi_d3d8to9_backtrace1
https://bugs.winehq.org/show_bug.cgi?id=49812
Algaris winehq@foreversmall.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #68150|ffxi_d3d8to9_backtrace1 |ffxi_d3d8to9_backtrace2 description| |
https://bugs.winehq.org/show_bug.cgi?id=49812
--- Comment #8 from Algaris winehq@foreversmall.com --- Created attachment 68151 --> https://bugs.winehq.org/attachment.cgi?id=68151 ffxi_d3d8to9_backtrace3
https://bugs.winehq.org/show_bug.cgi?id=49812
--- Comment #9 from Algaris winehq@foreversmall.com --- Created attachment 68152 --> https://bugs.winehq.org/attachment.cgi?id=68152 ffxi_d3d8to9_backtrace4
https://bugs.winehq.org/show_bug.cgi?id=49812
--- Comment #10 from Fabian Maurer dark.shadow4@web.de --- Tip: Next time compress logs with 7-zip, it gets the very small!
Can you please make an apitrace (https://github.com/apitrace/apitrace) using d3d8 (aka no wrapper) from the game? I don't own the game, and with that I could try to reproduce the issues.
Feel free to upload that somewhere else, since it will get BIG. Uncompressed easily multiple GB, so be warned.
https://bugs.winehq.org/show_bug.cgi?id=49812
--- Comment #11 from Gijs Vermeulen gijsvrm@gmail.com --- Could you also test without any wrapper at all? For all we know, the fault might lie in d3d8to9.
https://bugs.winehq.org/show_bug.cgi?id=49812
--- Comment #12 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-7.0-rc4?
-
WineHQ Bugzilla