https://bugs.winehq.org/show_bug.cgi?id=55131
Bug ID: 55131 Summary: Celeste FNA x86 Windows Game does not work on WOW64 Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dofficialgman@gmail.com Distribution: ---
Created attachment 74684 --> https://bugs.winehq.org/attachment.cgi?id=74684 backtrace when trying to boot the game
Specifically testing the FNA build of Celeste available on Itch.io but it is available on other platforms as well https://mattmakesgames.itch.io/celeste
The game does not run on WOW64 (tested on Wine-8.10 and Wine-8.11) builds but runs fine on the standard Wine-8.10 multiarch (32bit and 64bit linux userspace).
A backtrace when trying to launch the game is attached.
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #1 from Rafał Mużyło galtgendo@o2.pl --- Attach full output, not just the backtrace.
...interesting find though.
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #2 from dofficialgman@gmail.com --- Created attachment 74690 --> https://bugs.winehq.org/attachment.cgi?id=74690 terminal log
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #3 from dofficialgman@gmail.com --- Created attachment 74691 --> https://bugs.winehq.org/attachment.cgi?id=74691 backtrace to match terminal log (incase it matters)
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #4 from Rafał Mużyło galtgendo@o2.pl --- ...
There is a non-insignificant chance this is the same problem as addressed by mr3053 - there are a few sort-of duplicate bugs about that.
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #5 from dofficialgman@gmail.com --- Created attachment 74826 --> https://bugs.winehq.org/attachment.cgi?id=74826 logs booting into game on wine-8.12 with wow64
Since Wine-8.12 has the patch you mentioned included I tried to run it again. It gets to the title screen but there are tons of graphical glitches and error logs in the termial output.
non-wow64 has none of these vkd3d errors and no graphical issues.
https://bugs.winehq.org/show_bug.cgi?id=55131
dofficialgman@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Celeste FNA x86 Windows |Celeste FNA x86 Windows |Game does not work on WOW64 |Game has graphical | |corruption on WOW64
https://bugs.winehq.org/show_bug.cgi?id=55131
dofficialgman@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|8.11 |8.14 Component|-unknown |d3d
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #6 from Rafał Mużyło galtgendo@o2.pl --- Sorry, but...recheck with 8.14. There had been another commit (opengl32: Preserve the remainder of the version string) that may affect those 'wined3d_guess_gl_vendor' lines, that didn't go in before.
Also, given that d3dcompiler spam, check with 'loaddll' channel which version d3dcompiler is being used and if using native helps.
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #7 from Rafał Mużyło galtgendo@o2.pl --- Also, 'Version' field of the bug isn't supposed to be changed after bug creation - its meaning is 'the earliest version of wine the bug had been observed with'. One of the few valid reasons to changed it would be if - for example - you've made a mistake in the initial filing and the actual version when the bug started was different than the one entered.
https://bugs.winehq.org/show_bug.cgi?id=55131
dofficialgman@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|8.14 |8.11
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #8 from dofficialgman@gmail.com --- (In reply to Rafał Mużyło from comment #6)
Sorry, but...recheck with 8.14. There had been another commit (opengl32: Preserve the remainder of the version string) that may affect those 'wined3d_guess_gl_vendor' lines, that didn't go in before.
vendor issue is fixed in 8.14
Also, given that d3dcompiler spam, check with 'loaddll' channel which version d3dcompiler is being used and if using native helps.
title screen is now a white screen on 8.14 (instead of vertex explosions seen before), log output is still similar.
We could already tell which dll was loaded from the before logs (dx11) and the output from loaddll confirms it
0024:trace:loaddll:build_module Loaded L"C:\windows\system32\opengl32.dll" at 7A800000: builtin 0024:trace:loaddll:build_module Loaded L"C:\windows\system32\wined3d.dll" at 04850000: builtin 0024:trace:loaddll:build_module Loaded L"C:\windows\system32\dxgi.dll" at 04730000: builtin 0024:trace:loaddll:build_module Loaded L"C:\windows\system32\d3d11.dll" at 044E0000: builtin
I don't understand what you mean but "if using native helps".
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #9 from dofficialgman@gmail.com --- Created attachment 75066 --> https://bugs.winehq.org/attachment.cgi?id=75066 wine-8.14 log
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #10 from Rafał Mużyło galtgendo@o2.pl --- I was referring to this line:
trace:loaddll:build_module Loaded L"C:\windows\system32\d3dcompiler_47.dll" at 63500000: builtin
So, get 32bit native of d3dcompiler_47.dll, drop it into the executable dir (sometimes WINEDLLOVERRIDES=d3dcompiler_47=n might be required, though usually works without) and see if that will make things work.
While vkd3d_shader works far better now than it did 6 months ago, there still are *many* pitfalls of it in the context of shaders in plain text form.
(also, a bit curious you still have patience for this and didn't test the Linux version - going by the site, it has one; doesn't mean I wouldn't like vkd3d_shader to reach the point of not giving up on random spec covered statements; actually, IIRC ternary operator is already done in vkd3d_shader git, waiting for its next merge date into wine tree)
https://bugs.winehq.org/show_bug.cgi?id=55131
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #11 from Zeb Figura z.figura12@gmail.com --- Are you encountering these bugs without new-style wow64?
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #12 from Zeb Figura z.figura12@gmail.com --- (In reply to Rafał Mużyło from comment #10)
So, get 32bit native of d3dcompiler_47.dll, drop it into the executable dir (sometimes WINEDLLOVERRIDES=d3dcompiler_47=n might be required, though usually works without) and see if that will make things work.
`winetricks -q d3dcompiler_47` is an easier way to achieve this.
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #13 from Rafał Mużyło galtgendo@o2.pl --- Personally, I despise blackboxing, so while I consider winetricks as useful as a repository of links of downloads (and - sometimes - dll sets), it's quite a bit less so as a tool to be promoted for casual use.
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #14 from Zeb Figura z.figura12@gmail.com --- (In reply to Rafał Mużyło from comment #13)
Personally, I despise blackboxing, so while I consider winetricks as useful as a repository of links of downloads (and - sometimes - dll sets), it's quite a bit less so as a tool to be promoted for casual use.
Huh? What do you mean?
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #15 from dofficialgman@gmail.com ---
Are you encountering these bugs without new-style wow64?
no, please refer to literal first report before asking https://bugs.winehq.org/show_bug.cgi?id=55131#c0
So, get 32bit native of d3dcompiler_47.dll, drop it into the executable dir (sometimes WINEDLLOVERRIDES=d3dcompiler_47=n might be required, though usually works without) and see if that will make things work.
that does not work still. exact same issue and I can see that it was indeed used
0024:trace:loaddll:build_module Loaded L"Z:\home\garrett\windows-applications\celeste-win-opengl\d3dcompiler_47.dll" at 63500000: builtin
(also, a bit curious you still have patience for this and didn't test the Linux version - going by the site, it has one; doesn't mean I wouldn't like vkd3d_shader to reach the point of not giving up on random spec covered statements; actually, IIRC ternary operator is already done in vkd3d_shader git, waiting for its next merge date into wine tree)
I am well aware of the native linux port, I own it and it works great. This is purely for testing purposes and it is just one of MANY games that I have seen this issue with, it just happens to be a game that has many releases so I can test easily.
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #16 from Zeb Figura z.figura12@gmail.com --- (In reply to dofficialgman from comment #15)
Are you encountering these bugs without new-style wow64?
no, please refer to literal first report before asking https://bugs.winehq.org/show_bug.cgi?id=55131#c0
I know, but you've mentioned multiple different bugs over the course of this report, and it's a bit surprising that new-style wow64 would cause these in that specific way. So I figured I'd confirm whether this really is specific to new-style wow64.
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #17 from Rafał Mużyło galtgendo@o2.pl --- Note the emphasis:
loaddll:build_module Loaded L"Z:\home\garrett\windows-applications\celeste-win-opengl\d3dcompiler_47.dll" at 63500000: *builtin*
Did you just copy one of the wine's libs there ? 'Native' means the native for Windows i.e. the one from DirectX package. Alternatively, quite a few games bundle it, for example AFAIK all node-webkit RPGMaker games do.
One way of recognizing it was done correctly will be that regardless if it helps, the vkd3d messages will be gone, as those come only from the wine version.
https://bugs.winehq.org/show_bug.cgi?id=55131
--- Comment #18 from Rafał Mużyło galtgendo@o2.pl --- ...PS: just make sure it's the 32bit variant of the lib.
-
WineHQ Bugzilla