Yakuza: Like a Dragon (1235140)

[alosarjos]

Compatibility Report

• Name of the game with compatibility issues: Yakuza: Like a Dragon
• Steam AppID of the game: 1235140

System Information

• GPU: AMD 5700XT
• Driver/LLVM version: Mesa 20.2.2
• Kernel version: 5.9.6
• Link to full system information report: Gist
• Proton version: 5.13-2 RC

I confirm:

• [X ] 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.

Proton Log:

steam-1235140.log

Symptoms

Game won't launch

[HassaanMahmood1999]

@kisak-valve Thank you for your help, adding the %command% to the launch option allowed for the game window to open however it remains black. Is there a workaround for this problem?

[HassaanMahmood1999]

@kisak-valve Disregard my previous post, the game works now after a reinstall. Thank you for your suggestions

[alosarjos]

Game just got updated, may be worth checking our list of current problems to see if any has been fixed.

For example, setting off multi-sampling now it's fixed and wont crash the game

[olav-valle]

1.02 patch notes claim "Fixes for issues with controller mapping on wireless controllers", so here goes.

All tests were done with js-test open to confirm and compare registered inputs. The TL;DR is that Xbox pads still seem broken (at least the Elite 2), PlayStation still works with Steam Input forced off, and Switch Pro still has the R-stick issue.

One detail I hadn't noticed before is that inputs from the paddles on the back of the Elite are incorrectly mapped in the same way as the rest of the controller. E.g., I have one profile where the A paddle acts as R-stick click, and this is picked up by the game as Select in the same way as the actual R-stick click is. I have no idea if this is useful information to anyone, but there it is.

The results, aka "i herd u leik permutations":

Controller Model	Connection Type (driver)	Forced Steam Input Per-Game Setting	Config. Support (overridden by Per-Game Setting)	Works?	Comment
Xbox Elite 2	Wireless Dongle (Xow)	On	On	No response to input.
Xbox Elite 2	Wireless Dongle (Xow)	Default	On	No response to input.
Xbox Elite 2	Wireless Dongle (Xow)	Off	Off	Incorrect mappings. Camera rotates and tilts unless RT and LT are pulled 50%.	No D-pad, LT=Ry, RT=Rx, ABXY correct, LB/RB correct, select=LT, start=RT, L-click=Start, R-click=Select, Xbox button = select
Xbox Elite 2	Bluetooth (xpadneo)	Off	On	Incorrect mappings. Camera rotates and tilts.	Same as above, except: L-click=Select, R-click=Start, Xbox button does nothing
Xbox Elite 2	Bluetooth (xpadneo)	Off	Off	Incorrect mappings. Camera rotates and tilts.	Same as above.
Xbox Elite 2	Bluetooth (xpadneo)	On	On	No response to input.
Xbox Elite 2	Bluetooth (xpadneo)	Default	On	No response to input.
Xbox Elite 2	Wired (xpad)	Off	Off	Incorrect mappings. Camera rotates and tilts.	Mappings identical to wireless dongle.
Xbox Elite 2	Wired (xpad)	On	On	No response to input.
DualShock 4	Bluetooth (hid_sony)	Off	Off	No change from before patch: Works, but no touchpad.
DualShock 4	Bluetooth (hid_sony)	On	On	No response to input.	This is a change from before the patch, where forcing Steam Input on would make the PS4 pad appear to the game as an Xbox pad, with the same incorrect mappings as other Xbox pads.
Switch Pro	Bluetooth (hid_generic)	Off	Off	No change from before patch.	Only R-stick is incorrect, with y-axis moving x-axis, and y-axis being unbound.
Switch Pro	Bluetooth (hid_generic)	On	On	No response to input.

[sonic2kk]

Very unfortunate that it's still not working. I wonder if the controller issues were fixed on Windows even, in that are the people who had these mapping issues natively still having them.

[sonic2kk]

Not that I really expected the results to differ much but my Steam Controller still has the incorrect mapping as well. Not surprising since the game still sees it as an Xbox controller. I also tried with various Steam Input forced settings, Steam Overlay on and off, and also tried with SC-Controller. No luck with these options either.

I wonder if the game is still at fault, or if it is an issue that'll get fixed similar to how Yakuza Kiwami's controller support got fixed with a Wine patch.

