[Bug 56014] New: Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56014

Bug ID: 56014
           Summary: Steam app displays a black screen on the Wayland
                    driver with the new wow64 mode but not x11
           Product: Wine
           Version: 0.9-pre
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

*with dxvk if I remember correctly steam doesn't work on the new wow64 mode
without it

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56014

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexandros.frantzis@collabo
                   |                            |ra.com

--- Comment #1 from [e-mail] ---
The Steam application (like many store apps) use CEF, which requires
cross-process rendering. We don't support that yet in the Wayland driver.

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56014

--- Comment #2 from m1m1k4tz  ---
(In reply to alexandros.frantzis from comment #1)
> The Steam application (like many store apps) use CEF, which requires
> cross-process rendering. We don't support that yet in the Wayland driver.

Thanks for letting me know. There used to be an option to launch steam without
the browser but it got depreciated so rip

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56014

Grigory Vasilyev  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Grigory Vasilyev  ---
Everything works. And there are no such problems, although I had to compile
lsteamclient, transfer patches from valve wine to load lsteamclient.dll,
rewrite proton python script, proton manifest. Without the lsteamclient, your
games will not be authorized by steam.

The problem you are talking about is caused by the default proton manifest in
the toolmanifest.vdf file witch start wine in the steam linux runtime virtual
container, container the complete isolated with your main system, and it loads
only its own vulkan files, and there is support limited to X11.

To disable running the container before starting wine, you need to change the
manifest to this form and remove all other json parameters.

```
"manifest"
{
  "version" "2"
  "commandline" "/proton %verb%"
}
```

You must also copy your dxvk files into the system and manual edit
dlloverrides, unset DISPLAY, add fsync and stagging patches, edit registry with
commands:

cd ${HOME}/.steam/root/compatibilitytools.d/GE-Proton9-1
export
STEAM_COMPAT_DATA_PATH=${HOME}/.local/share/Steam/steamapps/compatdata/1100990
export
STEAM_COMPAT_INSTALL_PATH=${HOME}/.local/share/Steam/steamapps/common/Aimbeast
export STEAM_COMPAT_LIBRARY_PATHS=${HOME}/.local/share/Steam/steamapps
export STEAM_COMPAT_CLIENT_INSTALL_PATH=${HOME}/.local/share/Steam

./proton runinprefix regedit

This example for Aimbeast game.

Thus, I recommend closing this bug report and it has nothing to do with CEF.
And it is related to the specifics of how steam and proton work.

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56014

--- Comment #4 from Grigory Vasilyev  ---
To run games, you do not need windows steam, games that require steam in proton
have a steam_helper.
https://github.com/ValveSoftware/Proton

Thus, to run games under your Wine, you need to compile 32 and 64 bit versions:
lsteamclient and steam_helper.

Apply these two patches to your wine sources.
https://github.com/ValveSoftware/wine/commit/5b5785001537dea33fb3aa93b0e0d0a...
https://github.com/ValveSoftware/wine/commit/53ba023e0a3638123c1ae64a070b45b...

You may also want to remove these lines since stemoverlay will probably not
work correctly.
         !RtlCompareUnicodeStrings(basename, basename_len,
L"gameoverlayrenderer", 19, TRUE) ||
         !RtlCompareUnicodeStrings(basename, basename_len,
L"gameoverlayrenderer64", 21, TRUE)) &&

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56014

--- Comment #5 from m1m1k4tz  ---
(In reply to Grigory Vasilyev from comment #3)
> Everything works. And there are no such problems, although I had to compile
> lsteamclient, transfer patches from valve wine to load lsteamclient.dll,
> rewrite proton python script, proton manifest. Without the lsteamclient,
> your games will not be authorized by steam.
>
> The problem you are talking about is caused by the default proton manifest
> in the toolmanifest.vdf file witch start wine in the steam linux runtime
> virtual container, container the complete isolated with your main system,
> and it loads only its own vulkan files, and there is support limited to X11.
>
> To disable running the container before starting wine, you need to change
> the manifest to this form and remove all other json parameters.
> "manifest"
> {
>   "version" "2"
>   "commandline" "/proton %verb%"
> }
>
> You must also copy your dxvk files into the system and manual edit
> dlloverrides, unset DISPLAY, add fsync and stagging patches, edit registry
> with commands:
>
> cd ${HOME}/.steam/root/compatibilitytools.d/GE-Proton9-1
> export
> STEAM_COMPAT_DATA_PATH=${HOME}/.local/share/Steam/steamapps/compatdata/
> 1100990
> export
> STEAM_COMPAT_INSTALL_PATH=${HOME}/.local/share/Steam/steamapps/common/
> Aimbeast
> export STEAM_COMPAT_LIBRARY_PATHS=${HOME}/.local/share/Steam/steamapps
> export STEAM_COMPAT_CLIENT_INSTALL_PATH=${HOME}/.local/share/Steam
>
> ./proton runinprefix regedit
>
> This example for Aimbeast game.
>
> Thus, I recommend closing this bug report and it has nothing to do with CEF.
> And it is related to the specifics of how steam and proton work.

Sorry, I'm not really following I compiled this on a fedora toolbox container
with this script then did the registry edit to test Wayland

sudo dnf install mingw64-gcc mingw32-gcc libX11-devel libXcursor-devel
libXfixes-devel libXi-devel libXrandr-devel libXrender-devel
wayland-devel.x86_64 rust-xkbcommon+wayland-devel.noarch freetype-devel.x86_64
alsa-lib-devel.x86_64 pulseaudio-libs-devel.x86_64 dbus-devel.x86_64
fontconfig-devel gnutls-devel mesa-libGL-devel libunwind-devel
gstreamer1-devel.x86_64 gstreamer1-plugins-base-devel.x86_64
gstreamer1-plugin-libav.x86_64 gstreamer1-plugins-bad-free-devel.x86_64
mesa-libOSMesa-devel.x86_64 vulkan-loader-devel.x86_64 SDL2-devel

sudo dnf group install 'C Development Tools and Libraries'
sudo dnf group install 'Development Tools'

#!/bin/bash
if [ ! -d ~/wine-dirs ]; then
  mkdir ~/wine-dirs
fi

if [ -d ~/wine-dirs/wine-source ]; then
  cd ~/wine-dirs/wine-source
  git pull
  git submodule update --init --recursive
fi
if [ ! -d ~/wine-dirs/wine-source ]; then
  git clone https://gitlab.winehq.org/wine/wine.git/ ~/wine-dirs/wine-source
  git submodule update --init --recursive
fi

rm -r ~/wine-dirs/wine-build
mkdir ~/wine-dirs/wine-build
cd ~/wine-dirs/wine-build
../wine-source/configure --with-mingw --with-wayland --with-vulkan
--enable-archs=i386,x86_64
make -j"$(nproc --ignore=2)"

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56014

--- Comment #6 from m1m1k4tz  ---
Also, wouldn't it have to be a Wayland driver thing if that's the only thing
that's changed and it works on x?

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56014

Zeb Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |winewayland
            Version|0.9-pre                     |unspecified

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=56014

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download
                URL|                            |https://cdn.cloudflare.stea
                   |                            |mstatic.com/client/installe
                   |                            |r/SteamSetup.exe

--- Comment #7 from Ken Sharp  ---
What version of Wine are you using?

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=56014

--- Comment #8 from m1m1k4tz  ---
The new wow64 mode with Wayland enabled the workaround is to use the flag
-cef-single-process

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=56014

--- Comment #9 from Ken Sharp  ---
> What version of Wine are you using?

$ wine --version

[Bug 56014] Steam app displays a black screen on the Wayland driver with the new wow64 mode but not x11

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=56014

--- Comment #10 from m1m1k4tz  ---
wine-10.8-247-ge0bb1dba3d6