Rocksmith 2014 (Remastered) (221680) Unlaunchable

[SoftwareSchlosser]

The game crashes right after the loading screen shows up.

system information

steam-221680.log

[romanstingler]

sysinfo

same here

[Lucretia]

System Info log - with full debugging

[Lucretia]

Added an strace using the following /tmp/proton_laguest/run:

#!/bin/bash
#Run game or given command in environment

cd "/home/laguest/.local/share/Steam/steamapps/common/Rocksmith2014"
DEF_CMD=("/home/laguest/.local/share/Steam/steamapps/common/Rocksmith2014/Rocksmith2014.exe" "-uplay_steam_mode")
PATH="/home/laguest/.local/share/Steam/steamapps/common/Proton 3.7 Beta/dist/bin/:/home/laguest/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/bin:/home/laguest/.local/share/Steam/ubuntu12_32/steam-runtime$
        TERM="xterm" \
        WINEDEBUG="-all" \
        WINEDLLPATH="/home/laguest/.local/share/Steam/steamapps/common/Proton 3.7 Beta/dist/lib64/wine:/home/laguest/.local/share/Steam/steamapps/common/Proton 3.7 Beta/dist/lib/wine" \
        LD_LIBRARY_PATH="/home/laguest/.local/share/Steam/steamapps/common/Proton 3.7 Beta/dist/lib64:/home/laguest/.local/share/Steam/steamapps/common/Proton 3.7 Beta/dist/lib:/home/laguest/.local/share/Steam$
        WINEPREFIX="/home/laguest/.local/share/Steam/steamapps/compatdata/221680/pfx/" \
        SteamGameId="221680" \
        SteamAppId="221680" \
        WINEDLLOVERRIDES="d3d11=" \
        STEAM_COMPAT_CLIENT_INSTALL_PATH="/home/laguest/.local/share/Steam" \
        strace "/home/laguest/.local/share/Steam/steamapps/common/Proton 3.7 Beta/dist/bin//wine64" "${@:-${DEF_CMD[@]}}"

[Lucretia]

After some testing, I'm getting errors related to encryption, namely, bcrypt in wine and the Steamrt gnutls library, gives the following errors, full log in link:

"GnuTLS does not support algorithm 11" and "GnuTLS does not support algorithm 10"

This seems to be sending data over the internet, thus failing and not being able to start.

Steam has an old version of gnutls installed, I think this library needs updating to >3 to get this to work.

$ find  ~/.local/share/Steam/ -name libgnutls.so.* -print
/home/laguest/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libgnutls.so.26
/home/laguest/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libgnutls.so.26.21.8
/home/laguest/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libgnutls.so.26
/home/laguest/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libgnutls.so.26.21.8

[Lucretia]

Anyone know how I can get libgnutls30 installed in a test env/rt with steam? Or if I can run steam using my system libs?

[Dehir]

Well should not the steam client itself to be build against it to make features in 3.0 to work. Tried to launch by copying gnutls from /usr/lib ** 32 and 64 bit in their proper directory and renamed to .26.21 etc.. Kept erroring as before. Thou didnt run any bugtracking to make sure those libraries were initialized.

Atleast in arch-linux you get gnutls 3.5.19-1from core build.

[madrang]

Hi, it seems Proton expects a libgnutls.so.26, and not a libgnutls.so. I was able to remove all gnutls warnings symlinking /usr/lib{32,}/libgnutls.so to /usr/lib{32,}/libgnutls.so.26, even it being the 3.5 version of the library, and running Steam with runtime off (see #74). It didn't help run the game I was trying to run, but it did fix gnutls errors. https://github.com/ValveSoftware/Proton/issues/162#issuecomment-416427322

[lucasmr]

Just adding that this game is runnable on Wine, reported as Platinum in version 2.7:

https://appdb.winehq.org/objectManager.php?sClass=version&iId=29333

Looking forward to running this with Proton!

[leal-alvaro]

As far as I know, although this game is runnable on Linux with Wine, there are some issues:

• You have to set Win32UltraLowLatencyMode=0 in Rocksmith.ini, which causes bigger latency in input (guitar) than in Windows. For some users, the latency is bearable, and for some users it is not.
• You also have to set ExclusiveMode=0 in Rocksmith.ini, which further impacts audio input performance.
• Apparently, the game only recognizes the official guitar USB adapter (RealTone cable) in some distros (or Wine versions?). Then some users managed to bypass the official adapter completely and use any sound input connected to the guitar, but that involves cracking the game, which isn't exactly ideal.

So, if anyone is working to make this game work with Proton, please have a look at these issues as well. Thanks.

[torvitas]

as a workaround you can use the flatpak of steam, at least I was able to start the game that way, although it crashed after login...

[kisak-valve]

Rocksmith 2014 (Remastered) (221680) Crash after login

Issue transferred from https://github.com/ValveSoftware/Proton/issues/1708. @torvitas posted on 2018-10-08T17:07:57:

Compatibility Report

• Name of the game with compatibility issues: Rocksmith 2014 (Remastered)
• Steam AppID of the game: 221680

System Information

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Desktop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz
    CPU Family:  0x6
    CPU Model:  0x4f
    CPU Stepping:  0x1
    CPU Type:  0x0
    Speed:  3800 Mhz
    12 logical processors
    6 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    Linux 4.x (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.17.19-200.fc28.x86_64
    X Server Vendor:  Fedora Project
    X Server Release:  11906000
    X Window Manager:  GNOME Shell
    Steam Runtime Version:  steam-runtime-beta-release_2018-09-03

Video Card:
    Driver:  X.Org AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.25.0, 4.17.19-200.fc28.x86_64, LLVM 6.0.1)
    Driver Version:  4.4 (Compatibility Profile) Mesa 18.2.1
    OpenGL Version: 4.4
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 59 Hz
    VendorID:  0x1002
    DeviceID:  0x67df
    Revision Not Detected
    Number of Monitors:  3
    Number of Logical Video Cards:  1
    Primary Display Resolution:  2560 x 1440
    Desktop Resolution: 3610 x 2384
    Primary Display Size: 23.50" x 13.23" (26.97" diag)
                                            59.7cm x 33.6cm (68.5cm diag)
    Primary VRAM: 8192 MB

Sound card:
    Audio device: Realtek ALC1150

Memory:
    RAM:  64397 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_GB.UTF-8
    Total Hard Disk Space Available:  293135 Mb
    Largest Free Hard Disk Block:  28408 Mb
    VR Headset: None detected

Recent Failure Reports:

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.

Logs: where do I find the logs if I use flatpak?

Symptoms

After working around #812 (lib issues) by using flatpak the game crashes after logging in. (only happens if credentials are correct)

Reproduction

Start rocksmith, enter valid credentials, wait for about 10 seconds (depending on ubisoft servers I guess), see the game vanish.

[torvitas]

steam-221680.log

[Lucretia]

As far as I know, although this game is runnable on Linux with Wine, there are some issues:

I would just like to point out that Steam/Proton != Linux/Wine, there are differences in libraries. Like I posted here already, this is, I'm pretty sure, an issue with the libgnutls version available with Steam. It may also be an issue with other libs.

[pszypowicz]

It's running for me though. Steam installed via flatpak.

The game itself does not recognize Real Tone cable, I have no luck with that so far.

The question is, may the flatpak block the access to device, how enable steam build to access it?

[pycebs]

I installed steam via flatpak and I can start the game. It feels responsive and the menus have no lag/delay. I can start a song and it plays, but as soon as the first notes appear the games becomes a bit choppy. Also the Real Tone cable isn't recognized by Rocksmith even though "lsusb" shows that it's recognized by my Linux distribution.

So two questions:

1. Why does it get choppy once the notes appear?
2. How can we get the Real Tone cable to be recognized?

And for question 2:

• Does flatpak "block" access to the USB cable?
• Does Proton even have USB support?
• Is there anything that can be done by the creators of Rocksmith to help with this?

I'll look into it more and then update this post accordingly.

[TheSurak]

To me, I start the game, then soon after, it shows up an error message "Sorry, something went wrong, for solutions, please visit:" with a link to support.coldfusion.technology. If I click "retry", it goes back to the same pop-up. If I click "Next", it briefly shows another pop-up message then terminates.

[odinu]

@TheSurak I am getting the same error. I tried both steam-native and steam-runtime. No flatpack though. I know someone who got it 100% running but says he doesn't remember what he did. If someone makes it work please post how you did it.

[romanstingler]

It always depends when it was running. There were a lot of updates to steam client and also uplay since launch.

[pycebs]

@TheSurak and @dncrash You need to be using the flatpak version. It's much easier than the repo version anyway because you don't need to activate the multilib repository. (Which is why I initially installed it via flatpak)

It runs just fine this way. The only problem that remains is getting the USB cable to work.

[torvitas]

If I enter the game without logging in to ubisoft it somehow works (realtone cable not yet tested) - but as soon as I log in the game crashes away.

[torvitas]

maybe another libgnutls problem? @kisak-valve

fixme:bcrypt:key_asymmetric_verify GnuTLS does not support algorithm 11 with hash len 48
fixme:crypt:verify_signature_bcrypt Failed to verify signature: c0000002

[Lucretia]

@torvitas Yes it is. If they can update mesa and sdl, they can update this library.

[Meelo]

@Lucretia, is this still relevant with Proton 3.16? For me it has been working since I selected 3.16 and at least two other users have been able to get it working with 3.16.

edit: was supposed to add this link: https://www.protondb.com/app/221680

[Lucretia]

@Meelo have they updated the libgnutls to 3? If not, then yes, it's still relevant. Even if they upgrade t 3, there could still be missing algorithms that RS uses.

[Meelo]

I've been playing it via Proton 3.16 on daily basis for over 3 weeks now. Definitely is launchable and playable (with both real tone cable and my amp working as an input device). It actually runs better than with just wine, where the game crashed after 10 minutes of Score Attack.

My point is, give it another go with the latest Proton to see if the bug report is still relevant.

[Lucretia]

Still doesn't launch here. I've no clue how it's launching for others if you are all using the libraries/runtime that comes with steam and not a system libs?

[torvitas]

I've been playing it via Proton 3.16 on daily basis for over 3 weeks now. Definitely is launchable and playable (with both real tone cable and my amp working as an input device). It actually runs better than with just wine, where the game crashed after 10 minutes of Score Attack.

My point is, give it another go with the latest Proton to see if the bug report is still relevant.

Hi @Meelo , would you mind giving a little bit more information about your system than that you are using proton 3.16? (Distribution, GPU, GPU-Driver, flatpak?, etc)

[Meelo]

Naturally: sysinfo.txt 64bit gentoo distribution, steam is installed from Anyc's steam overlay repository, using instructions found from here: https://wiki.gentoo.org/wiki/Steam

The only thing I had to do to make Rocksmith 2014 launchable was to accept beta-testing from:

• Steam Settings -> Account -> Beta Participation AND
• Steam Settings -> Steam Play -> Enable Steam Play for all titles
• Use this tool instead of game-specific selection: Proton 3.16.x-Beta This however had one trick to do. Instead of accepting steam's request to restart itself, you had to reject that and restart steam client manually, otherwise it didn't actually change the beta client setting.

The game was launchable, but not playable. Yet. I still needed to apply the same couple of fixes that are necessary with pure Wine-version. Change sound driver from pulse to alsa and fix the Rocksmith.ini config file

WINEPREFIX="~/.local/share/Steam/steamapps/compatdata/221680/pfx winetricks sound=alsa
sed -e 's:\(Win32UltraLowLatencyMode\)=1:\1=0:g' -e 's:\(ExclusiveMode\)=1:\1=0:g' -i ~/.local/share/Steam/steamapps/common/Rocksmith2014/Rocksmith.ini

Any other info that might be helpful?

ps. I also tested this with fresh debian install after I got my own system working (no system information available). Probably followed these instructions: https://wiki.debian.org/Steam The machine had intel i7 cpu and NVIDIA gfx card, but I can't remember what they were. It was a machine I had available for some repairs before taking it back to its owner. Took same exact steps as I did with my own gentoo machine and it worked.

[torvitas]

Thanks @Meelo ! Looks like there's a missing quotation mark in the suggested command.

On Fedora 29 I was able to launch Rocksmith by changing drive Z: to ~/.local/share/Steam

WINEPREFIX=~/.local/share/Steam/steamapps/compatdata/221680/pfx/ winecfg

The Realtone-Cable still doesn't work, but it looks like - although Rocksmith writes its configuration to the Rocksmith.ini when changing it in game, it completely ignores what ever I write into it (in game options do not change to the value I put into the file manually - I did restart the game in between).

Also, I am still unable to login. Everytime I login using valid credentials the game just crashes away. To bypass this I have to go to the login form, click on cancel and on the following dialogue also on cancel. This takes me to the profile selection from where I can enter the game in off line mode.

[Meelo]

:woman_facepalming:

I've pasted an invalid command to like four different places so far, you are the first one to mention there is a syntax error :D

Anywas, use find to see if there is a competing "Rocksmith.ini" somewhere in your system, which might get chosen by the Rocksmith.

[torvitas]

The last missing bit to make the realtone cable work was to use regedit to set the string value key Audio in HKEY_CURRENT_USER\Software\Wine\Drivers to alsa. After doing this the guitar started to work but also the sound started to crackle. This also went away after changing the default-sample-rate in /etc/pulse/daemon.conf from 44100 to 48000, followed by restarting pulseaudio (pulseaudio --kill; pulseaudio --start).

Although I still cannot login, I can at least start using the game.

[Meelo]

You had winetricks installed, right? The incorrectly written command was supposed to take care of that regedit hassle. WINEPREFIX=~/.local/share/Steam/steamapps/compatdata/221680/pfx winetricks sound=alsa

[torvitas]

For me this results in:

Unknown arg sound=alsa

Which version of winetricks do you use?

20180603 - sha256sum: cad4e699f55c297afe5b177d68dccf1ef54e9dd23518a6f6343caa0ab7636615

[Meelo]

20180815-next - sha256sum: 0d05e5b5312f7f7ae0a6e692f8cbcb12f08c29cb0cd10309b8253977bd645b6c

[Meelo]

This seems to be valid after Steam had a failure of an update on 5th of february. First the game got removed from all steam users. After that was resolved, the game no longer launches with Proton 3.16.6. All I get is a "something went wrong" popup that fails to display any relevant information.

Should not be libgnutls.so anymore.

$ find  ~/.local/share/Steam/ -name libgnutls.so.* -print
/home/milo/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libgnutls.so.26.21.8
/home/milo/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libgnutls.so.30
/home/milo/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libgnutls.so.26
/home/milo/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libgnutls.so.30.6.2
/home/milo/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libgnutls.so.26.21.8
/home/milo/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libgnutls.so.30
/home/milo/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libgnutls.so.26
/home/milo/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libgnutls.so.30.6.2

[bismurphy]

Any updates here? I can't get any tiniest bit of indication of anything working, just the window that says "Sorry, something went wrong, for solutions please visit:" and a useless link.

[Meelo]

Using 3.16-4 proton gives me this same result as wine versions 3.17 - 3.20 started giving after November's update. I made bug report about this to winehq https://bugs.winehq.org/show_bug.cgi?id=46131, which is a duplicate of https://bugs.winehq.org/show_bug.cgi?id=46142 The bug got fixed with wine 3.21. It's starting to look like we have to wait for proton-3.21 beta :/ (or play the game via wine)

Here is the result: crash stacktrace

[Meelo]

Using the beta version: 3.16-6 how ever gives a different error:

ERROR: ld.so: object '/home/milo/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
GameAction [AppID 221680, ActionID 1] : LaunchApp changed task to Completed with ""
/bin/sh: /home/milo/.local/share/Steam/steamapps/common/Rocksmith2014/Rocksmith2014.exe: cannot execute binary file: Exec format error
>>> Adding process 10626 for game ID 221680
Game removed: AppID 221680 "", ProcID 10625 

No idea how to work around that. It's trying to execute the binary as a shell script

[bismurphy]

As per ProtonDB (https://www.protondb.com/app/221680) it appears that most people can get the game to launch if they re-map Z: to the right place, otherwise Proton can't find the EXE. I was able to get it to launch by doing this. However, I'm unable to get it to detect the RealTone Cable. lsusb shows it. Some people have had success using "pavucontrol" to turn the cable off, but that isn't working for me.

[Meelo]

@tj-murphy Did you try winetricks sound=alsa? (the exact syntax is in one of the posts above)

[bismurphy]

@Meelo Yes. If I look at steamapps/compatdata/221680/pfx/winetricks.log, that file simply has two lines of text, both of which are "sound=alsa".

[Meelo]

how about the sound tab in? WINEPREFIX=~/.local/share/Steam/steamapps/compatdata/221680/pfx winecfg

[bismurphy]

I believe this is what you're requesting? At the top it says the selected driver is winealsa.

[Meelo]

That's definitely correct. Can you also paste your ~/.local/share/Steam/steamapps/common/Rocksmith2014/Rocksmith.ini

[Meelo]

Oh and since you got it running, could you show a screenshot of what your winecfg shows for drive mappings?

[bismurphy]

Rocksmith.ini.txt

[Meelo]

Other than having higher latency, and microphone enabled, that should be just fine, if you have disabled Rocksmith cable from pavucontrol.

[bismurphy]

Huh. Well, I guess one of the many changes I've done needed a reboot because now suddenly it's working! Strange. I'll change my latency to 1 and see if that improves things. Thanks!

[Meelo]

if you'll post that drive mapping section of winecfg of yours, perhaps I can get mine running again as :) I'm currently running it off bare wine, which crashes at score attack mode :/ Would prefer get it working via proton again.

[bismurphy]

I remapped my Z: to be /home/user/.steam/steam If you go into your Steam Library Folders, I believe the library folder path should be identical to your Z: path.