An interesting side note: This update has pretty significantly boosted performance for me to a reliable 110fps with everything at max settings. The game also felt faster with the Steam Overlay off but I haven't been able to verify yet (MangoHud, my preferred tool, does not currently work with Proton 5.13)

[sonic2kk]

Proton-GE was released which is based on Wine 5.21, so I thought I'd give it a go and see how it worked but had no luck. The new release doesn't require the launch option so it'll work out of the box in that regard, but the controller mappings are still wrong - However, they are wrong in different ways!

Before, R-Stick for me was Start (pause game) and L-Stick was Select (Map). This has now reversed! The D-Pad is still broken, and R-Stick doesn't control the camera. Unfortunately though, the biggest dealbreaker here is that the camera is constantly spinning. I wonder what has caused this spinning camera, I can confirm it isn't there in the custom noname_pipes patched version of Proton from this thread and that if my controller is off, it does not happen. I tried a few different variations of forcing controller on/off and using my Switch Pro Controller, as well as using SC-Controller. They all had the same issues.

Out Run, Super Hang-On, Fantasy Zone and Space Harrier (side arcade games you can play) are still broken for anyone wondering, but they're broken on Windows (and reportedly on Xbox Series X as well). However, the Virtua Fighter 2 and Virtua Fighter 5 seem to work fine. As mentioned by others in this thread, I think we'll just have to wait for a patch for the myriad of issues this release seems to have.

[sonic2kk]

Quick follow up with Proton-tkg with Wine 5.22; still no luck getting the controller to work, but it fixes the spinning camera issue. The button mappings are also back to being the way they are in builds of Proton based on Wine 5.13. The arcade games I mentioned are still busted.

I'll edit this post if I make any progress, but I doubt I will.

---

EDIT: Amidst my research I found some interesting things, building on top of the table provided by olav-valle. In the game's input.ini file, it lists the input codes for controllers and for keyboard/mouse. Sadly it seems like editing this file does nothing, and mappings are overridden when the game is opened again.

The first value is for the controller, the second value is for the keyboard/mouse. Below are the mappings for showing the main menu and the map.

Display_Main_Menu="9,27"
View_Map="8,9"

On an Xbox Controller, Display_Main_Menu should be mapped to Start, and View_Map should be mapped to Select. To recap, these buttons are in reality bound to Left Stick Down (LSD) for Display_Main_Menu and Right Stick Down (RSD) for View_Map. To my understanding, Yakuza: Like a Dragon expects you to be using an Xbox One controller.

I installed a tool called jstest from joyutils and it gives information on the controller you currently have connected. As I'm using a Steam Controller, I'm using SC-Controller to globally map it as an Xbox 360 controller system-wide. As expected, jstest properly detects this. So for all intents and purposes, going forward I'll be referring to my Steam Controller with SC-Controller to refer to the Xbox 360 controller.

From my inputs with jstest, here are codes (Note that 8 is missing likely as it is the "mode" button, e.g. the Xbox button or Steam button):

A=0
B=1
X=2
Y=3

LBUMP=4
RBUMP=5

SELECT=6
START=7

LSD=9
RSD=10

The face buttons, A/B/X/Y, are correctly mapped, so we can leave those for now. But we have a problem here - The input.ini earlier has different mappings for Select and Start! Here, we don't have an 8, but 9 is mapped to DISPLAY_MAIN_MENU. The code 9 also happens to represent pushing down on the left stick (LSD), and this is also the behaviour we see in the game. As for why 8 is missing with this tool I'm not sure. Here is a visual of how the codes seem to correspond to the buttons on the Xbox 360 Controller:

In other words, the codes we're passing to the game seem to be 8 and 9, which correspond to LSD and RSD. The game is looking for these, as it expects these to be Select and Start. However, our codes in jstest for Select and Start are 6 and 7. The game has the following entry for button code 6:

Party_Status="6,90"

In the game, this is "Toggle Party Status" and by default is bound to Left Bumper. It's the setting that toggles the display of your party members health, level, etc. But this button is mapped correctly - In other words, the game sees 6 as Left Bumper. To check, I tried changing the binding to Right Bumper and the code changed to 7.

