Proton
Proton copied to clipboard
ValveSoftware
Ashes of the Singularity: Escalation (507490)
Compatibility Report
- Name of the game with compatibility issues: Ashes of the Singularity: Escalation
- Steam AppID of the game: 507490
System Information
- GPU: RX580 8GB
- Driver/LLVM version: Mesa 18.1.8, LLVM 6.0.1
- Kernel version: 4.18.6
- Link to full system information report as Gist: https://gist.github.com/ananace/fec7a290582e7d7070af19b675ac074d
- Proton version: 3.7-6 Beta
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.
Symptoms
The launcher fails to load, crashing with an error about not being able to load gamedata.dat.
Replacing the StardockLauncher.exe binary with AshesEscalation.exe to bypass the launcher lets the game launch, until it finishes loading assets and then freezes.
Reproduction
Replace StardockLauncher.exe with AshesEscalation.exe, launch the game.
Using regular WineD3D11 shows no difference, except for taking longer to finish loading the assets.
Where it freezes;
Confirmed. I had the same issue.
Distro: Linux Mint 19 Tara Processor: AMD Ryzen 7 1700 GPU: GTX 1070, Nvidia proprietary driver 396.54 RAM: 32GB Kernel (custom) - 4.17.14 (optimized for Ryzen) Resolution: 1920x1080 Proton 3.7-6
not working for me error.log shows a weird message
Game update: AppID 507490 "", ProcID 5277, IP 0.0.0.0:0
ERROR: ld.so: object '/home/dan/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
>>> Adding process 5294 for game ID 507490
ERROR: ld.so: object '/home/dan/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 5297 for game ID 507490
AL lib: (WW) GetSymbol: Failed to load jack_error_callback: /usr/lib/x86_64-linux-gnu/libjack.so.0: undefined symbol: jack_error_callback
AL lib: (WW) jack_msg_handler: Cannot connect to server socket err = No such file or directory
AL lib: (WW) jack_msg_handler: Cannot connect to server request channel
AL lib: (WW) jack_msg_handler: jack server is not running or cannot be started
AL lib: (WW) jack_msg_handler: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
AL lib: (WW) jack_msg_handler: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
AL lib: (WW) ALCjackBackendFactory_init: jack_client_open() failed, 0x11
AL lib: (WW) alc_initconfig: Failed to initialize backend "jack"
AL lib: (EE) SetChannelMap: Failed to match front-center channel (2) in channel map
Installing breakpad exception handler for appid(gameoverlayui)/version(20180908192109)
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
I have a creative x-fi fatality pro which has 7.1 sound. i have no clue why i'm getting that message about jack server. i've never used jack server weird game freeze with turinium optimized
not working for me error.log shows a weird message
...I have a creative x-fi fatality pro which has 7.1 sound. i have no clue why i'm getting that message about jack server. i've never used jack server weird game freeze with turinium optimized
Those messages are probably related to using the Wine XAudio DLLs, you could get rid of them using winetricks/protontricks and installing xact, though it won't solve the game issues as they're not audio related.
is there any way to find out what is the problem with the game in proton? i've seen a lot of people saying that they can play the game. Here are my system infos ive tried also arch linux with 4.18 kernel. no luck there also the only think in common is cinnamon DM
btw another strange thing is that launcher can't find setting file when you try to edit it. it even offer you the option to save it in a "strange" path. it seems like launcher and wine are not working well togheter
@flibitijibibo This seems somewhat related to XAudio2 too?
From original post Proton log:
394966.649:0025:0026:trace:module:load_dll looking for L"C:\windows\system32\xaudio2_7.dll" in L"C:\windows\system32;C:\Program Files (x86)\Steam;C:\windows\system32;C:\windows\system;C:\windows;.;C:\windows\system32;C:\windows;C:\windows\system32\wbem"
But it seems that the game not loading issue stems from something other than Xaudio, according to user ananace:
Those messages are probably related to using the Wine XAudio DLLs, you could get rid of them using winetricks/protontricks and installing xact, though it won't solve the game issues as they're not audio related.
In addition to checking for xaudio2_x, it's also a good idea to check for x3daudio1_*, as some games might only use XAudio2 as a basic output stream, and the current builtin should handle that without any trouble. This seems to fall into the X3DAudio category so it probably is actively used, but you're right in that there's probably something bigger going on with this one...
I have found 2 problems with Proton and Ashes so far:
In game settings not saved across restart
Proton 3.16 beta now uses a Compatdata folder for the pfx folder. In the pfx/drive_c/users/steamuser folder there is no symlink to "My Documents" folder. Creating a symlink to Documents in your home folder fixes this and allows the game to save settings in the settings.ini. (Note: The "edit settings file" from the launcher still does not open properly. Ignore this, the settings from ingame will be saved with the above fix.)
Multiplayer is disabled:
Multiplayer is disabled and if we look at the run log it shows:
ChecksumManager: Checksum_GameCore_Summary does NOT match!
Reading on the internet suggests that some windows users have suffered from this problem and it appears to be caused by installing Ashes on a drive that is not C:/. This is a problem for Proton as it maps any linux location to Z:/ (this is confirmed in the Ashes runlog.txt).
Executable Path: Z:\mnt\ssd_games\native_steam\steamapps\common\Ashes of the Singularity Escalation\AshesEscalation_DX11.exe
Hopefully a Proton dev will be able to chip in on this one to see if there is any workarounds for the Z:/ mapping issue
Also this game will not launch for me unless I set the following launch options to the following in steam:
PROTON_NO_ESYNC=1 %command%
When you say
Replace StardockLauncher.exe with AshesEscalation.exe, launch the game.
What does that entail exactly? There are many different actions that could match that.
If I cop and rename AshesEscalation.exe to StardockLauncher.exe overwriting the initial one the same issue persists where the game just immediately closes when launching.
It seem it might be a pathing issue? As the game can't find it's settings.ini, even though it clearly exists.
In my case, I just copy the game executable on top of the launcher, overwriting it.
On Fri, 11 Jan 2019, 08:03 Douglas Gaskell <[email protected] wrote:
When you say
Replace StardockLauncher.exe with AshesEscalation.exe, launch the game.
What does that entail exactly? There are many different actions that could match that.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/1479#issuecomment-453400872, or mute the thread https://github.com/notifications/unsubscribe-auth/AAgnvKCoSiNQGxab8Y7C0yljJU27jKRgks5vCDdTgaJpZM4WqyZX .
@ananace So renaming the executable to StardockLauncher.exe overwriting it?
rename StardockLauncher.exe to StardockLauncher.exe.bak rename AshesEscalation.exe to StardockLauncher.exe
Be aware you might need the NO_ESYNC option. This is required by some but not by others. Not sure why. If I do not set the NO_ESYNC option the game will instantly close
Also this game will not launch for me unless I set the following launch options to the following in steam:
PROTON_NO_ESYNC=1 %command%
@7oxicshadow Thanks! This confirms what I have been trying.
Unfortunately, in my case, the game still instantly closes after opening. Do you know where I might be able to find a log that says why? Unfortunately the system log doens't have anything, and there is no error log in the ashes folder.
Tried the dx11 and vulkan ones too (and dx12 for good measure, tho never expected that to work) since I read other people having success in dx11 or vulkan mode.
Looking to find out what I can do to diagnose or find error logs at this point.
Basic System info:
Proton:3.16-6
Distro:Ubuntu 18.10
Kernel:4.18.0-12-generic
RAM:32 GB
GPU Driver:4.4 Mesa 18.2.2
GPU:Radeon RX 580
CPU:AMD Ryzen 7 2700X Eight-Core
Hopefully someone with an AMD setup will be able to tell you if that is the best driver or not. I think the Mesa driver is still missing support for some DXVK functions/Extensions.
All I can recommend is to check that you are using proton 3.16-6 and that "use this tool instead of game-specific selections from steam" is also ticked on the steam play settings page.
In my case;
CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
GPU: Radeon RX 580 Series (POLARIS10, DRM 3.26.0, 4.18.0-sabayon, LLVM 7.0.0)
Driver: 4.5 (Compatibility Profile) Mesa 18.3.1
I've been playing some skirmishes on Ashes with the Mesa radv driver, so it certainly implements enough features to run this game.
My suggestion on debugging is to run Steam in a terminal so you can see any output in there, and possibly also adding PROTON_LOG=1 to the launch, it'll produce a full Wine log in your home directory which might help on if it's a Wine issue that causes the issue for you at @douglasg14b .
Thanks!
Was able to see some error in the wine log, not sure how helpful it is though:
wine: Unhandled page fault on read access to 0x00000000 at address 0x1403fab5b (thread 0025), starting debugger...
696114.801:0024:0025:trace:seh:start_debugger Starting debugger "winedbg --auto 36 148"
696115.492:0024:0025:trace:seh:call_teb_handler handler at 0x7b4a0c30 returned 1
696115.492:0024:0025:warn:seh:call_stack_handlers exception data not found in L"AshesEscalation_DX11.exe"
See the same error for the vulkan one as well. Hm.
Regarding the failed validation. If you re-verify the steam files, 1 file gets fixed. These are the files that are modified while steam verifies and fixes the files:
/SteamLibrary/steamapps/downloading/507490/gamedata.dat
/SteamLibrary/steamapps/downloading/state_507490_580374.patch
/SteamLibrary/steamapps/compatdata/507490/version
/SteamLibrary/steamapps/compatdata/507490/pfx.lock
The steam steamclient.dll and steamclient64.dll get modified as well. So does openvr_api_dxvk.dll and vrclient.dll.
When the game is run the following files are modified:
/SteamLibrary/steamapps/compatdata/507490/pfx/reg41950000.tmp
/SteamLibrary/steamapps/compatdata/507490/pfx/drive_c/users/steamuser/Local Settings/Temporary Internet Files/Content.IE5/2J1WR8SC/gamedata.337[0]
/SteamLibrary/steamapps/compatdata/507490/pfx/drive_c/users/steamuser/Temp/gamedata.dat
/SteamLibrary/steamapps/common/Ashes of the Singularity Escalation/gamedata.dat
/SteamLibrary/steamapps/compatdata/507490/pfx/drive_c/users/steamuser/My Documents/My Games/Ashes of the Singularity - Escalation/RunLog.txt
I think the safe bet is that gamedata.dat is getting modified. I just don't understand why that is happening.
Glad some people are taking a look at this, I'm going to try it out too,
btw guys this is supposed to have a native port to linux sometime this year (2019). It was always Stardock's plan to eventually support linux for this game, so don't sweat it too hard :P
this guide allowed me to run it on my first try! thanks! :
rename StardockLauncher.exe to StardockLauncher.exe.bak rename AshesEscalation.exe to StardockLauncher.exe
Be aware you might need the NO_ESYNC option. This is required by some but not by others. Not sure why. If I do not set the NO_ESYNC option the game will instantly close
Also this game will not launch for me unless I set the following launch options to the following in steam: PROTON_NO_ESYNC=1 %command%
runs acceptably for me, haven't tried multi but I don't see the point given how laggy this is.
I'd used this same rig under windows and was getting night-and-day performance from this. I never tried wine or proton on it because I didn't think it'd run well and now I've confirmed it.
Here's hoping Stardock hurry up. they had already promised the linux port for Q4 2018, it keeps getting pushed back.
A linux port will be great! Also funny seeing you here as well @tatsujb :smile_cat:
i can't start the game with vulkan api. do i need to do anything? the game starts but i get only the mouse and an empty window - as in whatever was in the background before the game starts will be in the game windows like a screenshot
It sounds like you are getting the launcher without graphics. This used to be an issue for me but was fixed with the latest proton builds.
If you look at the attached screenshot and estimate where the play button is and click it the game should launch.
This game runs great with proton now. Multiplayer works and everything with proton 4.2-2
@7oxicshadow How did you get proton 4.2-2? I don't see that option in my steam install.
I have seen that happen before. Force steam to check for updates (Steam > Check for steam client updates). It should find it.
Got it.
Unfortunately Ashes still just crashes as soon as I hit play in the launcher 0n 4.2-2 :/