Bayonetta (460790)

[mrdeathjr28]

Seems wine error still remains, this game cant load second time because lack of this feature

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

Also affects vanquish

[kisak-valve]

[GREYLIST] Bayonetta (460790)

Issue transferred from #693.
@mimattr posted on 2018-08-26T18:40:47:

Ubuntu 16.04, NVIDIA GTX 970, Proton 3.7-4 Beta:

Steam System Information

Test	Result
Singleplayer	Working^
Local Co-op	N/A
Online Multiplayer	N/A

Configuration	...
Input	Steam Controller
Display	1920x1080
Fullscreen	Yes
Preset	Medium
VSync	On^^
API	DX9

^ CRIWARE “Filmstrip” cutscenes display incorrectly
^^ Disabling “VSync” causes application freeze (#262)

---

@Zero86Sk commented on 2018-08-26T19:21:49

i would say this is not whitelist worthy yet

---

@mimattr commented on 2018-08-26T19:39:35

@Zero86Sk Please note this is a GREYLIST item (i.e. near feature complete), the WHITELIST should be reserved for fully functional products.

[MuchiMuchiPink]

Wonder if this is fixed yet? In Vanquish it is possible now to change resolution etc, while Bayonetta still crashed.

[Francesco149]

I'm still observing the issue as of now with proton 3.16-3 beta on a r9 270x with mesa-git and kernel 4.18.14-zen

[popsUlfr]

Yes, with 3.16-3 beta changing the graphics options either crash the game or it says it can not save the changes.
Also the start screen and main menu look like this for me :

It's maybe because of the Nvidia beta drivers 396.54.09. Sometimes when starting the game the Bayonetta logo appears correctly it's like 1/10 times though.

[NTMan]

Bayonetta crashed immediately after start on AMD Vega 56.

steam-460790.log

$ inxi -bM
System:    Host: localhost.localdomain Kernel: 4.19.0-1.fc30.x86_64 x86_64 bits: 64 Desktop: Gnome 3.30.1 
           Distro: Fedora release 30 (Rawhide) 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-I GAMING v: Rev 1.xx serial: <root required> 
           UEFI: American Megatrends v: 0901 date: 07/23/2018 
CPU:       8-Core: AMD Ryzen 7 2700X type: MT MCP speed: 1996 MHz min/max: 2200/4000 MHz 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] driver: amdgpu v: kernel 
           Display: wayland server: Fedora Project X.org 1.20.2 driver: amdgpu resolution: 3840x2160~60Hz 
           OpenGL: renderer: Radeon RX Vega (VEGA10 DRM 3.27.0 4.19.0-1.fc30.x86_64 LLVM 7.0.0) v: 4.5 Mesa 18.2.2 
Network:   Device-1: Intel I211 Gigabit Network driver: igb 
           Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter driver: r8822be 
Drives:    Local Storage: total: 11.35 TiB used: 5.64 TiB (49.7%) 
Info:      Processes: 459 Uptime: 44m Memory: 31.34 GiB used: 19.23 GiB (61.4%) Shell: bash inxi: 3.0.27 

[ghost]

https://github.com/wine-mirror/wine/commits/master/dlls/ntdll/file.c
https://www.phoronix.com/scan.php?page=news_item&px=Wine-3.19-Released

There's been a lot of changes to the relevant file in Wine causing this bug, not sure if it effects this.

It'd be great if someone could test this game again on Wine 3.19 or git.

[popsUlfr]

I tested with wine 3.19 and git (EDIT2 : just realized that the latest git commit was to tag 3.19, so that was useless haha) and still the same problem with the saving of the options

But since 3.19 no graphic issues on my end with the main menu

At least I think, I don't know what it looks like on windows.

EDIT3: I was wrong. It's still random with the graphics glitches.

EDIT:
Here's a wine trace but I don't think it's very useful (remove the last .log at the end)
steam-460790.log.xz.log