From here, I tried remapping the Show Map button to "Back", and it mapped this to Left Trigger. When I checked the INI file, View_Map was bound to code 4! This means the game thinks 4 corresponds to Left Trigger instead of Left Bumper. But why 4? Looking at the mappings on the x360ce website (controller remapping software for Windows), we can see that Left Trigger corresponds to Axis 4. I could not check what the game thinks the Start button is, as it didn't recognise my presses of it at all similar to how it does not detect the D-Pad. This site also lists LSD and RSD as being codes 8 and 9 - The two buttons the game sees for Select and Start!

In other words, the game is receiving the wrong codes. It is also looking for Button 4 (Back) as Axis 4 (Left Trigger). I suspect this Axis issue is a root cause for why the right stick camera is not working and why the D-Pad is not working either. From what I have tested tonight, this is what the game expects:

A=0
B=1
X=2
Y=3

LTRIG=4 

LBUMP=6
RBUMP=7

SELECT=8
START=9

I have absolutely no idea why the buttons are messed up like this, but as you can see comparing what jstest sees our input as versus what the game expects, there are discrepancies. The axis issue is quite strange as well, it seems as though the game is not correctly differentiating between Buttons and Axis inputs.

[chtaube]

Game just opens a black window with a message box "System does not meet the minimum requirements."

Any ideas what is causing this? Hardware should be good for the game I think.

---

Launch option: PROTON_LOG=1 PROTON_USE_SECCOMP=1 %command%

Proton Log file: steam-1235140-proton-5.9-GE-8-ST.log

[System] OS: Debian GNU/Linux testing bullseye Arch: x86_64 Kernel: 5.9.0-3-amd64 Desktop: XFCE Display Server: x11

[CPU] Vendor: AuthenticAMD Model: AMD Ryzen 7 3700X 8-Core Processor Physical cores: 8 Logical cores: 16

[Memory] RAM: 62.8 GB Swap: 60.5 GB

[Graphics] Vendor: X.Org OpenGL Renderer: Radeon RX 5500 XT (NAVI14, DRM 3.39.0, 5.9.0-3-amd64, LLVM 11.0.0) OpenGL Version: 4.6 (Compatibility Profile) Mesa 20.2.2 OpenGL Core: 4.6 (Core Profile) Mesa 20.2.2 OpenGL ES: OpenGL ES 3.2 Mesa 20.2.2 Vulkan: Supported

[sonic2kk]

@chtaube Your system definitely meets the minimum (and recommended) specs by the looks of it. Only thing I'd suggest trying is switching to Proton-5.21-GE-1 and removing the launch options for the game. See if that solves your issue.

In the meantime, I'll investigate!

EDIT: Doh! Just after posting this I just thought of something! If you have Protontricks installed on your system you can run protontricks 1235140 --gui winecfg to open winecfg for the game's Proton prefix. From here, check your Windows version at the bottom of the window that just opened. Make sure that it's set to Windows 10. If it's not, select it from the dropdown and click apply.

[chtaube]

@sonic2kk Thanks for investigating!

Switched to Proton-5.21-GE-1 but unfortunately still doesn't work. Also checked the Windows version as you described and it's set to Windows 10 already. Moved the game to another (faster) Steam library and deleted steamapps/compatdata/1235140 to have the wine prefix recreated, but no effect.

steam-1235140-proton-5.21-GE-1.log

As a side note: When using Proton-5.21-GE-1, games never seem to quit. Steam keeps showing the game as running, even after I'd quit it.

[chtaube]

Ok, I got the game running! The issue must be related to the ASUS RX 5500 XT graphics card. Game starts without any issues after I replaced the graphics card with an Sapphire RX 5700 XT.

Anyway, I have another machine with Ryzen 5 3600X + RX 5500 XT where I can test running the game next week. At least, after I got it working on my main machine, I don't have reasons to refund the game :)

Ok, I refunded the game cause I got locked out for 24 hours for whatever reasons. Might give it another try when things have settled.

[sonic2kk]

@chtaube The lockout is related to the Denuvo DRM. Even on Windows, if you launch the game from more than two different PCs too quickly in a day, the game will lock you out. This will only change if/when Denuvo Anti-Tamper is removed from the game, or if SEGA lax the DRM restrictions.

---

I just tested Patch 1.03, and controller support is still broken regardless of what I test. The old arcade games (OutRun, Super Hang-on, etc) are still broken. Upon reading a comment on a Steam discussion and then investigating myself, it seems like the files for those old games are missing entirely. Many Windows players are also voicing similar complaints around these games, so I would hazard a guess that the arcade game issue is not related to Proton. Pachinko DLC is still broken, and again this is also broken for many users on Windows - The Steam reviews speak for themselves on this matter.

[sonic2kk]

I've been able to confirm that the issue with the arcade games is indeed an issue with the game. It's missing the files for the old arcade games. I followed a Steam guide which takes the files from copies of the game that do work, and was able to get them working. Played a little bit of Out Run and it was fine. Interestingly, this has sound, while the games in Yakuza 0 do not.

As a small aside, I tested the game with the latest Proton-tkg 6.0-RC release and it did not have any controller support. The changelog for Wine 6.0-RC shows some controller changes, however I tested some other games and they worked fine; NieR:Automata, Resident Evil 3, and Hades. Going back to older versions of Proton fixes this issue, however all but the noname_pipes build that was initially provided do not show keyboard prompts if a controller is connected as of Patch 1.03.1 specifically. Pachinko DLC is also still broken but as mentioned, this is also broken on Windows.

[kisak-valve]

Hello @sonic2kk, thanks for identifying that an issue with this game isn't caused by Proton, however, we can not condone third party distribution of game content here, so I've removed the link to the workaround in your last post. Since windows users are equally affected, the best option is to bring that issue to the attention of the game's dev(s).

[eth0OS]

Just my 2 cents over the controller issues, I've been talking with other LaD players and it looks like the controller issues on Windows are 100% fixed, at least on patch 1.04, so the fix may have to come through the wine/proton devs efforts.

[yoyossef]

I'm also getting the "System does not meet the minimum requirements." window with Proton 5.13-4/Proton Experimental despite running on a Ryzen 9 3900X w/ a RX 6800XT.

Screenshot


steam-1235140.log

System Information

``` Processor Information: CPU Vendor: AuthenticAMD CPU Brand: AMD Ryzen 9 3900X 12-Core Processor CPU Family: 0x17 CPU Model: 0x71 CPU Stepping: 0x0 CPU Type: 0x0 Speed: 3800 Mhz 24 logical processors 12 physical processors HyperThreading: Supported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Supported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported AVX2: Unsupported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Unsupported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: "Arch Linux" (64 bit) Kernel Name: Linux Kernel Version: 5.10.0-rc7-98-tkg-upds X Server Vendor: The X.Org Foundation X Server Release: 12010000 X Window Manager: KWin Steam Runtime Version: steam-runtime_0.20201203.1 Video Card: Driver: AMD AMD SIENNA_CICHLID (DRM 3.40.0, 5.10.0-rc7-98-tkg-upds, LLVM 11.0.0) Driver Version: 4.6 (Compatibility Profile) Mesa 21.0.0-devel (git-4eaff8dba7) OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 164 Hz VendorID: 0x1002 DeviceID: 0x73bf Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 2560 x 1440 Desktop Resolution: 2560 x 1440 Primary Display Size: 27.44" x 15.43" (31.46" diag) 69.7cm x 39.2cm (79.9cm diag) Primary VRAM: 16384 MB Sound card: Audio device: ATI R6xx HDMI Memory: RAM: 32090 Mb VR Hardware: VR Headset: None detected ```

[kisak-valve]

Hello @yoyossef, please copy your system information from Steam (Steam -> Help -> System Information) including the extended diagnostic information and put it in a gist, then include a link to the gist in this issue report.

I suspect that the game is trying to run with lavapipe instead of the video card and temporarily disabling it with something like sudo mv /usr/share/vulkan/icd.d/lvp_icd.x86_64.json /usr/share/vulkan/icd.d/lvp_icd.x86_64.json.disabled might help.

[yoyossef]

Hello @yoyossef, please copy your system information from Steam (Steam -> Help -> System Information) including the extended diagnostic information and put it in a gist, then include a link to the gist in this issue report.

I suspect that the game is trying to run with lavapipe instead of the video card and temporarily disabling it with something like sudo mv /usr/share/vulkan/icd.d/lvp_icd.x86_64.json /usr/share/vulkan/icd.d/lvp_icd.x86_64.json.disabled might help.

Hi @kisak-valve, here is the complete system info including the extended diagnostic information: system-info

And the logs associated with the run: steam-1235140.log

I did try your recommendation but it didn't work.

[kisak-valve]

