Game also doesn't detect any of my gamepads (generic + XB1), no matter if Steam Input is enabled or not. Ubuntu 18.04.2.

steam-838380.log.gz

Related: https://github.com/ValveSoftware/Proton/issues/1549

Game also doesn't detect any of my gamepads (generic + XB1), no matter if Steam Input is enabled or not.

DS4 controller works fine here. Try making sure your controller is configured right in the global settings, and then try right clicking the game and selecting "Edit Steam Controller Configuration"

Forcing steam input to off fixed generic fight stick for me, seems like similar issue is happening on windows: https://steamcommunity.com/app/838380/discussions/0/1843566500520413517

Forcing steam input to off fixed generic fight stick for me

That got my XB1 pad working (but not the generic one). Thanks.

Installing the game in wine-staging (with DXVK and MF) and enabling the DXVA2 VAAPI backend does not make it work, at least on AMD/mesa. It instead completely freezes the game and spits this out in the terminal infinitely.

016c:err:ole:CoGetClassObject no class object {42c9b9f5-16fc-47ef-af22-da05f7c842e3} could be created for context 0x1
016c:err:ole:CoGetClassObject class {3ffb3b8c-eb99-472b-8902-e1c1b05f07cf} not registered
016c:err:ole:CoGetClassObject no class object {3ffb3b8c-eb99-472b-8902-e1c1b05f07cf} could be created for context 0x1
0113:fixme:dxva2:Direct3DDeviceManager9_ResetDevice (0x32471ea0)->(0x325e58a0, 3735928559): semi-stub
016c:err:ole:CoGetClassObject class {926f41f7-003e-4382-9e84-9e953be10562} not registered
016c:err:ole:CoGetClassObject no class object {926f41f7-003e-4382-9e84-9e953be10562} could be created for context 0x1
016c:err:ole:CoGetClassObject class {41457294-644c-4298-a28a-bd69f2c0cf3b} not registered
016c:err:ole:CoGetClassObject no class object {41457294-644c-4298-a28a-bd69f2c0cf3b} could be created for context 0x1
016c:err:ole:CoGetClassObject class {7afa253e-f823-42f6-a5d9-714bde467412} not registered
016c:err:ole:CoGetClassObject no class object {7afa253e-f823-42f6-a5d9-714bde467412} could be created for context 0x1
016c:err:ole:CoGetClassObject class {a8721937-e2fb-4d7a-a9ee-4eb08c890b6e} not registered
016c:err:ole:CoGetClassObject no class object {a8721937-e2fb-4d7a-a9ee-4eb08c890b6e} could be created for context 0x1
016c:err:ole:CoGetClassObject class {a82e50ba-8e92-41eb-9df2-433f50ec2993} not registered
016c:err:ole:CoGetClassObject no class object {a82e50ba-8e92-41eb-9df2-433f50ec2993} could be created for context 0x1
016c:err:ole:CoGetClassObject class {b084785c-dde0-4d30-8ca8-05a373e185be} not registered
016c:err:ole:CoGetClassObject no class object {b084785c-dde0-4d30-8ca8-05a373e185be} could be created for context 0x1
016c:err:ole:CoGetClassObject class {7a56c4cb-d678-4188-85a8-ba2ef68fa10d} not registered
016c:err:ole:CoGetClassObject no class object {7a56c4cb-d678-4188-85a8-ba2ef68fa10d} could be created for context 0x1
016c:err:ole:CoGetClassObject class {42c9b9f5-16fc-47ef-af22-da05f7c842e3} not registered
016c:err:ole:CoGetClassObject no class object {42c9b9f5-16fc-47ef-af22-da05f7c842e3} could be created for context 0x1
016c:err:ole:CoGetClassObject class {3ffb3b8c-eb99-472b-8902-e1c1b05f07cf} not registered
016c:err:ole:CoGetClassObject no class object {3ffb3b8c-eb99-472b-8902-e1c1b05f07cf} could be created for context 0x1
0113:fixme:dxva2:Direct3DDeviceManager9_ResetDevice (0x3251ceb0)->(0x325e58a0, 3735928559): semi-stub
016c:err:ole:CoGetClassObject class {926f41f7-003e-4382-9e84-9e953be10562} not registered
016c:err:ole:CoGetClassObject no class object {926f41f7-003e-4382-9e84-9e953be10562} could be created for context 0x1
016c:err:ole:CoGetClassObject class {41457294-644c-4298-a28a-bd69f2c0cf3b} not registered
016c:err:ole:CoGetClassObject no class object {41457294-644c-4298-a28a-bd69f2c0cf3b} could be created for context 0x1
016c:err:ole:CoGetClassObject class {7afa253e-f823-42f6-a5d9-714bde467412} not registered

