Proton: Cuphead (268910)

Created on 23 Aug 2018  Â·  27Comments  Â·  Source: ValveSoftware/Proton

The game launches and its playable, but Steam Controller is not detected by the game.

I have tried both in regular and Big Picture Mode. I can access the overlay while playing the game and it works fine. Tried to change controller mapping as well and still its not detected.

My setup is an updated Archlinux.
Kernel 4.18 so the kernel already has the Steam Controller hid_steam driver.

Game compatibility - Unofficial

Most helpful comment

My wired Xbox One controller wasn't working in Cuphead or other Proton games, then I went into Big Picture mode and unchecked the "Xbox Controller Support" option and it worked fine (Found this solution searching the SPCR Discord server, credit to zinchalk).

All 27 comments

Same problem with the latest official SteamOS. The game did recognize my wired Xbox 360 controllers.

Cuphead isn't detecting any of my controllers. I have steam controller and have tried a DS4. Running pop_os 18.04.

Hello @jmissao can You tell me what drivers are you using? I'm in Arch too but the game won't even start. https://github.com/ValveSoftware/Proton/issues/424
Edited: Game is working now, check my issue.

@necronoise my GPU is a Nvidia GT960M, so I'm 396.51 drivers.

The rest is pretty much an updated arch, 4.18-3 kernel, Proton 3.7, my wm is dwm 6.

Same here won't detect any controller even though Steam sees the controller. Using a DS4 connected via USB, Ubuntu 18.04 64bit, Nvidia GTX 960 - driver 396.54. Proton 3.7-3, i5-4690.
Same controller setup is working fine with other Steam Play games

Using ds4drv driver for the joypad - https://github.com/chrippa/ds4drv

Cuphead Working now (268910)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/424.
@necronoise posted on 2018-08-24T18:15:33:

Arch Linux
Kernel 4.18.3
Proton 3.7
bspwm 0.9.5
CPU Intel Core i3-2350m @ 4x 2.3GHz
RAM 4gb
GPU Intel(R) HD Graphics 3000

Logs: https://gist.github.com/necronoise/46b76ddc898ebba805b92eed18329206


@necronoise commented on 2018-08-26T15:08:55

I clicked in 'Verify integrity of game files...' and now its working more than better, my FPS is amazing and i'm so happy to play it on Linux!

Used this command to run. Working very nice.

PROTON_USE_WINED3D11=1 %command%

The only bug i get its the / its not showing up.
image_2018-08-26_12-02-40


@bisby commented on 2018-08-31T19:43:32