Thanks, unfortunately the log doesn't make sense to me, the way I read it: 1) the game is in startup 2) there's two OutputDebugStringA messages and a bunch of seh noise that comes with them 3) the game closes without crashing

[BillFleming]

Is there any type of controller that works ok in this game on Linux? Does the steam controller work well? I can confirm that using a win7 VM that the original xbox 360 wireless adapter worked ok even before the recent patches.

[sonic2kk]

@BillFleming I personally use a Steam Controller and it doesn't work. Switch Pro Controller doesn't work, neither does a third party Switch Pro Controller. Wired Xbox 360 clone controller doesn't work, and SC-Controller doesn't work either (tool to make the Steam Controller show up as an Xbox 360 controller).

Some users have had moderate success with the DualShock 4 controller, but the touchpad doesn't seem to work. You could try that controller.

[dgurney]

@BillFleming I play with a DS4, and apart from the touchpad issue mentioned earlier it works perfectly fine.

[sonic2kk]

@dgurney Out of curiosity, have you tried mapping it in the Steam Controller Configuration? Or rather, checking if it's mapped? I was looking around last night in the menus and seen an option I think is related to the DS4 touchpad. It probably is already mapped but in the interest of being thorough I thought I'd ask 😅

[dgurney]

@sonic2kk Unfortunately none of the Steam mapping options are available since Steam Input must be forced off for the DS4 to be usable.

[yoyossef]

Thanks, unfortunately the log doesn't make sense to me, the way I read it:

1. the game is in startup
2. there's two OutputDebugStringA messages and a bunch of seh noise that comes with them
3. the game closes without crashing

Hi @kisak-valve, with the help of a few members we found out that using DXVK's dxgi fixes the issue of the game saying that I'm not meeting the minimum required specs.

Adding WINEDLLOVERRIDES=dxgi=n to the launch arguments gets me past that error and the game seems to render correctly.

Maybe some bug report needs to be filled but I wanted to inform you first.

[eth0OS]

Hello everyone, the new proton-experimental brought some fixes for Yakuza Like a Dragon gamepad handling. I can't test at the moment but I am curious if the situation have improved.

[PSebs]

I can say that my steam controller works fine in proton experimental.

[BillFleming]

x360 wireless controller appears to be working perfectly fine now. 👍 Who do we send Japanese :beer: to for fixing this?

[sonic2kk]

Can also confirm my Steam Controller is working fine with the latest Proton Experimental! Now we can finally be real Yakuza 😄

[BillFleming]

After finally finding the dongle the xbone wireless controller using xow worked and also for the first time I have seen controller hotplug actually work. I had Dragon running in the background, plugged in the xbone (newer slim) dongle and immediately Yakuza recognized the controller when connected. 👍 👍 👍 😃

[digaxfr]

I am delighted to report that the PlayStation 5 controller (over USB-C and Bluetooth) works for me with the latest Proton Experimental (I was on Proton-5.21-GE-1 prior to this). I only have the PS5 controller enabled in my controller settings. PlayStation button prompts work as well.

[olav-valle]

Can confirm that Xbox Elite 2 wireless on XOW now works, with steam input disabled. 🎉

[sonic2kk]

I may have spoken too soon: With my Steam Controller, the triggers are no longer recognised. I've tested with standard Steam Controller drivers, using SC-Controller with Steam Input forced off, and using SC-Controller with Steam Input forced on. Not sure if this was alwasys the case or a regression with the latest 1.07 patch for the game (which is unlikely).

[sonic2kk]

Issue with triggers is still present with the latest Proton Experimental, and with the latest update to the patchset that initially fixed the broader issue with controlles (e.g. on builds of Proton-tkg 6.1 and Proton-GE 6.1 the triggers are still not recognised)

[mvykol]

Not sure if this should go here or somewhere else, but I'm seeing a black screen on launch and I'm unable to get past it. Tried a few different versions of proton but no luck. None of the fixes mentioned here worked for me either.

Here's a log of when I tried with Proton 9.0-3: https://pastebin.com/BZcq2D4E

System info:

OS: Arch Linux
KERNEL: 6.11.3-arch1-1
CPU: 12th Gen Intel Core i7-12700K
GPU: NVIDIA GeForce RTX 3070 Ti
GPU DRIVER: NVIDIA 560.35.03
RAM: 64 GB