Open KorinFlakes opened 5 years ago
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.
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
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.