I have the game beaten but my parry achievements are still at 0/20 and 0/100. Everything is working great (playing with an Xbox one controller, the steam controller stuff wasn't working properly) except these achievements. Already have most of the other achievements, just wasn't sure if there was an issue with proton counting incremental achievements.

Cuphead is not working with my steam or xbox one controllers either.

Cuphead works only with wired controllers. Steam controller via wireless/bluetooth doesn't work same for xbox one s controller and ps4 controller. With USB cable all controllers works!

To clarify for mine:

Steam controller works when mapped to keyboard commands. Steam controller doesn't work when mapped to xbox controls. (which is the same behavior I experienced on regular wine)

Xbox One controller works fine on USB or bluetooth (using xpadneo).

@fabry92 @bisby

For me it seems that the steam controller will only work (wired or wireless) if I map the controls to keyboard keys. Xbox one controller actually is working! If you proceed through the pause screen with a keyboard you'll need to reassign the controller in the game's options menu. My bad!

My wired Xbox One controller wasn't working in Cuphead or other Proton games, then I went into Big Picture mode and unchecked the "Xbox Controller Support" option and it worked fine (Found this solution searching the SPCR Discord server, credit to zinchalk).

Cuphead worked fine for me with "PROTON_USE_WINED3D11=1 %command%", including with Xbox 360 controllers. The only issue was some graphical glitches with assets not appearing, which made a couple of levels considerably more difficult.

Cuphead crashes at start

Issue transferred from https://github.com/ValveSoftware/Proton/issues/1696.
@kenogo posted on 2018-10-05T18:48:27:

Compatibility Report

  • Name of the game with compatibility issues: Cuphead
  • Steam AppID of the game: 268910

System Information

  • Arch Linux
  • GPU: Intel Mobile 4 Series Integrated Graphics
  • Driver/LLVM version: Mesa 18.2.1-2
  • Kernel version: 4.18.12
  • Proton version: Problem occurs with 3.7-6 and 3.7-7

Symptoms

Game crashes at start with a dialog informing that a crash report was put next to the game executable

output_log.txt

Initialize engine version: 5.6.2p1 (8a29de46e0a0)
GfxDevice: creating device client; threaded=1
d3d11: failed to create factory (887a0004).
GfxDevice: creating device client; threaded=1
Crash!!!
SymInit: Symbol-SearchPath: '.;Z:\home\\keno\\.local\\share\\Steam\\steamapps\\common\\Cuphead;Z:\\home\\keno\\.local\\share\\Steam\\steamapps\\common\\Cuphead;C:\\windows;C:\\windows\\system32;SRV*c:\\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'steamuser'
OS-Version: 6.1.7601 (Service Pack 1) 0x0-0x1
Z:\home\\keno\\.local\\share\\Steam\\steamapps\\common\\Cuphead\\Cuphead.exe:Cuphead.exe (00400000), size: 19156992 (result: 0), SymType: '-nosymbols-', PDB: 'Z:\\home\\keno\\.local\\share\\Steam\\steamapps\\common\\Cuphead\\Cuphead.exe', fileVersion: 5.6.2.10718
C:\windows\\system32\
tdll.dll:ntdll.dll (7BC10000), size: 1044480 (result: 0), SymType: '-exported-', PDB: 'C:\windows\\system32\
tdll.dll', fileVersion: 6.1.7601.24059
C:\windows\\system32\\KERNEL32.dll:KERNEL32.dll (7B410000), size: 4038656 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\KERNEL32.dll', fileVersion: 5.1.2600.2180
C:\windows\\system32\\hid.dll:hid.dll (7EB60000), size: 69632 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\hid.dll', fileVersion: 10.0.0.0
C:\windows\\system32\\user32.dll:user32.dll (7E970000), size: 2002944 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\user32.dll', fileVersion: 5.1.2600.2180
C:\windows\\system32\\gdi32.dll:gdi32.dll (7E840000), size: 1159168 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\gdi32.dll', fileVersion: 10.0.0.0
C:\windows\\system32\\advapi32.dll:advapi32.dll (7E7C0000), size: 450560 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\advapi32.dll', fileVersion: 5.1.2600.2180
C:\windows\\system32\\version.dll:version.dll (7E7A0000), size: 90112 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\version.dll', fileVersion: 5.1.2600.2180
C:\windows\\system32\\ole32.dll:ole32.dll (7E660000), size: 1294336 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\ole32.dll', fileVersion: 10.0.0.0
C:\windows\\system32\pcrt4.dll:rpcrt4.dll (7E5D0000), size: 479232 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\pcrt4.dll', fileVersion: 5.1.2600.2180
C:\windows\\system32\\shlwapi.dll:shlwapi.dll (7E560000), size: 413696 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\shlwapi.dll', fileVersion: 6.0.2800.1692
C:\windows\\system32\\shell32.dll:shell32.dll (7E2C0000), size: 2686976 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\shell32.dll', fileVersion: 6.0.2900.6242
C:\windows\\system32\\opengl32.dll:opengl32.dll (7A820000), size: 1167360 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\opengl32.dll', fileVersion: 5.1.2600.2082
C:\windows\\system32\\winmm.dll:winmm.dll (7E200000), size: 720896 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\winmm.dll'
C:\windows\\system32\\msacm32.dll:msacm32.dll (7E1D0000), size: 163840 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\msacm32.dll'
C:\windows\\system32\\ws2_32.dll:ws2_32.dll (7E1A0000), size: 184320 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\ws2_32.dll', fileVersion: 5.1.2600.5512
C:\windows\\system32\\oleaut32.dll:oleaut32.dll (7E080000), size: 1130496 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\oleaut32.dll', fileVersion: 6.0.6001.18000
C:\windows\\system32\\imm32.dll:imm32.dll (7E050000), size: 81920 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\imm32.dll', fileVersion: 5.1.2600.2180
C:\windows\\system32\\dnsapi.dll:dnsapi.dll (7E030000), size: 65536 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\dnsapi.dll', fileVersion: 5.2.3790.4318
C:\windows\\system32\
etapi32.dll:netapi32.dll (7DF80000), size: 176128 (result: 0), SymType: '-exported-', PDB: 'C:\windows\\system32\
etapi32.dll'
C:\windows\\system32\\iphlpapi.dll:iphlpapi.dll (7DF60000), size: 106496 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\iphlpapi.dll', fileVersion: 5.1.2600.2180
C:\windows\\system32\\winhttp.dll:winhttp.dll (7DF20000), size: 196608 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\winhttp.dll', fileVersion: 5.1.2600.2180
C:\windows\\system32\\jsproxy.dll:jsproxy.dll (7DFF0000), size: 94208 (result: 0), SymType: '-exported-', PDB: 'C:\\windows\\system32\\jsproxy.dll'
C:\windows\\system32\\msvcrt.dll:msvcrt.dll (F6050000), size: 659456 (result: 87), SymType: '-unknown-', PDB: '', fileVersion: 7.0.2600.2180
C:\windows\\system32\\lsteamclient.dll:lsteamclient.dll (F5EE0000), size: 1413120 (result: 87), SymType: '-unknown-', PDB: ''
C:\windows\\system32\\api-ms-win-core-winrt-l1-1-0.dll:api-ms-win-core-winrt-l1-1-0.dll (F4890000), size: 49152 (result: 87), SymType: '-unknown-', PDB: ''
C:\windows\\system32\\combase.dll:combase.dll (F4870000), size: 98304 (result: 87), SymType: '-unknown-', PDB: ''
C:\windows\\system32\\api-ms-win-core-com-l1-1-1.dll:api-ms-win-core-com-l1-1-1.dll (F4850000), size: 77824 (result: 87), SymType: '-unknown-', PDB: ''
C:\windows\\system32\\api-ms-win-core-winrt-string-l1-1-0.dll:api-ms-win-core-winrt-string-l1-1-0.dll (F4840000), size: 53248 (result: 87), SymType: '-unknown-', PDB: ''
C:\windows\\system32\\winex11.drv:winex11.drv (F47B0000), size: 561152 (result: 87), SymType: '-unknown-', PDB: '', fileVersion: 10.0.0.0
Z:\home\\keno\\.local\\share\\Steam\\steamapps\\common\\Cuphead\\Cuphead_Data\\Mono\\mono.dll:mono.dll (10000000), size: 2297856 (result: 0), SymType: '-nosymbols-', PDB: 'Z:\\home\\keno\\.local\\share\\Steam\\steamapps\\common\\Cuphead\\Cuphead_Data\\Mono\\mono.dll', fileVersion: 1.0.0.1
C:\windows\\system32\\psapi.dll:psapi.dll (F46F0000), size: 24576 (result: 87), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.3264
C:\windows\\system32\\mswsock.dll:mswsock.dll (F46D0000), size: 73728 (result: 87), SymType: '-unknown-', PDB: '', fileVersion: 4.0.0.0
C:\windows\\system32\\shcore.dll:shcore.dll (F4690000), size: 77824 (result: 87), SymType: '-unknown-', PDB: ''
C:\windows\\system32\\d3d11.dll:d3d11.dll (6A540000), size: 2195456 (result: 0), SymType: '-nosymbols-', PDB: 'C:\\windows\\system32\\d3d11.dll'
C:\windows\\system32\\vulkan-1.dll:vulkan-1.dll (F4680000), size: 45056 (result: 87), SymType: '-unknown-', PDB: '', fileVersion: 10.0.0.0
C:\windows\\system32\\winevulkan.dll:winevulkan.dll (F4640000), size: 208896 (result: 87), SymType: '-unknown-', PDB: '', fileVersion: 10.0.0.0
C:\windows\\system32\\dxgi.dll:dxgi.dll (6F400000), size: 1720320 (result: 0), SymType: '-nosymbols-', PDB: 'C:\\windows\\system32\\dxgi.dll'
C:\windows\\system32\\openvr_api_dxvk.dll:openvr_api_dxvk.dll (04960000), size: 495616 (result: 0), SymType: '-nosymbols-', PDB: 'C:\\windows\\system32\\openvr_api_dxvk.dll', fileVersion: 1.0.10.0
C:\windows\\system32\\api-ms-win-core-synch-l1-2-0.dll:api-ms-win-core-synch-l1-2-0.dll (F45D0000), size: 77824 (result: 87), SymType: '-unknown-', PDB: ''
C:\windows\\system32\\api-ms-win-core-fibers-l1-1-1.dll:api-ms-win-core-fibers-l1-1-1.dll (F45C0000), size: 61440 (result: 87), SymType: '-unknown-', PDB: ''
C:\windows\\system32\\api-ms-win-core-localization-l1-2-1.dll:api-ms-win-core-localization-l1-2-1.dll (F45B0000), size: 45056 (result: 87), SymType: '-unknown-', PDB: ''
C:\windows\\system32\\d3d9.dll:d3d9.dll (F4570000), size: 225280 (result: 87), SymType: '-unknown-', PDB: '', fileVersion: 5.3.1.904
C:\windows\\system32\\wined3d.dll:wined3d.dll (F4430000), size: 1269760 (result: 87), SymType: '-unknown-', PDB: '', fileVersion: 10.0.0.0
C:\windows\\system32\\dbghelp.dll:dbghelp.dll (F2AB0000), size: 327680 (result: 87), SymType: '-unknown-', PDB: '', fileVersion: 6.1.7601.17514

========== OUTPUTING STACK TRACE ==================

  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 00C170C9)
