Conan Exiles crashes after their recent update. Both server and client.
System Info
Log:
steam-440900.log
Conan Exiles does not work with 5.13
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4447.
@ThomasLocke posted on 2020-12-08T17:19:17:
You can start the game, but not actually play the game. Trying to either start a new singleplayer game or continue an existing one results in the game hanging at a load screen.
This only happens with 5.13-x whereas 5.0-10 works fine.
Start the game and then attempt to actually play a singleplayer game.
https://gist.github.com/ThomasLocke/94e2890ddd5ba2de6842c550630d14f7
A quick update to my previous post: Just tested 5.13-4 and it does not work either. Fails the same way as all the previous 5.13-x releases.
Just checking in on this one, and reporting that 5.13-5 also fails the same way as the previous 5.13-x releases.
It is worth noting that there are a couple of reports at https://www.protondb.com/app/440900 claiming that 5.13-4 works. One of them is using Ubuntu 20.04.1. I'm on Ubuntu 18.04, so maybe this is just some library somewhere that needs and update?
Got a 7.5MB proton download via steam this morning, and now 5.13-5 works! I can both start the game, and enter a single player instance.
@kisak-valve feel free to close this issue. After a 2 hour play session playing online with friends, it seems to work great. I only had one crash, which feels about in line with 5.0-10. Awesome! :+1:
The BattlEye does not work it fails to install driver load error 31. It pushes me to unofficial.
steam-440900.log
https://gist.github.com/ioannis120/c664f015742641d8441b0f4fdddf985b
Proton:Experimental
Just as a general note the Funcom Launcher that was just added is causing issues for me.
I had a log, but didn't keep it. I'll get another one soon.
For a dirty workaround I added ~/.local/share/Steam/steamapps/common/Conan Exiles/ConanSandbox/Binaries/Win64/ConanSandbox.exe as an external program, and launch that instead, which seems to bypass the Launcher and runs the game fine...
I'm sure there are better ways though.
EDIT: So after some messing the only way I can get the Launcher to work is if I use PROTON_LOG=1 %command% otherwise it crashes...
I can confirm the regression mentioned by @HanFox - the game will not start at all now. I've tried both 5.0-10 and 5.13-6
It now gives me Funcom and it does not start
Proton experimental
steam-440900.log
https://gist.github.com/ioannis120
6.3-1 does not work either. Game won't start.
Can confirm, does not start with Proton 6.3-4. Seems to be a problem with the Funcom Launcher.
Symptoms: Does not run with Proton 6.3-4
Additional steps
Note: I deleted the prefix everytime I switched the Proton Version
Actually working work around
Bypassing the Funcom launcher: https://pastebin.com/8b5X7bm3
(not my work)
I don't understand what's happening. Today I tried to run the game, it wasn't working besides the newer proton version indicating it now runs. However, and here's the fun thing... If you put PROTON_LOG=1 %command% in the launch settings it works, which makes no sense because we should just get logs, but it makes the game work. Any idea about why could this be?
Replying to https://github.com/ValveSoftware/Proton/issues/2563#issuecomment-869162591
Odd, It works perfectly in Arch, but not on Fedora. What distro are you running?
Replying to https://github.com/ValveSoftware/Proton/issues/2563#issuecomment-874068352
Pop OS. I don't understand it, because it runs perfectly, but you must enable logs to make it run, it has no sense xD
Replying to https://github.com/ValveSoftware/Proton/issues/2563#issuecomment-874124985
Are you on Nvidia or AMD, if AMD are you using AMDVLK driver or Mesa?
Replying to https://github.com/ValveSoftware/Proton/issues/2563#issuecomment-874238185
I'm using Nvidia :)
It's working fine for me on my NVIDIA RTX 2070 Super but won't start on my other PC with a AMD RX470.
It will start with the AMD card on that PC if I start the game directly. Be it through wine or proton. But I always get the message "Steam services are no responding". Can't play in either single or multiplayer due to that trash message. Seems to be a reasonable candidate for downloading a ... less restrictive version of the game if you ask me.
BattlEye will give some cryptic message "Failed to install driver load error 31." See above.
Anti cheat really only serves one purpose... to make honest customers mad.
Conan Exiles Crash
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5217.
@LiSiaoCheng posted on 2021-10-12T02:49:43:
Game exits when trying to start. There is no error message, game simply quits before showing anything.
@LiSiaoCheng commented on 2021-10-12T03:36:12:
Add scripts 'PROTON_LOG=1 %command%' to the game's launch options, now Conan Exiles can be Launched.but I'm not sure it can play smoothly, and the BattlEye still can not install on Linux based Operate System,i have nothing to do but disable BattlEye,also I'am not sure all games that users have to add scripts 'PROTON_ENABLE_NVAPI=1' to support Nvidia's NVAPI GPU library and DLSS, and scripts 'PROTON_LOG=1 %command%' to avoid game crashing ,and the scripts can not be save like steam cloud,maybe Valve can do something like set-default or release some patch for games.There is not everyone can know visiting the right website and say:"help me",hoping we have better solution.
For a while I was able to play on servers with BattlEye enabled using the Proton BattlEye Runtime. I'm not sure what changed but it doesn't work anymore. Even with Proton BattlEye Runtime uninstalled the game doesn't even open anymore when BattlEye is enabled.
For a while I was able to play on servers with BattlEye enabled using the Proton BattlEye Runtime. I'm not sure what changed but it doesn't work anymore. Even with Proton BattlEye Runtime uninstalled the game doesn't even open anymore when BattlEye is enabled.
Hi ZephaniahNoah ,
That was a problem because of Battleye itself,Battleye cannot support Linux distribution as useless as NVIDIA
Another problem:Newer Proton Version( Experimental, 7.x, etc)may not support Conan Exiles
pls try:
#1 worked.
Proton 6.3-8 and 6.21-GE-2 work fine with BattlEye. Thanks for the help!
OK, so after an extensive amount of testing I've determined the only version of proton that works for me long(er) term is the 6.3-8c. Using the latest proton including experimental will work on a fresh game, or when creating a new character. But long term (save the game a bunch, build things, etc) on my machine you end up being unable to load your game. It will hang on the second "pass" of the loading screen. I will attempt to reproduce again (work backwards a bit) and get both proton logs for comparison purposes.
Working Proton:
https://paste.gloriouseggroll.tv/?d84d4c06d67aa7c1#DrQjsMmXe1WJb2X2Lvx2Xiuq3bzB6FbrdAA4tumtD3Mo
Later, not working proton:
https://paste.gloriouseggroll.tv/?46ce7cf8e356395a#BJqboZQrEEU9QPWi6SATd5QieW4H3aD1EZwCkVdMfC6e
In addition, because I really feel this is important - if you use GE to skip the launcher it does a great job of it - and the game, when it runs, runs better here than anywhere else... BUT, that being said, it has a problem still with loading a game that has gotten of size that the 6.3 version can still load.
https://paste.gloriouseggroll.tv/?2e09f418e17f3f0c#8GXMmW3pdoguwGKxqMARgTHu5MLCmx3bZMPsoA8Qu1GM
Conan was working for me under 6.3 until this morning. I tried loading the game but it keeps crashing with the error "DX11 feature level 10.0 is required to run the engine."
Here's the gist
https://gist.github.com/ltsjoe/3d1f9eacf19b2ec79fb1c865f6aa36b8
Hello @ltsjoe, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
Hello @ltsjoe, please copy your system information from Steam (
Steam->Help->System Information) and put it in a gist, then include a link to the gist in this issue report.
Done.
Looking at your system information, Vulkan is broken in general on your system (https://gist.github.com/ltsjoe/3d1f9eacf19b2ec79fb1c865f6aa36b8#file-steam_systeminformation-txt-L370-L383 and https://gist.github.com/ltsjoe/3d1f9eacf19b2ec79fb1c865f6aa36b8#file-steam_systeminformation-txt-L734-L748)
Most likely an AMDVLK issue.
Odd. I wonder what broke that. Thanks for pointing that out. I had been using AMD_VULKAN_ICD=RADV in the Launch Options, but that doesn't seem to be loading Vulkan anymore. Adding VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json seems to have fixed it.
Had to add PROTON_LOG=1 %command% to launch. As stated above, this was strange and I tried every combination of GE. Working however.
Right now game does not work. In best case I can open launcher, but when I press "Launch" it disappears and nothing happens. Log: steam-440900.log
With launch options:
gamemoderun $(eval $(echo "PROTON_LOG=1 %command%" | sed -E "s~/Launcher/FuncomLauncher.exe'~/ConanSandbox/Binaries/Win64/ConanSandbox.exe'~g"))
I can bypass launcher, but then game crashes after I start single player. Log: steam-440900.log
I tested with proton 8.0-2. With other versions can't even start the game.
Conan Exiles (440900) Accented keys not working on AZERTY keyboard
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7223.
@Nyalnara posted on 2023-11-01T14:15:33:
In Conan Exiles (appid: 440900), accented keys of an azerty keyboard are not recognized, regardless of the actual keymap that is set.
I couldn't set the é and è as keybinds for the hotbar, they're not recognized.
Borrowed a keybinds file from a friend running the game on Windows, the keybinds are properly shown on the hotbar but when you press them, they're not recognized.
Full system hardware, but it probably doesn't matter. Could reproduce with several different keyboards, all from different manufacturers.
Problem present with the following proton versions:
I didn't try older versions of Steam supplied proton, but as I did find a 2 years old reddit thread about this exact issue, I would assume older versions are impacted too.
I would provide a full wine log, but the one generated when using PROTON_LOG=1 %command% as launch options doesn't show anything useful. I will definitely provide the log if provided with correct launch options.
Hello, Conan Exiles seems to be broken again since the latest patch.
The Funcum Luncher works, but the game binary just crashes on startup.
So far what I could gather, some weirdness happening with file descriptors in winsock.h.
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
I've tried multiple proton versions and the latest ge, but same error.
Here's my system info.
Here's the proton log with proton experimental: log
@fwind4 Just in case you really want to play Conan Exiles over the holidays, I can report that it works with GE-Proton8-25. :)
Thanks for the update @ThomasLocke, sadly it doesn't work with GE-Proton8-25 either, for me, I guess this confirms there's something wrong on my system specifically, not a general issue.
Happy holidays. :)
@fwind4 for what it is worth, we have pretty much the same specs. I have a 5600X CPU, a RX 6700 XT and 32GB RAM.
The biggest difference is my kernel is 6.2.0-39 and my driver version is 23.3.1. So an older kernel and bit newer Mesa.
Maybe a Mesa update will fix it? I'm using the kisak-mesa PPA for Ubuntu. Maybe there's something similar for Manjaro?
game stopped working for me. it was working fine the past week, but now all of a sudden it won't launch anymore. i tried proton-ge and experimental. i made sure to even delete my compdata folder too. i also tried the regular arch linux kernel, linux-mainline from the aur, and the nobara kernel from the aur. i even tried the official amd closed source vulkan drivers. game just won't launch. i also verified its file as well.
i went ahead and uninstalled conan exiles completely. currently in the process of reinstalling it.
steam-440900.log
i reinstalled the game. still fails to launch. i uploaded my proton-log.
Game stopped working for me too now. I'm on Ubuntu 22.04.3. Worked fine a couple of days ago, doesn't work today. I've tried all ge-proton versions from 8-9 to 8-27. I click the Play button, it switches to launching, then stop and a few seconds later back to play.
With experimental I get the launcher, but the game still wont play.
With an old ge-proton 7-55 I get the small Conan Exiles "splashscreen", then black screen and then a UE4 engine crash popup.
Some extra info: My wife and I have the exact same machines. Same hardware, same OS, same everything. While I was sitting here struggling with Conan Exiles, she clicked play and it just worked. This with ge-proton 8-25.
The difference: She was running an older Steam version, because hers had not been turned off. We exited her Steam, and started it again. Steam updated itself to the latest version, and now she too can no longer play Conan Exiles. It crashes just like mine.
So for some odd reason, this might be somehow connected to the latest Steam update. At least that's what it seems like from here.
ProtonFixes[41618] INFO: Running protonfixes
ProtonFixes[41618] INFO: Running checks
ProtonFixes[41618] INFO: All checks successful
ProtonFixes[41618] INFO: Using global defaults for "Conan Exiles" (440900)
ProtonFixes[41618] INFO: Using protonfix for "Conan Exiles" (440900)
ProtonFixes[41618] INFO: Changing FuncomLauncher.exe to ../ConanSandbox/Binaries/Win64/ConanSandbox.exe
ProtonFixes[41618] INFO: Adding argument -BattlEye
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Setting breakpad minidump AppID = 440900
Steam_SetMinidumpSteamID: Caching Steam ID: 76561197974032443 [API loaded no]
LogPakFile:Warning: Spent 0.158 seconds mounting Pak File "../../../ConanSandbox/Content/Paks/Sound.pak". Mounting status: Success
LogOnline:Display: STEAM: Loading Steam SDK 1.57
Setting breakpad minidump AppID = 440900
SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197974032443 [API loaded no]
CAppInfoCacheReadFromDiskThread took 6 milliseconds to initialize
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no]
*** buffer overflow detected ***: terminated
steam.sh[11040]: Running Steam on arch rolling 64-bit
steam.sh[11040]: STEAM_RUNTIME is enabled automatically
setup.sh[11108]: Steam runtime environment up-to-date!
steam.sh[11040]: Steam client's requirements are satisfied
tid(11160) burning pthread_key_t == 0 so we never use it
[2024-01-13 09:16:48] Startup - updater built Jan 13 2024 00:51:43
[2024-01-13 09:16:48] Startup - Steam Client launched with: '/home/agent/.local/share/Steam/ubuntu12_32/steam'
01/13 09:16:48 Init: Installing breakpad exception handler for appid(steam)/version(1705108172)/tid(11160)
[2024-01-13 09:16:48] Loading cached metrics from disk (/home/agent/.local/share/Steam/package/steam_client_metrics.bin)
[2024-01-13 09:16:48] Using the following download hosts for Public, Realm steamglobal
[2024-01-13 09:16:48] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2024-01-13 09:16:48] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2024-01-13 09:16:48] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2024-01-13 09:16:48] Verifying installation...
[2024-01-13 09:16:49] Verification complete
Steam logging initialized: directory: /home/agent/.local/share/Steam/logs
XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xeba30dc0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xeba2f500
steamwebhelper.sh[11193]: Runtime for steamwebhelper: defaulting to /home/agent/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[11193]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()
CAppInfoCacheReadFromDiskThread took 52 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 11388
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
BRefreshApplicationsInLibrary 1: 1ms
BuildCompleteAppOverviewChange: 540 apps
RegisterForAppOverview 1: 19ms
RegisterForAppOverview 2: 20ms
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
/bin/sh\0-c\0/home/agent/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=440900 -- /home/agent/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/mnt/storage1/files/SteamLibrary/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/agent/.local/share/Steam/compatibilitytools.d/GE-Proton8-27'/proton waitforexitandrun '/mnt/storage0/files/SteamLibrary/steamapps/common/Conan Exiles/Launcher/FuncomLauncher.exe'\0
chdir "/mnt/storage0/files/SteamLibrary/steamapps/common/Conan Exiles"
ERROR: ld.so: object '/home/agent/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/agent/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/agent/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/agent/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/agent/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ProtonFixes[12928] INFO: Running protonfixes
ProtonFixes[12928] INFO: Running checks
ProtonFixes[12928] INFO: All checks successful
ProtonFixes[12928] INFO: Using global defaults for "Conan Exiles" (440900)
ProtonFixes[12928] INFO: Using protonfix for "Conan Exiles" (440900)
ProtonFixes[12928] INFO: Changing FuncomLauncher.exe to ../ConanSandbox/Binaries/Win64/ConanSandbox.exe
ProtonFixes[12928] INFO: Adding argument -BattlEye
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Setting breakpad minidump AppID = 440900
Steam_SetMinidumpSteamID: Caching Steam ID: 76561197987159849 [API loaded no]
LogPakFile:Warning: Spent 0.137 seconds mounting Pak File "../../../ConanSandbox/Content/Paks/Sound.pak". Mounting status: Success
LogOnline:Display: STEAM: Loading Steam SDK 1.57
Setting breakpad minidump AppID = 440900
SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197987159849 [API loaded no]
CAppInfoCacheReadFromDiskThread took 2 milliseconds to initialize
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no]
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
0x2a01da0:2: Async thread=0x2ac3290
0x2aa6500:2: I/O status block
0x2ac3e10:1: fsync idx=2768
0x2ac4f90:1: Fd unix_fd=1766 user=0x1bb8600 options=00000000
0x1bb8600:2: Socket fd=0x2ac4f90, state=3, mask=0, pending=44, reported=44
0x2ac3290:1: Thread id=04dc unix pid=13181 unix tid=13478 state=1
0x29d7570:1: Token id=0.1013 primary=1 impersonation level=-1
0x29d76d0:1: Process id=0124 handles=(nil)
pid 12961 != 12959, skipping destruction (fork without exec?)
Game 440900 created interface STEAMAPPS_INTERFACE_VERSION008 /
Game 440900 created interface STEAMREMOTESTORAGE_INTERFACE_VERSION016 /
Game 440900 created interface STEAMUSERSTATS_INTERFACE_VERSION012 /
Game 440900 created interface SteamFriends017 /
Game 440900 created interface SteamMatchMaking009 /
Game 440900 created interface SteamMatchMakingServers002 /
Game 440900 created interface SteamNetworking006 /
Game 440900 created interface SteamUser023 /
Game 440900 created interface SteamUser023 / User
Game 440900 created interface SteamUtils010 /
Game 440900 method call count for IClientNetworking::AllowP2PPacketRelay : 1
Game 440900 method call count for IClientUtils::RecordSteamInterfaceCreation : 12
Game 440900 method call count for IClientUtils::GetAppID : 14
Game 440900 method call count for IClientUser::BIsSubscribedApp : 1
Game 440900 method call count for IClientUser::GetSteamID : 1
Uploaded AppInterfaceStats to Steam
here is mine when i try to launch conan exiles.
maybe its related to:
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
i found this https://github.com/ValveSoftware/steam-for-linux/issues/10215 and apparently steamservice.so missing was causing other games to not launch. i tried updating to steam beta and still won't launch.
Yesterdays steam update broke Conan Exiles, same errors here as well.
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no]
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
pid 1967 != 1966, skipping destruction (fork without exec?)
I have been able to get the game running (without steam services) by editing the /steamapps/common/Conan Exiles/ConanSandbox/Config/Windows/WindowsSteamEngine.ini and changing true to false on the OnlineSubsystemSteam bEnabled line.
Does not help much in my use, since I would like to play online again.
@maliciouspastry I can confirm this. Setting bEnabled to false works. The game starts just fine, bit since the steam services are now disabled, nothing actually works.
Is this one of those things, where a well placed link in the right place maybe fixes the problem?
Yesterdays steam update broke Conan Exiles, same errors here as well.
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no] *** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated pid 1967 != 1966, skipping destruction (fork without exec?)
I have been able to get the game running (without steam services) by editing the /steamapps/common/Conan Exiles/ConanSandbox/Config/Windows/WindowsSteamEngine.ini and changing true to false on the OnlineSubsystemSteam bEnabled line.
Does not help much in my use, since I would like to play online again.
can confirm this too, on arch
i can confirm that disabling OnlineSubsystemSteam by setting bEnabled to false works on my end too. but, like mentioned, online play is completely disabled. which in return means single player as well for whatever reason. maybe its because it has co-op built into it. at least it launches now and we know it isn't the game. its steam.
Same here, game is now broken. Logs mention *** buffer overflow detected *** before the process exits. There's also mention of steamservice.so near the end, but probably the buffer overflow is the more likely cause.
This occurs on proton 8, experimental, and hotfix at least, proton 6 gets into the game main menu but complains no steam services are responsive. Proton 7 variants crash in the intro movie with Unreal Engine crash reporter. I used to run the game on Proton 8 before the update that seems to have stopped it from starting normally.
when using proton experimental i don't have
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
but game don't start.
CAppInfoCacheReadFromDiskThread took 2 milliseconds to initialize
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
pid 64761 != 64760, skipping destruction (fork without exec?)
Game 440900 created interface STEAMAPPS_INTERFACE_VERSION008 /
Game 440900 created interface STEAMREMOTESTORAGE_INTERFACE_VERSION016 /
Game 440900 created interface STEAMUSERSTATS_INTERFACE_VERSION012 /
Game 440900 created interface SteamFriends017 /
Game 440900 created interface SteamMatchMaking009 /
Game 440900 created interface SteamMatchMakingServers002 /
Game 440900 created interface SteamNetworking006 /
Game 440900 created interface SteamUser023 /
Game 440900 created interface SteamUser023 / User
Game 440900 created interface SteamUtils010 /
Game 440900 method call count for IClientNetworking::AllowP2PPacketRelay : 1
Game 440900 method call count for IClientUtils::RecordSteamInterfaceCreation : 12
Game 440900 method call count for IClientUtils::GetAppID : 14
Game 440900 method call count for IClientUser::BIsSubscribedApp : 1
Game 440900 method call count for IClientUser::GetSteamID : 1
Uploaded AppInterfaceStats to Steam
steam-440900.log
attached my proton-log with proton-experimental. the:
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
error isn't present with proton experimental, but still fails to launch BUT, the game will launch still, if you disable steam online services by editing the /steamapps/common/Conan Exiles/ConanSandbox/Config/Windows/WindowsSteamEngine.ini and changing true to false on the OnlineSubsystemSteam bEnabled line.
so either way, its steam online services preventing the game from working.
steam-440900.log attached my proton-log with proton-experimental. the:
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
error isn't present with proton experimental, but still fails to launch BUT, the game will launch still, if you disable steam online services by editing the /steamapps/common/Conan Exiles/ConanSandbox/Config/Windows/WindowsSteamEngine.ini and changing true to false on the OnlineSubsystemSteam bEnabled line.
so either way, its steam online services preventing the game from working.
can confirm this too.
I just post same here for both my PC and SteamDeck - was hoping you super smart people would have a work around.
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
Maybe the problem is here?
Interesting to note a massive uptick of reports about this specific issue at ProtonDB: https://www.protondb.com/app/440900
So it's not just those of us who know about github. :)
Interesting to note a massive uptick of reports about this specific issue at ProtonDB: https://www.protondb.com/app/440900
So it's not just those of us who know about github. :)
question is, is it enough to get valves attention to get this fixed? sucks conan isn't an officially supported game by valve. has me really worried its a low priority because of it. really sucks.
Having the same issue as everyone else (working fine prior to last update), except I get this
*** buffer overflow detected ***: terminated
Instead of
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
I tried with the Proton versions provided by Steam as well as the Custom GE versions.
Did that config file edit and was able to reach main menu as well, but unable to do anything else due to an expected error about not connecting to steam.
Ran the game with strace attached. Not sure if this helps but all the DLL files are untouched, fresh game install as well to verify. I get these lines as output.
0128:warn:steamclient:get_mem_from_steamclient_dll Module not found, err 126. 0128:warn:debugstr:OutputDebugStringA "[S_API FAIL] SteamAPI_Init() failed; no appID found.\nEither launch the game from Steam, or put the file steam_appid.txt containing the correct appID in your game folder.\n" 0128:warn:seh:dispatch_exception "[S_API FAIL] SteamAPI_Init() failed; no appID found.\nEither launch the game from Steam, or put the file steam_appid.txt containing the correct appID in your game folder.\n" 0128:warn:debugstr:OutputDebugStringA "[S_API FAIL] Tried to access Steam interface SteamUtils010 before SteamAPI_Init succeeded.\n" 0128:warn:seh:dispatch_exception "[S_API FAIL] Tried to access Steam interface SteamUtils010 before SteamAPI_Init succeeded.\n" 0128:warn:seh:OutputDebugStringW L"LogOnline:Warning: STEAM: Steamworks: SteamUtils() failed!\r\n"
This is what causes the bit out of range error, and the buffer overflow error.
That strace is interesting.. Where is Steam trying to look? It complains about no appID being found, did you check to see if such a file existed in the Conan directory? I see it in mine.
I tried doing launch option:
LD_PRELOAD=path/to/.steam/steam/ubuntu12_32/steamservice.so %command%
The log shows this:
ERROR: ld.so: object 'path/to/.steam/steam/ubuntu12_32/steamservice.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
[17:18:01.413 | browser | info] Application will quit.
CAppInfoCacheReadFromDiskThread took 4 milliseconds to initialize
*** buffer overflow detected ***: terminated
Then it hangs indefinitely unless I force it to stop. Was there ever a 64 bit version of steamservice.so? I don't see any in the /ubuntu12_64/ folder.
Update: It seems like that ELF class error happens even when steam is working "normally", so it might not be the culprit.
This sucks. I can confirm config change allows game to open main menu but nothing more as even single player requires online services...
It's a workaround.
But i'm able to play conan exiles throught the steam client that i've installed on lutris.
It's a workaround. But i'm able to play conan exiles throught the steam client that i've installed on lutris.
Be interesting to know the version of the Steam Client you have vs the rest. My current.
Steam Beta Branch: Stable Client
Steam Version: 1705108172
Steam Client Build Date: Fri, Jan 12 17:52 UTC -07:00
Steam Web Build Date: Fri, Jan 12 10:02 UTC -07:00
Steam API Version: SteamClient021
It's a workaround. But i'm able to play conan exiles throught the steam client that i've installed on lutris.
i take it you installed the windows version of steam via lutris?
yes i've installed the windows version of steam via lutris.
client version is the same
After an update for left 4 dead (thanks for that) I am forced to update via steamcmd.sh and see this issue.
No Proton version works at the moment. The issue is reported on the Official Funcom website and across various social media outlets. Clicking "Play" will trigger the Funcom launcher but the game will not launch from there. This all started after two Steam Workshop updates on January 11th and January 12th.
These are the two Steam updates:
https://store.steampowered.com/news/app/593110/view/3901870710035098052 https://store.steampowered.com/news/app/593110/view/6623172784186899212
Official Funcom:
https://forums.funcom.com/t/since-jan-13-game-wont-launch-on-linux/248673
ProtonDB:
https://www.protondb.com/app/440900
I got a stack trace of the crash, it's in the thread IPC:CSteamEngine, so definitely looks like a steam bug. The bit out of range is 0x49c, larger than the fd_set size of 0x400.
The game makes a large number of threads, and each thread opens a pipe for communicating with wineserver, which pushes the fd count past the size of fd_set.
For anyone with the debug symbols to the (64-bit) steamclient.so with sha256 ad9f4250539276932f1c1010bbcc44a9f1aa98e88ad573ca555a9b969c6f11ba, here's a partial stack trace (addresses match what you get in Ghidra):
__fdelt_warn (crash) libc.so.6
0x01cdf826
0x01cdc160
0x01cde82c
0x01f78b11
0x00cc9f55
0x00c38b2b
0x0123e304
0x013b5ed9
0x013b6638
0x01eda37a
0x01ed8571
0x01ed8c6b
Replying to https://github.com/ValveSoftware/Proton/issues/2563#issuecomment-1906462064
if this is indeed a steam bug, could you make a thread about what you found at https://github.com/ValveSoftware/steam-for-linux ? to help get their attention for it.
also can anyone else confirm that conan exiles is working via windows steam installed via lutris to go with the one report of it working that way?
Replying to [#2563 (comment)](https://github.com/ValveSoftware/Proton/issues/2563#issuecomment-1906462064)
if this is indeed a steam bug, could you make a thread about what you found at https://github.com/ValveSoftware/steam-for-linux ? to help get their attention for it.
Looks like somebody did. The issue was closed, and the poster was referred to the Proton repo as is their policy for unsupported titles. because they see it as an issue with Proton compatibility. I disagree, but that means little.
Its also possible that this issue is related but I'm not certain on that.
also can anyone else confirm that conan exiles is working via windows steam installed via lutris to go with the one report of it working that way?
I'm currently playing the game with Lutris + Windows Steam client install. Smooth gameplay
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
Thanks, the beta client update works for me. :+1:
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!Thanks, the beta client update works for me. 👍
Thanks so much beta client update works!
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
Confirmed working! Thank you!
Steam Beta Branch: Steam Beta Update
Steam Version: 1706306386
Steam Client Build Date: Fri, Jan 26 9:28 PM UTC -08:00
Steam Web Build Date: Fri, Jan 26 8:26 PM UTC -08:00
Steam API Version: SteamClient021
Proton 8.0-5 - Build ID: 13223186
Debian 6.1.69-1 (2023-12-30)
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
@TTimo Can confirm that the game now works with the Steam beta on Ubuntu 22.04, using GE-Proton8-25. Everything seems to be back to normal. Thank you!
Any ETA on when this fix will make it to stable Steam?
Steam Beta Branch: Steam Beta Update
Steam Version: 1706306386
Steam Client Build Date: Fri, Jan 26 9:28 PM UTC -08:00
Steam Web Build Date: Fri, Jan 26 8:26 PM UTC -08:00
Steam API Version: SteamClient021
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
i confirm too, it's working on steam beta.
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
Thank you very much, looks like it works fine now in Steam Beta indeed! ^_^
thank you valve. the new steam client beta update for linux indeed fixed it for me.
Conan Enhanced - Launcher Refuses to Play, Due to DirectX12 Requirement
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9775.
@BraniyaKz posted on 2026-05-12T21:53:53:
The Launcher shows fine, and I've disabled BattleEye to play offline, however, when hitting Play, a window pops up, saying that DirectX12 is required, and to remove the DX11 launch options (I don't have any launch options set). When manually setting the launch options for DX11 and hitting Play in the launcher, a new popup says "This project doesn't support DX11.", and the game fails yet again. Keep in mind, this is after Vulkan has finished processing Shaders.
It is my understanding the DXVK isn't supported for DX12, only 11 and older, and I've never used it before. I checked Reddit, and some people are able to play Conan Enhanced on Steam Deck perfectly fine, so I'm unsure why Linux users are having such a hard time, but as of now, noone has found a work-around.
Contacted Steam Support, and they didn't have any advice for me, just to leave a bug report here. If anyone knows what's going on, please reply to my report.
Clear all Conan Enhanced Launch Options, Set Compatibility to any Proton Version, Launch, let Vulkan Process, Disable BattleEye and hit Play in the Launcher.
Get met with a popup complaining about needing DirectX12, and to remove your DX11 Launch options, even though you've got none of that set (Probably something Proton is doing in the background, idk).
Force DX11 in launch options, launch the game, and get another popup saying that the project doesn't support DX11.
Verify files, Clear everything again, set to Proton Experimental, launch. Hit Play in Launcher and be met with the same messagebox again, effectively locking you out of the game.
Only thing I havent tried yet is tinkering around with Protontricks/Wine to try to launch the executable directly, which according to others on reddit, is hit or miss for others on linux with the same issue.
Hello @BraniyaKz, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
@kisak-valve Took me awhile to find it, but here it is.
steam-440900.log
Gist: https://gist.github.com/BraniyaKz/7ec60e29fd3206a3dd7f24af61b16382
Also, after recent updates to the game, the launcher no longer shows.
Looks like there's a problem with your system seeing your NVIDIA GPU. https://gist.github.com/BraniyaKz/7ec60e29fd3206a3dd7f24af61b16382#file-gistfile1-txt-L82-L83 tells us the environment is trying hard to use the NVIDIA driver, usually seen with optimus laptops, but an NVIDIA GPU wasn't enumerated (https://gist.github.com/BraniyaKz/7ec60e29fd3206a3dd7f24af61b16382#file-gistfile1-txt-L96-L125) leaving a GLX render path busted https://gist.github.com/BraniyaKz/7ec60e29fd3206a3dd7f24af61b16382#file-gistfile1-txt-L151-L162.
I'd start troubleshooting by pulling the prime render offload environment variables first and get the game running on the Intel GPU, then after that investigate what's going on with the NVIDIA GPU.
GPU: GeForce RTX 4070 Ti
Video driver version: 595.71.05-1pop1~1778517566~24.04~dd7d311
Kernel version: Linux 6.18.7-76061807-generic
Gist: https://gist.github.com/):https://gist.github.com/jkavenaugh/a9d67f40366bf387e6c16c48ed397c7c
Proton version: Default
Log:
Crash with error "Out of video memory trying to allocate a rendering resource. Make sure your video card has the minimum required memory, try lowering the resolution and/or closing other applications that are running. Exiting..."
Edit:
This seems to only happen when using direct connection. Single player and being invited over Steam don't seem to have an issue. Isle of Siptah is fine.
GPU: AMD Radeon RX 6650 XT
OS: Ubuntu 24.04
Proton Version: Experimental
Game crashes on launch. This seems to be a regression, as Proton Hotfix works without issue.
Found a custom swapchain provider: 'FSRSwapchainProvider'. SwapChain1->ResizeBuffers(NumBackBuffers, SizeX, SizeY, UE::DXGIUtilities::GetSwapChainFormat(PixelFormat), SwapChainFlags) failed at C:\b\exiles\Engine\Source\Runtime\D3D12RHI\Private\Windows\WindowsD3D12Viewport.cpp:310 with error E_INVALIDARG
proton hotfixx1 2026-07proton experimentalx8 2026-05ge-proton8-25x3 2024-01proton 8.0-5x1 2024-01ge-proton8-27x1 2024-01ge-proton8-16x1 2023-11ge-proton8-20x1 2023-11proton 8.0-4x1 2023-11proton 8.0-2x1 2023-05proton 6.3-8x1 2022-05proton 6.3-5x1 2021-10proton 6.3-4x2 2021-06proton 6.8x1 2021-06proton 6.9x1 2021-06PROTON_LOG=1x8 2026-05PROTON_ENABLE_NVAPI=1'x1 2021-10
Compatibility Report
System Information
I confirm:
Symptoms
You can't launch the game with Battleye or play any Battleye protected servers but the game does allow you to play without it in both singleplayer/co-op and online on non-protected servers.
The game runs at a solid 60fps for me on almost all high graphics with the exception of frame drops. I'd assumed it was a shader cache issue (or whatever you call it) but it never stops. Every time you look in a new direction, the framerate will drop suddenly and shoot back up to 60. Every time you gather a resource node, every time you build an object etc, the same thing. Normally a drop that small wouldn't matter much but it actually causes an immense and jarring stuttering throughout the entirety of the game.