@kisak-valve Thank for the quick reply, here is the gist with my PC information. https://gist.github.com/pandymiku/319cf449c6b17b41c7de82ec3ca77832

I've never, ever been able to get UPlay working in Wine. Not proton, not ANY wine version. I've tried so many different winetricks, different uplay versions, Wine versions, etc. This is something that has just never worked for me.

Have you tried installing corefonts via winetricks to make Uplay launch?

@Progman-DT Yes. That's a winetricks package I always install. I've tried installing different combos of dotnet and such along with pretty much every Wine version from like 2 to 3.13-staging

It appears to be trying to preload a 64-bit DLL into a 32-bit program, which won't work. The error message is very deceptive though. I am not sure if that is what is fatal here though.

IIRC, the error I got every time when I tried to start Uplay was it couldn't find libcef (chromium dll), and some other super basic DLL. I tried downloading the actual DLLs online and placing them everywhere around the prefix. I placed it in sys32, the uplay dir, the game dir, etc. I also tried doing DLL overrides in winecfg but nothing I did could actually help Uplay find the DLL that was actually there

Hi,
i've the same problem.

Uplay crash dump:
upc.exe_29.0.0.5120_2018-09-02_18-44-57.zip

Debug log:
debug.zip

System infomation:
gist

Processes still runnung after the crash:

C:\windows\system32\services.exe
C:\windows\system32\winedevice.exe
C:\windows\system32\plugplay.exe
C:\windows\system32\winedevice.exe
C:\windows\system32\explorer.exe /desktop
C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\UbisoftGameLauncher.exe -gamelauncher_wait_handle 144 -upc_uplay_id 2916 -upc_game_version 1 -upc_exe_path WjpcaG9tZVxkaW1hXC52YXJcYXBwXGNvbS52YWx2ZXNvZnR3YXJlLlN0ZWFtXC5sb2NhbFxzaGFyZVxTdGVhbVxzdGVhbWFwcHNcY29tbW9uXEZvciBIb25vclxmb3Job25vci5leGU= -upc_working_directory WjpcaG9tZVxkaW1hXC52YXJcYXBwXGNvbS52YWx2ZXNvZnR3YXJlLlN0ZWFtXC5sb2NhbFxzaGFyZVxTdGVhbVxzdGVhbWFwcHNcY29tbW9uXEZvciBIb25vcg== -upc_arguments LXVwbGF5X3N0ZWFtX21vZGUgL3N0YXJ0ZWRCeVVwbGF5OlByb2QsMjkxNixMaXZlX0xJVkVQQw== -uplay_steam_mode /startedByUplay:Prod,2916,Live_LIVEPC
C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\upc.exe -upc_uplay_id 2916 -uplay_steam_mode /startedByUplay:Prod,2916,Live_LIVEPC
C:/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/UplayWebCore.exe --type=renderer --disable-gpu-compositing --enable-smooth-scrolling --no-sandbox --lang=en-US --lang=en-US --locales-dir-path=C:/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/locales/1/ --log-file=C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\debug.log --disable-spell-checking --enable-system-flash --device-scale-factor=1 --num-raster-threads=2 --content-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --video-image-texture-target=3553 --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=45.0.1599199454\1966901970 /prefetch:1
C:/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/UplayWebCore.exe --type=renderer --disable-gpu-compositing --enable-smooth-scrolling --no-sandbox --lang=en-US --lang=en-US --locales-dir-path=C:/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/locales/1/ --log-file=C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\debug.log --disable-spell-checking --enable-system-flash --device-scale-factor=1 --num-raster-threads=2 --content-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --video-image-texture-target=3553 --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --channel=45.1.1260361879\2037262790 /prefetch:1

My log file
steam-304390.log

#571
I've tried with corefonts and austin987's foss_corefonts and the error is still the same.

For honor open, but doesn't connect to the servers. I don't know why.
Proton version 4.2

I've not tried things myself yet, but connection problems could be related to how the game uses Easy Anti-Cheat.

Tested the game with Proton 4.2.3b.

Game launches, shows cinematic, but crashes to the desktop after reaching "Connecting to servers".
Probaly because of EAC.
After the crash I right clicked the uplay icon in the taskbar and clicked quit. (Providing this since there might be more log info about that)

System specs (neofetch, unnecessary stuff removed):

OS: Ubuntu 18.10 x86_64 
Kernel: 5.0.9-050009-generic 
Shell: bash 4.4.19 
DE: KDE 
WM: KWin 
CPU: Intel i7-6700K (8) @ 4.200GHz 
GPU: NVIDIA GeForce GTX 1070 (Driver: 418.56)
Memory: 5147MiB / 15978MiB 

Log file is 14 MB and has some difficulties when uploading as a Gist.

Steam system information is at the top of the file
PROTON_LOG=1 %command% log file: https://send.firefox.com/download/055e10d7bbacbe15/#nPbxSHv2SGBsDOVs0ynFFg

(If you'd rather have a different link, please tell me. I'm happy to provide it.)

Hey hum, the game is working for me until the "Press any button to continue" and then the screen is flickering like crazy and then crash... I'm pretty sure this is about the fullscreen mode i feel like Gnome is trying to keep it windowed... i didn't found the lauch option to force fullcreen off yet.

OS: LinuxKERNEL: 5.1.4-arch1-1-ARCHCPU: Intel Core i5-8600K @ 3.60GHzGPU: NVIDIA GeForce GTX 1060 6GBGPU DRIVER: NVIDIA 430.14RAM: 16 GB

With Proton 4.2-7 game not working,
Hardware Info: https://github.com/tele1/Steam.logs/blob/master/Hardware Info
Log: https://github.com/tele1/Steam.logs/blob/master/2019.06.12/For Honor.Crash.2019.06.12.with xboxdrv.steam-304390.log.zip

With

1. Jacek's threadsafe libx11 patches (https://aur.archlinux.org/packages/libx11-threadsafe/)
2. Wine staging patches
   and
3. My bcrypt patchset (https://www.winehq.org/pipermail/wine-devel/2020-January/157433.html)

For Honor seems to work, at-least the single-player portions; I haven't tested MP but I'm not hopeful given the game uses EAC.

Tried it with Lutris using lutris-5.0-rc5 which includes @Guy1524 's bcrypt patchset (I think, only said in the changelog "Added a new bcrypt patch to make Steep playable.") since lutris-5.0-rc4 and so far it works. Also installed Jacek's threadsafe libx11 patches. Indeed no MP, tried joining a match but got the error: 4000027 when getting in a lobby. This error seems to indicate "This error means that the connection between you and another player (or several players) could not be established.". So this is most likely EAC's doing.
Training matches and the arcade mode work fine I'd say, I was able to complete the weekly quest in arcade and mess around a bit in a training match. Presumably like Guy said, the single-player also works.

There are mouse issues when looking around. Guard mode seems to work fine with my limited testing.
Controller works fine, I get force feedback on the controller and can turn the camera smoothly.

Ran the benchmark a few times which went fine after some stutters at the first attempt. Ran around 100fps average on high or extreme settings with a i7-6700k, 16GB ram and a GTX 1070 with driver version 440.44 on Manjaro with the 5.3.18-1-MANJARO kernel. Ran in full screen mode with v-sync off and refresh rate set to 144hz. Not a very comprehensive test but if you'd like a full on benchmark, please tell me.
DXVK version 1.5.1 and Esync enabled.
Not sure if it's needed but in Lutris both nvapi and nvapi64 were both disabled in the DLL overrides.

So they included the EAC .so file but it still isn't working,... yet.

Singleplayer seems to work well (with dxvk-asnync and uplay overlay disabled) but multiplayer does not work and "NAT" is shown in red.

The game does create UPnP entries though.

This game did previously work well on singleplayer, but now that it appears Ubisoft have added the necessary .so files to enable EAC on Linux, people are coming back to play it and seeing that it doesn't seem to work as well as it did previously. My previously-working configuration no longer does, even on older versions of Proton it seems.

I have just finished a For Honor play session for me it continues to works fine. See: https://www.protondb.com/app/304390 and https://github.com/AreWeAntiCheatYet/AreWeAntiCheatYet/issues/1272
With Proton 8 currently on AMD Manjaro

It's possible there's an issue with Ubisoft servers that are causing the issue some are facing; it also doesn't seem to get past the initial loading screen on the Steam Deck despite previously working - the most recent Steam Deck post on ProtonDB predates the EAC files being added by Ubisoft.

See the same issue mentioned here.

I can confirm that the Ubisoft servers appear to have righted themselves now and the game works great on Linux desktop, but still does not progress past the loading screen for the Steam Deck any more.

I can confirm that the Ubisoft servers appear to have righted themselves now and the game works great on Linux desktop, but still does not progress past the loading screen for the Steam Deck any more.

Can you please share the setup that got the game working for you? Thanks in advance

I've had success with GE-Proton 7-55 and Experiential on desktop. Be sure to disable VSync when you get in game, though.

I put more details about my setup on my ProtonDB submission.

It works perfectly using Proton GE 8.4 and pointing to the EAC runtime location in the launch options. Just like native.

(Make sure to have installed in Steam the Proton EAC runtime before launching For Honor with this parameter)

PROTON_EAC_RUNTIME="/home/YourUsernameHere/.local/share/Steam/steamapps/common/Proton EasyAntiCheat Runtime/" %command% uplay://launch.569/0

I've been successfully running this game on my desktop with two tweaks:

1. Ubisoft Connect seems to have a poorly implemented network stack and cannot handle TCP mtu correctly under my network setup. It might be fine for other network conditions. On my end, I need to enable kernel TCP mtu probing by setting net.ipv4.tcp_mtu_probing = 1 in sysctl to avoid "Cannot connect to Ubisoft Services" errors.
2. Any sort of overlay other than Ubisoft Connect overlay will crash the game right before it enters the main menu. mangohud, steam overlay, anything will cause a crash. I need to disable everything else for it to work.

However, I cannot run the game on steam deck even with both of the tweaks. It will crash in the same way as the overlay crash - right before entering the main menu. Since steam deck enables mangohud by default, I strongly doubt that either I did not disable it correctly (I set DISABLE_MANGOHUD=1 and DISABLE_MANGOAPP=1 for now), or there is some other form of overlay/graphic API interceptions that are messing with it.

Any further clues/ideas on this would be very helpful.

Since the latest patch the game runs almost flawless as far as I can see. Only minor issues are that the game starts minimized (maybe Gnome focus issue?) and when alt-tabbing you have to click the window a few times otherwise it minimizes again (using Gnome). Other than that no performance, graphical or input related issues :)

Using Proton 8.0-3 worked fine for a while. But Ubisoft Connect introduced an issue. Switching to Proton Experimental solves this.

In my case works nice using PROTON_EAC_RUNTIME, but the anticheat must have a problem, because it kickme while i trying join to party

See the log files of anticheat in /home/user/Games/ubisoft-connect/drive_c/users/noe/AppData/Roaming/EasyAntiCheat

loader.log:

[2023.12.04-17.58.18] Progreso de la descarga: 0%.
[2023.12.04-17.58.18] [Connection] Connect result: No error (0) Response Code: 200 Destination IP: 172.67.****
[2023.12.04-17.58.18] Código de respuesta HTTP: 200 Código curl: 0
[2023.12.04-17.58.18] [EAC Callback] Code 915. Message: 'Código de respuesta HTTP: 200 Código curl: 0'.

gamelauncher.log:

[Info] [LauncherProgress] 0%.
[Info] [LauncherProgress] 0%.
[Info] [LauncherProgress] 0%.
[Info] [LauncherFinished] EACAsyncResult: 0 Message: 'Se ha cargado con éxito Easy Anti-Cheat en el juego'.
[Info] Unloading the EasyAntiCheat library.
[Info] Destroying windows.
[Info] Exit.

for try solved it, i would do WINEPREFIX=/home/user/Games/ubisoft-connect winetricks hidewineexports=enable, and then all load to 100% but the game crashes at start, and born a new bug EACAsyncResult: 4 Message: 'StartService failed with 1053.'.

By this reason i must keep it in hidewineexports=disable

what could be a solution? I've tried many things, but the game (easy anticheat sure) always kick me when try join in a multiplayer party.

gamelauncher.log
loader.log

So trying via Lutris, with the Ubisoft Connect Launcher, (having tried using Proton GE 9-11 / Experimental, and Wine-GE 8-26) I can get the game to launch regardless of arguments (WINEPREFIX, PROTON_EAC_RUNTIME, etc) documented above.

However, I have tried using them all, isolated and together, but still I end up with the same issue as @Milor123 above, unable to connect to multiplayer, it's easy to suspect that there's an issue with EAC running for the Ubisoft connect version, wondering if anyone else has had any better luck figuring this out.

Using Lutris with umu-launcher (GE-Proton) trying to play my copy of For Honor in Uplay via Ubiconnect.
I have experienced the same issue as @Milor123 and @Aracnoss above.

Everytime I tried to join multiplayer match, it end up with message "Failed to join session" and will show Error Window ' EasyAntiCheat: "Missing required file (lmath-2_2.dll)" (0006000143) v70.554 ' . After that I got penalty 15 minutes wait time from the game to join multiplayer match again.
Wondering if anyone know how to fix it. This is not a game, without multiplayer working on linux PC.

EDIT: I have another copy of For Honor game Steam version that I got for free years ago. Today, I install it using Steam with Proton Experimental, launch it and tried multiplayer and it works.

So I browsed the Steam version of For Honor folder and I found the missing dll. I copied lmath-2_2.dll and steam_api64.dll from the steam version folder to ubisoft connect folder. Now I can play multiplayer on Uplay (ubisoft connect) version using Lutris + umu_launcher (GE_Proton).

@ThankyouLinusTorvalds could you share this two files with me? Also did you make any other changes like custom arguments? Having exact same problem as you did.
EDIT:
got files from a friend, but after copying steam_api64.dll game wont start normally, im trying to use umu-launcher but after ubisoft connects start it ask me for activation key

EDIT2:
i managed to start ubisoft connect with argument "uplay://launch.569/0" but game wont start either, @ThankyouLinusTorvalds pls help me man, im desperate XD

Not trying to necro, but it seems Ubisoft has updated this game and temporarily killed the game on Linux in their latest patch. What seems peculiar is the "libEOSSDK-Linux-Shipping.so" addition and "eos.exe" to the repo. Seems like there's a new method of anticheat enforcement.

Game takes forever to launch, about 10 minutes but works flawlessly ingame with proton experimental

• CPU Brand: 13th Gen Intel(R) Core(TM) i5-13600KF
• "CachyOS" (64 bit) 6.16.8-2-cachyos
• NVIDIA Corporation NVIDIA GeForce RTX 4070
• G.Skill Flare X5 F5-5600J3636C16GX2-FX5 2x16GB

@Fyuran can you check if proton experimental bleeding edge makes a difference for you? https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge

@Fyuran can you check if proton experimental bleeding edge makes a difference for you? https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge

No luck, still does the same thing, game is on a nvme that is partitioned in 3 where 2 are windows partitions and the last one has cachyos

@Fyuran is the game on a ntfs partition? if so, can you try on a partition with a different format(ext4,xfs,etc)?

@SCP-155 have you tried to use bleeding edge? https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge

@SCP-155 have you tried to use bleeding edge? https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge

@simifor Yes. Just tried it with bleeding edge. No difference. Still takes that long to start.

@Fyuran is the game on a ntfs partition? if so, can you try on a partition with a different format(ext4,xfs,etc)?

Performs the same on a btrfs, ext4 and ntfs3 format

@Fyuran @SCP-155 can you share the dmeg log after running the game?
Run this on your terminal sudo dmesg > dmesg.log, this will create a dmesg.log file in your home folder, upload it here

@simifor As requested, dmesg AFTER running For Honor
dmesg.log

@Fyuran Please wipe the game's prefix, add PROTON_LOG=1 %command% to the game's launch parameter and launch the game twice (first time it'll be installing dependencies and whatnot), then upload the resulting log file that'll be in your home folder as steam-304390.log, you might need to zip it if it's too big.

Ok i'll have to add SteamDeck=1 too as i had to revert to Proton Experimental stable, latest bleeding edge's update crashes the game

@simifor
Had to use SteamDeck=1 also, otherwise game crashes with "Failed to start Ubisoft Connect" after splash screen.
Here is the dmesg.log after game was running and also the proton log.

steam-304390.log
dmesg-after-game-start.log

Steam log on a fresh prefix, from start up to the game actually running

steam-304390.log

@SCP-155 @Fyuran as you are both on cachyos, have you looked into split lock detection? https://wiki.cachyos.org/configuration/general_system_tweaks/#disabling-split-lock-mitigate

@SCP-155 @Fyuran as you are both on cachyos, have you looked into split lock detection? https://wiki.cachyos.org/configuration/general_system_tweaks/#disabling-split-lock-mitigate

Tried, no difference

@simifor @SCP-155 further testing by disabling split lock mitigation has succesfully increased game startup speed

@Fyuran I should have been clearer. The split lock mitigation is the default behavior and it's there to throttle programs the kernel considers abusive in the way they use resources, by disabling the mitigation you disable the throttling which was affecting you in this game.

You were clear enough i just was too hasty in my judgment

I'm currently having an issue with Uplay crashing on startup without fail everytime. I'm not sure what the issue could be, I've tried changing proton versions. (CachyOS, GE, 9, 8, Experimental, TKG, etc.) and had zero luck.
I've deleted the proton prefix, manually installed Uplay, changed from wine-git, mesa-git to stable, deleting and reinstalling the game and still no luck. Heres my Proton log if anyone's able to help.
Running CachyOS with a 7900 XTX & 5950x, I also only have SteamDeck=1 in my launch options too.
steam-304390.log

EDIT: Downgrading to Kernel 6.16 Seemed to of fix the issue, seems to be some sort of regression with the 6.17+ kernels.