That got my XB1 pad working (but not the generic one). Thanks.

Have you tried selecting Generic Gamepad Configuration Support in the global Steam controller settings?

@z0z0z yep, I have both generic and xbox config enabled for my fight stick. I used it in number of fighting games under proton and never had issues with it, DOA is the only game I had to force off steam input.

As already mentioned in the initial post, the Story mode doesn't work. The rest of the game works fine for me and also my gamepad (XBOX One S) works out of the box.

• GPU: GTX 1080
• Driver/LLVM version: nvidia 418.43
• Kernel version: 5.0
• Link to full system information report as Gist: https://gist.github.com/NoXPhasma/28e4ef3359d4354dc9381b558eac678f
• Proton version: 3.16-8

steam-838380.log

203020.388:0026:0082:err:ole:CoGetClassObject no class object {b084785c-dde0-4d30-8ca8-05a373e185be} could be created for context 0x1

That is a png codec winetricks windowscodecs fixed that. Game will still black screen with it.

With Proton 4.2-1 even my generic gamepad works, even though Steam Input still needs to be force off, weirdly enough.

I can confirm that the game except the story mode works. Nintendo Switch Pro controller over bluetooth also worked. Story mode is unplayable because cut-scene videos are not played and get stuck in a black screen. (I looked through the games files and could not find any obvious video files, some files mediainfo identified as OGG.)

steam-838380.log
system_info.txt

Distro: Linux Mint 19.1 Tessa (64 bit)
GPU: Vega 56
Driver/LLVM version: Mesa 19.1.0-devel/9.0.0
Kernel version: 5.0.10-050010-lowlatency
Proton version: 4.2-3

Vulkan Instance Version: 1.1.97

System:    Kernel: 5.0.0-3.1-liquorix-amd64 x86_64 bits: 64 Desktop: Gnome 3.22.3 
           Distro: Debian GNU/Linux 9 (stretch) 
Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] driver: nvidia v: 418.56 
           Display: x11 server: X.Org 1.19.2 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa 
           resolution: 3840x2160~60Hz 
           OpenGL: renderer: GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 418.56 

Proton version: 4.2-3

I cannot start the tutorial and the game became slow after some seconds.
In the log I can see:

2383.661:000c:000d:warn:module:load_dll Failed to load module L"C:\\windows\\system32\\winemenubuilder.exe"; status=c0000135
wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe"
2383.661:000c:000d:trace:module:LdrShutdownProcess ()
2383.662:000a:000b:err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2)
ERROR: ld.so: object '/root/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

2476.259:002a:007b:trace:seh:call_vectored_handlers calling handler at 0x6a433b40 code=406d1388 flags=0
2476.259:002a:007b:trace:seh:call_vectored_handlers handler at 0x6a433b40 returned ffffffff
err:   D3D11: CreateGeometryShaderWithStreamOutput: Rasterized stream not supported

2385.961:002a:002b:err:ole:CoGetClassObject class {e018945b-aa86-4008-9bd4-6777a1e40c11} not registered
2385.961:002a:002b:err:ole:CoGetClassObject no class object {e018945b-aa86-4008-9bd4-6777a1e40c11} could be created for context 0x1

@ValveSoftware please fix all the game problems.
steam-838380.log

@AwesamLinux Do you mind making a Mediainfo file for this game?

The games video files are packaged in a way they can't be easily accessed. But looking through a hex dump of 0x38561b41.file I discovered these lines:

ftypmp4 mp42isomavc1 kmoov lmvhd 
Video Media Handler AVC Coding

TMPGEnc Video Mastering Works 5 Version. 5.5.3.10

x264 - core 136 - H.264/MPEG-4 AVC codec - Copyright 2003-2013 - http://www.videolan.org/x264.html - options: cabac=1 ref=4 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=2 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=18 lookahead_threads=3 sliced_threads=0 slices=1 nr=0 decimate=1 interlaced=0 bluray_compat=0 stitchable=1 constrained_intra=0 bframes=0 weightp=0 keyint=1 keyint_min=1 scenecut=40 intra_refresh=0 rc_lookahead=3 rc=cbr mbtree=0 bitrate=75000 ratetol=1.0 qcomp=0.60 qpmin=3 qpmax=69 qpstep=4 vbv_maxrate=75000 vbv_bufsize=8192 nal_hrd=cbr ip_ratio=1.40 aq=1:1.00

@HonkingGoose I'm pretty sure the videos are MPEG-4, AVC

@AwesamLinux Thanks for looking into this. :smile: I've added the media type and codec to my list at 1464.

@kisak-valve, the newest Proton version wasn't having the issue is 4.2-5

I can confirm that there is no audio with 4.2-6 and that the FAudio build from flibitijibibo fixes it. Audio worked fine with 4.2-5.

Can confirm that the new FAudio build from @flibitijibibo fixes the no audio issue.

Story mode doesn't work with Proton 4.11-11

The cursor isn't hidden when the game starts, I need to switch to other window and switch back to hide the cursor.
Proton 4.11-11

• Story mode doesn't work on proton 5.0-5
• The audio stutters on loading screens.
• Ocasional freezes playing Quest mode/Arcade/Time attack/Survival. Last entry on the log (post freeze) is:

err: D3D11: CreateGeometryShaderWithStreamOutput: Rasterized stream not supported

(afterwards I killed the process).

steam-838380.log

Game runs perfect with the occasional 1 second stutter on a 2060 RTX smooth as butter maxed out after 10 minutes of play VS mode...
Story Mode = black screen ): Proton 5.09

any fixes for story mode yet?

I haven't found one. Really annoying, I have a hunch its to do with their cut-scene encoder or something since it crashes as soon as it loads

really want the story mode lol

The problem persists for me even on Windows 10 x64 fully updated, tested on
AMD Ryzen with a 2060 Super and on Intel 8400 with a 2060 OC and both
systems on Linux MINT 20 using Proton and both systems on Windows.

The game is literally broken, I've tried installing all codecs possible. I
can even open the menu using select and hit skip cutscene but the game was
overpriced already and I can't believe it's that broken...

On Tue, Jul 28, 2020 at 11:17 PM Jhackler [email protected] wrote:

really want the story mode lol

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2420#issuecomment-665312183,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQDBWF5TONWTN7R5M7K2MUDR55E6VANCNFSM4G6W3MXQ
.

Try clearing the cache and cofig files and make sure steam is not downloading any game data from cloud. rare occasions I have had issues in windows from cloud data between linux and windows.

Has the story mode black screen been fixed yet?

Nope

Using this with SteamDeck and story mode is still broken 😢

Compatibility Report

• Name of the game with compatibility issues: Dead or Alive 6 (Deluxe Edition)
• Steam AppID of the game: 838382

System Information

• GPU: RTX 2080 Ti
• Driver/LLVM version: Nvidia 510.60.02
• Kernel version: Linux 5.17.2-256-tkg-pds-llvm
• Link to full system information report as Gist: gist link
• Proton version: 7.0-2

I confirm:

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

steam-838380.log

Symptoms

DLC characters remain locked after purchasing the Deluxe Edition; might be related to this old issue? I can't manage the game's DLC either.

• https://github.com/ValveSoftware/steam-for-linux/issues/60

The game additionally thinks I don't own the full version, which is irritating because I just bought it yesterday.

Reproduction

1. Launch the game
2. Go to versus mode
3. Find all DLC characters locked

@kisak-valve

@kisak-valve That seems to work
Definitely shouldn't be the case though because selecting the tool manually on a per-game basis should be sufficient

steam-838380.log
@kisak-valve There also seems to be a performance hit with this game that I can't find the cause of; I set some of the lowest settings and it suffers a 25-30 FPS loss (it fluctuates) most of the time (which is ridiculous given my hardware) and it seems to suffer from controller input lag in local play (both of which are big no-nos for fighting games)

Just a FYI: this appears to be working with the GE-717 version, I decided to try it on a whim and surprise surprise, the movies played and it let me into story mode...

Story Mode worked with GE-717 version

Story mode videos still black screen under Proton 9 build 15038643, also Proton Experimental build 14944099