EDIT4:
I applied the patch from the wine bug report https://bugs.winehq.org/show_bug.cgi?id=42982
found here https://bugs.winehq.org/attachment.cgi?id=58637&action=edit

But the error still persists.

[Francesco149]

another quite annoying bug is that pause often softlocks at the loading... text

EDIT: spamming kick/punch for a couple seconds unlocks the game, still annoying though

[popsUlfr]

I compiled my own proton with the patch applied and I can change the settings. Anything higher that 1280x720 crashes the game though. Also the game completely bypasses an emulated desktop????
It crashes randomly while loading :( Because of the autosaving I presume...

EDIT:
Here's the patched 32bit ntdll.dll.so if someone wants to do some testing.
It would need to be dropped where the existing 32bit ntdll.dll.so is located. So for Proton 3.16 that would be ~/.local/share/Steam/steamapps/common/Proton 3.16/dist/lib/wine/ntdll.dll.so always backup the original file.
It would be nice if there were a way to LD_PRELOAD the library but I haven't figured out how to work this out.

Applied patch ntdll-file-async.v3.patch : ntdll.dll.so.gz

EDIT2:

Wait, so if you work your way up in the resolutions starting with 1280x720 and applying each higher resolution you can get up without crashing! :D

(The screenshot is 2560x1440, my monitor is 1440p, the game seems to upscale 1080p regardless and renders at native resolution if that makes sense...)

Can the system_data file be shared ? Why encrypt this it's beyond me. This file has all graphics at max, vsync off, resolution at 1920x1080. Goes into ~/.local/share/Steam/steamapps/compatdata/460790/pfx/drive_c/users/steamuser/My Documents/Bayonetta/system_data
1920x1080, All Max, Vsync off : system_data.gz
2560x1440, All Max, Vsync off : system_data.gz

The game WILL get stuck on start if the patched ntdll.dll.so isn't used by the way.

My launch options are : PROTON_NO_D3D11=1 %command%

1440p :

[popsUlfr]

Made a LD_PRELOAD hack for easy loading without having to alter the proton dist for all the games.
Here's the source code for ntdll_override.c :
https://gist.github.com/popsUlfr/363a6a0bf981cc2ae4308bf2cf0758fb
To compile yourself : gcc -m32 -O2 -Wall -shared -fPIC -ldl -o ntdll_override.so ntdll_override.c

Extract the following next to Bayonetta.exe
bayonetta_ntdll_override.tar.gz
(If the first one does not work then here's a ntdll_override.so that is compiled with gcc from the steam runtime : bayonetta_ntdll_override_steamgcc.tar.gz)
bayonetta_ntdll_override_3.16-6.tar.gz

So it looks like this :

Bayonetta.exe
ntdll.dll.so
ntdll_override.so

In the launch options for the game set :

LD_PRELOAD="${LD_PRELOAD}:./ntdll_override.so" PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_NO_D3D11=1 %command%

(also add PROTON_FORCE_LARGE_ADDRESS_AWARE=1)

[Francesco149]

@popsUlfr I tested your LD_PRELOAD hack (first version) and it works great as long as I have PROTON_NO_D3D11=1

the settings are correctly saved and loaded on subsequent starts

running high settings will result in more glitchy/missing textures though, while medium is fine througout the game except for a few menus and one boss where the water is transparent

I'm running mesa-git and amdgpu on a r9 270x

[popsUlfr]

@oblitum Yeah Vanquish works out of the box for me, changing settings and all on nvidia.
Bayonetta has still some peculiar file saving problems compared to Vanquish it seems.
You can compile the patched ntdll.dll.so yourself of course. Just need to pull this repo, patch the wine folder with the diff from the wine bug report and follow the instructions for building yourself.
As a convenience I offered those already built and ready for testing.

@Francesco149 Ah great to hear! Yeah I mentioned the option PROTON_NO_D3D11=1 to be set in the launch options. I created the second tarball because I remembered that a more recent glibc version might create versioning issues on older libc systems, the steam runtime version should therefore work on any distro where steam can be installed I think.

[Xeers]

proton 4.2-1
CPU Brand: AMD FX (tm) -8320 Eight-Core Processor
Memory:
    RAM: 16021 MB
"Antergos Linux" (64 bits)
Kernel version: 5.0.5-arch1-1-ARCH
Graphics card:
    Driver: NVIDIA Corporation GeForce GTX 950 / PCIe / SSE2
    Driver version: 4.6.0 NVIDIA 418.56

Empty window pops up briefly (less than one second) and then disappears

[kisak-valve]

Hello @Xeers, please opt into Steam's beta client and/or go to Steam -> Library dropdown -> Tools and verify Proton 4.2 is installed on the list.

[Xeers]

I have Steam (beta) with Proton 4.2

[vjr2]

I've reinstalled the game and nothing. I hace the same issue as @Xeers. I hace Steam beta with proton 4.2 and same. Empty Window Pops up and then it closets less than a second.

[ghost]

@vjr2 @Xeers

I've reinstalled the game and nothing. I hace the same issue as @Xeers. I hace Steam beta with proton 4.2 and same. Empty Window Pops up and then it closets less than a second.

Reinstalling the game won't work.

Delete the prefix at steamapps/compatdata/460790

[vjr2]

@vjr2 @Xeers

I've reinstalled the game and nothing. I hace the same issue as @Xeers. I hace Steam beta with proton 4.2 and same. Empty Window Pops up and then it closets less than a second.

Reinstalling the game won't work.

Delete the prefix at steamapps/compatdata/460790

Wont work for me. My theory is when I first attempted to launch it and change settings as I haven't read the documentation about this game at that time, the steam cloud saved my settings and now I can't change them, even tho there is no configuration file. But that's what I just belive. I'm hopping for proton use wine 4.4 to fix this

[kisak-valve]

If someone knows what upstream commit fixes the issue, feel free to open a pull request with it for a Proton dev to evaluate.

[ghost]

wine-mirror/wine@56f34c7

wine-mirror/wine@730b47e

These are the two commits in upstream that fix the issue. They're in Wine 4.4, which probably shouldn't be that long before Proton updates I'm sure.

@vjr2

the steam cloud saved my settings

You seem to be right.

I changed settings to test this, and I was unable to boot it even with deleting the prefix. I know you used to be able to just delete the prefix.

Disabling Steam Cloud synchronization and then deleting or moving the prefix and starting the game will work.

Re enabling Steam Cloud still allowed it to boot and my save was still there.

[vjr2]

I think I will just wait. I just realized that wine 4.5 comes with media foundation files. Witch means, 75% of the games will be compatible. Let's hope Proton hits wine 4.5 before July :P

[wgpierce]

With Steam finally bumping Proton to Wine 4.11, the fix added in Wine 4.4 for the save settings bug (https://bugs.winehq.org/show_bug.cgi?id=42982) in this game was finally picked up.

I've confirmed the game can be loaded a second time with custom settings and saves with Proton 4.11 with no problems. The workaround from popsUlfr in this issue is no longer needed.

I think this game can be considered for the Whitelist now, barring the visual glitches mentioned earlier in this issue.

[MuchiMuchiPink]

I can confirm this as well. Game runs perfect now.

[mimattr]

Compatibility Report

System Information

• GPU: RTX 2060
• Driver/LLVM version: NVIDIA 430.40
• Kernel version: 5.0.0-23-generic
• Link to full system information report as Gist
• Proton version: 4.11-2

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

1. Character voices occasionally appear out-of-sync during cutscenes.
2. Enabling PROTON_USE_D9VK resolves the "Voice Sync" issue but discards filmstrip/hole-punch effect during cutscenes. (CRIWARE)

Reproduction

1. Select the title within your Library using the Steam client and press the Play button

[arBalasquide]

Bayonetta crashing on all proton versions.

GPU: AMD Radeon RX 5600 XT
Kernel: 5.5.13-1-MANJARO
Using Mesa 19.3.5 and LLVM 9.0.1
Proton Versions tested: 5.0-5 4.11-13  4.2-9 3.16-9
Tested using steam-native and steam-manjaro

Log is here steam-460790.log

Basically goes to a black windowed screen then immediately crashed. I went through the logs but didn't find anything particular that could be causing the issue.
I also went through errors in this issue and tried the solutions but none have worked.

I only have one drive so I have not tested the solutions for having the game in a secondary drive. But I do have my drive partitioned for dual boot, so perhaps that could be an issue. The library is located in .local/share/Steam/

No saved_data file is generated and I have tried reinstalling the game, deleting the compatdata folder, etc.

[wgpierce]

There has been one visual glitch found with this game that affects both dxvk and wined3d:
doitsujin/dxvk#1619
https://bugs.winehq.org/show_bug.cgi?id=49133

@arBalasquide Bayonetta seems to work fine for others; there may be a problem with your setup.

[ekianjo]

I have installed Bayonetta on a single drive-system, Nvidia 440.x drivers, 8Gb Ram, Ubuntu 20.04, and on this particular system Bayonetta does not launch. I tried several versions of Proton (5.07, and 4.x ones available) and none of them make the game launch. I also tried with D9VK but no success. Any idea?

[ghost]

@ekianjo

Because you launched it with old versions of Wine, it may have created the corrupt save/config file that used to happen in old versions of Wine, where it wouldn't boot if it exists.

Try deleting/moving the prefix (steamapps/compatdata/460790), and possibly check your home folder for it saved under "My Documents".

[Valmar33]

@ekianjo

One fix that I found that tend to work is this:

In winecfg, in the Drives tab, add a new letter, D:, and point that to the Bayonetta game directory.

Someone on protondb found this obscure fix for it.

If that fails... well, then there are other problems.

[Saroufim]

That solves it for me. Thank you very much

[ghost]

I was able to get this to work using default Proton (5.0-9 as of this post) on Debian 10 with nVidia GTX 960 using buster-backports driver 440.100. I received the "black screen" issue reported here and used the D: drive letter fix (probably because it reads that as a soft link in the absence of a disk or ROM). Important to note, if the system has a ROM like mine does, the following needs to be done after the first run of the game and the prefix is created to correct the wrong D: drive path:

rm -f ~/.steam/debian-installation/steamapps/compatdata/460790/pfx/dosdevices/d::

If you don't have/want wine installed you can add the D: drive like this:

cd ~/.steam/debian-installation/steamapps/compatdata/460790/pfx/dosdevices
ln -s ~/.steam/debian-installation/steamapps/common/Bayonetta d:

Save games and settings did not work so the following was required:

mkdir -p ~/.steam/debian-installation/steamapps/compatdata/460790/pfx/drive_c/users/steamuser/'My Documents'/Bayonetta

Steam Cloud games were then visible after the game was started. Saving games and settings also worked as expected. It should certainly be possible to write a script or make these changes during the first component install steps of the game after install.

Graphics Quality was set to "High" and was tested on 5.0 and 4.11. 5.0 had better performance. No launch options were needed. There was minor tearing even with VSync enabled during the first Rodin cutscene in the bar. The overall performance is as good if not better than in Windows 10.

[ranplayer]

This game is facing a performance regression with Proton 5.13. Tweaking around, I've found out the reason: DXVK. Using Proton 5.10 (DXVK 1.7.0), the games runs pretty well on my end at 60 fps on maximum settings. Replacing Proton 5.13 DXVK dlls by those from 5.10 fixes the issue. Other D3D9 games might be facing the same issue.

My specs:
GPU: GTX 970 4GB
GPU Driver: Nvidia 460.32
CPU: Intel Core i5 4690s
Kernel: 5.4/5.10
O.S: ArchLinux

[kisak-valve]

Hello @ranplayer, that sounds like something which should be mentioned over in the dxvk issue tracker if it hasn't been already.

[ranplayer]

@kisak-valve , I've compiled DXVK manually with the latest changes from master (doitsujin/dxvk@0eec958) and added to Proton 5.13. The performance regression is fixed. If somebody wants to try, I'm going to attach my build here. Checksum (SHA256): be71c77dc35b7ea07447c63331a2c9c95d0e8c3834af3b5262b9f18762a279f1.

[Sewer56]

Required PROTON_SET_GAME_DRIVE=1 for me to successfully boot; this doesn't seem to be mentioned anywhere here.

[kisak-valve]

Bayonetta can't run on OpenMandriva Linux 23.10 Rome

Issue transferred from #7309.
@satoayanami posted on 2023-12-03T11:32:51:

Compatibility Report

• Name of the game with compatibility issues: Bayonetta
• Steam AppID of the game: 460790

System Information

• GPU:
• Video driver version:
• Kernel version:
• Link to full system information report as Gist: https://gist.github.com/satoayanami/3ed8482059e2017302ebc0e69abe1c34
• Proton version: 8.0.4 & Proton Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• [*] that I have checked whether there are updates for my system available.

steam-460790.log

Symptoms

I'm using Steam APP on OpenMandriva23.10 Linux AMD64, i've ran successfully the following games using Proton from 6 and up to 8.0-4c & experimental:

-Castlevania Lords Of Shadows APPID 234080
-Castlevania Lords Of Shadows 2 APPID 239250
-Pacman CEDX+ APPID 236450
-Saint Seiya Soldiers Soul APPID 348710
-DOOM 64 APPID 1148590

Also, Steam installed by itself the runtimes "Sniper" and "Soldier.

When i try to run Bayonetta using Proton, on any version from 6 and up to experimental, the first time, the game compiled the vulkan shaders; then the game try to start, a window opens and closes quickly, and the game closes (can´t load)

Reproduction

Install OpenMandriva23.03 AMD64 on an AMD system without SMT (HT+)
Update the Operating System up to the 23.10 or newer version, make sure the system can run OpenGL and Vulkan games.
Download the Steam Linux APP from flathub at:
https://flathub.org/apps/com.valvesoftware.Steam
then install the Steam APP using the flatpak file.
I also tested Serious Sam 3 BFE with it's linux version and runs fine, so, you can use this as an OpenGL test.
Run Castlevania Lords of Shadows Ultimate Edition and Castlevania Lords of Shadows 2 in order to make sure that proton runs fine.
Run DOOM 64 using Vulkan API in order to make sure Vulkan runs fine.

Try to launch "Bayonetta" with proton versions from 6, and up to 8.0-4c and experimental.

[kisak-valve]

Hello @satoayanami, it would be worthwhile to test how the game behaves with the game's launch options set to PROTON_SET_GAME_DRIVE=1 %command%.

[Steamvoker]

Hello @satoayanami, it would be worthwhile to test how the game behaves with the game's launch options set to PROTON_SET_GAME_DRIVE=1 %command%.

I've had the same issue that the game would immediately close on startup (tried every available version of proton from Experimental to 5.0-10). Setting PROTON_SET_GAME_DRIVE=1 %command% does seem to fix the issue. The game launches, but I still have to see if it is playable to the end.

System info just in case:
Distro: EndeavourOS
Kernel version: 6.6.8-arch1-1
GPU: RTX 4090
Driver/LLVM version: nvidia 545.29.06-1
CPU: AMD Ryzen 9 7950X
RAM: 2x32GB DDR5 6000MHz

Edit: I should add that I'm not using the flatpak.

[satoayanami]

Hi, thanks for the advice, i've tried the command you posted, but i'm still having the same issue, a black window that closes as soon as it opens, and the game cannot start. I've sent the log geberated with proton, and the lines in red seems to be a clue if what happens. Again, thanks.