0x00C170C9 (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 00C1796B)
0x00C1796B (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 0069AB38)
0x0069AB38 (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 0069FE3F)
0x0069FE3F (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 006831B5)
0x006831B5 (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 006E7153)
0x006E7153 (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 006F4646)
0x006F4646 (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 0068500C)
0x0068500C (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 00686E68)
0x00686E68 (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 00AF5133)
0x00AF5133 (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 00476ECA)
0x00476ECA (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 00C4C768)
0x00C4C768 (cuphead) 
  ERROR: SymGetSymFromAddr64, GetLastError: 'Erfolg.' (Address: 00C8A3D4)
0x00C8A3D4 (cuphead) 
0x7B4611DC (kernel32) call_process_entry
0x7B462A36 (kernel32) start_process
0x7B4611EA (kernel32) start_process_wrapper

========== END OF STACKTRACE ===========

**** Crash! ****

Reproduction

It seems that other people got Cuphead working, so I don't know how to reproduce that error. For me, it was just installing Cuphead and clicking "Play".

Worked perfectly for me even with DXVK enabled on Proton 3.16-3 with Nvidia 410.66 with a bluetooth PS4 revision 2 controller.

The Game won't run at first on my new machine (Ryzen 7 & RX580, MESA 19.0.0, Kubuntu 18.04 LTS), but it runs magically after I enabled DRI3.

The Game won't run at first on my new machine (Ryzen 7 & RX580, MESA 19.0.0, Kubuntu 18.04 LTS), but it runs magically after I enabled DRI3.

I'm not sure this is a problem, I was under the impression that DRI3 is the configuration you should be running nowadays in general on AMD or Intel.

The Game won't run at first on my new machine (Ryzen 7 & RX580, MESA 19.0.0, Kubuntu 18.04 LTS), but it runs magically after I enabled DRI3.

I'm not sure this is a problem, I was under the impression that DRI3 is the configuration you should be running nowadays in general on AMD or Intel.

Sorry, I was wrong: I did change the launch options to PROTON_USE_WINED3D11

The Game runs with PROTON_USE_WINED3D11. I would rate that Platinum, but there's a Gamepad problem which renders the game unusable for me personally. The Xbox360 Wireless Controller was working partially, but the key mapping is off: no A,B,X,Y Buttons are active (with few exceptions like A in the Map view, but impossible to play a Level), pushing some button combination leads back to the desktop, while the game runs, and then the controller pushes the mouse cursor constantly to the right until the controller is turned off. I haven't tinkered anything on the controller side, it's the standard xpad driver.

The Game won't run at first on my new machine (Ryzen 7 & RX580, MESA 19.0.0, Kubuntu 18.04 LTS), but it runs magically after I enabled DRI3.

I'm not sure this is a problem, I was under the impression that DRI3 is the configuration you should be running nowadays in general on AMD or Intel.

Sorry, I was wrong: I did change the launch options to PROTON_USE_WINED3D11

It sounds like there's something wrong with your Vulkan config. Can you run other games with dxvk or Vulkan?

Works great for me with Launch Options set to "PROTON_USE_WINED3D11=1 %command%" (otherwise it crashes on startup). Xbox 360 controller, keyboard, audio, and video all work fine. There is a small horizontal line artifact toward the top of my screen while moving around in the overworld map, but is certainly acceptable.
Intel Core i5-3570K CPU with NVidia GTX 670 (and Nouveau drivers)

Runs mostly OK here, though with occasional graphical glitches. These were not an issue until I got to the devil, when I drop through to the second stage his large head flashes in and out of view. If I escape and return to the home screen, everything is glitchy, from the MDHR logo to the cuphead sprites before the menu screen.

Edit: Ubuntu 18.04, Intel Corporation HD Graphics 620 (rev 02)

796

The Game won't run at first on my new machine (Ryzen 7 & RX580, MESA 19.0.0, Kubuntu 18.04 LTS), but it runs magically after I enabled DRI3.

I'm not sure this is a problem, I was under the impression that DRI3 is the configuration you should be running nowadays in general on AMD or Intel.

Sorry, I was wrong: I did change the launch options to PROTON_USE_WINED3D11

It sounds like there's something wrong with your Vulkan config. Can you run other games with dxvk or Vulkan?

You were right, I missed vulkan drivers back then. But it had nothing to do with the main problem: the controller problem persists. The game just won't accept my standard xbox360 wireless controller and it's not the only game (in Raiden IV Overkill the left-up direction seems to be default, rendering the game unplayable with this controller).

The Game seems to know only keyboard controls (shown by the key indicators in the lower-right corner when in Game Menu, same for Raiden IV Overkill), even when I start the game by controller inputs, also starting it in Big Screen Mode doesn't make any difference (does Big Screen Mode ever make any difference In-Game for controller inputs anyway?).

Today I started the game by Wine Steam (for windows) installed with Lutris and everything works perfectly (same for Raiden IV Overkill). The controller works out of the box, it's accepted from the start of the game (button indicator in the lower left shows an A instead of the Keyboard equivalent button), I can configure the buttons and it plays like it's intended to. Very strange. So it's definitly a Proton problem.

Cuphead not launching

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2640.
@dylanmtaylor posted on 2019-05-04T21:16:07:

I just get a pop-up that says:

Failed to initialize graphics.
Make sure you have DirectX 11 installed, have up to date
drivers for your graphics card and have not disabled
3D acceleration in display settings.
InitializeEngineGraphics failed

I'm running Antergos Linux (fully up to date) on GNOME with an AMD 2700X CPU and a Radeon VII graphics card.

Hello @dylanmtaylor, please verify you have the vulkan-radeon and lib32-vulkan-radeon packages installed, which is the userspace half of the vulkan driver stack for your video card.

After installing those packages, it worked.

This game was found in the 2019-07-31 whitelist update.

If you encounter an issue with this game, please search the open issues for 268910, and report any issues encountered with this game in separate issue reports, one issue per issue report.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

kforney picture kforney  Â·  3Comments

shaphanpena1 picture shaphanpena1  Â·  3Comments

prototype99 picture prototype99  Â·  3Comments

lumni1968 picture lumni1968  Â·  3Comments

BLaDZer picture BLaDZer  Â·  3Comments