Application Details:

Version: Steam
License: Retail
Votes: 1
Latest Rating: Platinum
Latest Wine Version Tested: 4.4

Maintainers: About Maintainership

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Creating new saves.

Loading saves and game assets.

Sound, Graphics, HUD


  • Quick Time Events
  • Torture Attacks
  • Witch Time
  • Completing Missions
  • Game Events
  • Angel Attack Mini-game

What does not

Changing Graphics Settings may cause temporary unresponsiveness, no rendering (blank white screen), abrupt exit or crash. If unresponsive, the game will resume responding after a tab-out and tab-in, but it will "default" to a different resolution and quality preset.

Steam Overlay may not fully dismiss if activated.

Windowed Mode- the game will force itself full screen.


What was not tested

This tests a playthrough of Chapter 3 The Burning Ground (level contains QTEs, cutscenes, and custom Level behaviors and triggers such as lava, fire spirits, hourglass, trash can triggered secret level) on a continued save, played with a keyboard.

A new save has been created and played through the Prologue and the first mission.

Boss Fights, Motorbike section, on-rail shooter section have not been tested.


Hardware tested


  • GPU: AMD
  • Driver: open source

Additional Comments

This was done on a fresh, no-customization , no tweaks prefix of Wine.

Drastically worse than native performance.

On Windows with the same hardware, the game is capable of running at 2560xs1440 at 60 fps.
On Wine, the game is capable of running the same resolution and settings at 8-25 fps.

Lowering graphics settings causes improved performance in the main menu only. Frame issues remain while playing.

Either Bronze or Garbage, as the game logic and events behave correctly, but the frame rate can not offer an acceptable playing experience.

CPU: AMD FX-6350

Video Card: AMD RX Vega 56


selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowUbuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)Mar 15 20194.4Yes Yes NoPlatinumCarlos Rodriguez 
CurrentUbuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)Aug 15 20183.12-stagingN/A Yes NoBronzeAnonymous 
ShowArch Linux x86_64Jun 04 20183.9-stagingYes Yes NoPlatinumGianfrancesco Scardua 
ShowDebian GNU/Linux 9.x "Stretch" x86_64Dec 18 20173.0-rc2Yes Yes NoGarbageBlendJul 
ShowUbuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)Nov 22 20172.21Yes Yes YesSilverCarlos Rodriguez 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs

HowTo / Notes

About System Specs

Please when submit results add hardware specs like as: cpu - mount of ram - videocard and videocard driver used

Remember another versions different to vanilla wine or wine staging dont accepted by wine in submited results


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Unplayably Low Frame Rate
by Anonymous on Wednesday August 8th 2018, 13:41
I'm not sure about a Platinum rating. I tried running the game on Wine Staging 3.12 with the following hardware:

CPU: AMD FX-6350 Six-Core @ 6x 3.9GHz
GPU: Radeon RX Vega
RAM: 7989MiB

And I get slideshow frame rates, definitely underneath 30 fps.
The game for whatever reason reverts to full screen mode even when set to windowed mode.
RE: Unplayably Low Frame Rate
by Anonymous on Sunday August 26th 2018, 15:42
Ok, I can sometimes get 60 fps if I run the game with Gallium Nine.
The difference is that if I'm underneath 60 fps, it frame skips as opposed to slowing the game down.
So while I can enjoy seeing a decent frame rate now and then, it is extremely difficult to dodge and get QTE's at
err:d3dcompiler:compile_shader HLSL shader parsing failed.
by Tod Jackson on Wednesday November 29th 2017, 15:27
Regarding the report of failing to launch with this error: err:d3dcompiler:compile_shader HLSL shader parsing failed.

You need a native copy of d3dcompiler_43.dll installed, if for some reason Steam didn't install it for you:
winetricks d3dcompiler_43
Controller Support
by Erik on Sunday April 30th 2017, 8:05
I managed to get a Logitech F310 game pad to work with bayonetta using x360ce:

* get the latest winetricks from git: (verb dotnet45 did not work for me in the latest release version)
* create a separate wine prefix for x360ce
$ WINEARCH=win32 WINEPREFIX=~/wine/x360ce winetricks -q dotnet45
* get x360ce:
* unzip in ~/wine/360ce/drive_c/
* run x360ce: cd ~/wine/x360ce/drive_c/; WINEPREFIX=~/wine/x360ce wine x360ce.exe
* setup your controller
* copy the resulting files xinput1_3.dll and x360ce.ini into your Bayonetta folder under steamapps
* add a DLL override for xinput1_3 and set it to native
Game not launching
by Mikko Niemelä on Friday April 14th 2017, 14:29
If your game is not launching and just stays on a white screen, it's because of a corrupted configuration file. For some reason the game isn't able to generate configuration files. Deleting the file from ~/Bayonetta will allow you to start the game again.
RE: Game not launching
by Carlos Rodriguez on Friday April 14th 2017, 15:39
Yeah this game have problems with save configuration files, more later add updated results

And thanks for advise
RE: Game not launching
by Maxwell on Saturday April 22nd 2017, 19:50
I decided to look a bit deeper into the issue.

Booting up an old Windows machine, I had it generate a `system_data` file, using the absolute minimum settings. I then went ahead and ran the game under WINE and did the same thing.

Here's the md5sums from each file:
94557b0db0352e8a8a916aec13429476 system_data_Windows
94557b0db0352e8a8a916aec13429476 system_data_Wine

As it turns out, the game writes perfectly good configuration files, but it still isn't able to boot using one. it's likely the pop-up that occurs when saving settings is because the game tries to read the saved settings file for errors.

That's all I have for now, though.
RE: Game not launching
by tonix on Thursday July 6th 2017, 8:23
The issue has been analyzed and some patches are proposed at: