Ashes of the Singularity: Escalation (507490) #1479
Comments
kisak-valve
added
the
Game compatibility - Unofficial
|
Confirmed. I had the same issue. Distro: Linux Mint 19 Tara |
|
not working for me 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 |
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? |
|
btw |
|
@flibitijibibo This seems somewhat related to XAudio2 too? From original post Proton log:
But it seems that the game not loading issue stems from something other than Xaudio, according to user ananace:
|
|
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. Multiplayer is disabled: Multiplayer is disabled and if we look at the run log it shows:
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). 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
What does that entail exactly? There are many different actions that could match that. If I cop and rename 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 ***@***.*** 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
<#1479 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAgnvKCoSiNQGxab8Y7C0yljJU27jKRgks5vCDdTgaJpZM4WqyZX>
.
|
|
@ananace So renaming the executable to |
|
rename StardockLauncher.exe to StardockLauncher.exe.bak 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
|
|
@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. |
|
try renaming AshesEscalation_DX11.exe to StardockLauncher.exe instead |
|
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. |
|
i assume you are using either the nvidia or amd binary drivers? |
|
Basic System info: |
|
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; 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 |
|
Thanks! Was able to see some error in the wine log, not sure how helpful it is though: 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: The steam When the game is run the following files are modified: 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! :
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 😸 |
|
well.... RTS-ers are nothing if not devoted to the genre ;) |
|
i can't start the game with vulkan api. do i need to do anything? |
|
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 can't really tell from that comment if they mean (a) there is no fix right now, or (b) a fix is impossible And does this mean that no Windows games with Vulkan drivers work with any Radeon card? |
|
Ashes' Vulkan renderer also doesn't work with RADV.
On Linux (using Wine/Proton), you mean? No, there are definitely games with Vulkan renderers that work fine using Wine on Linux with AMD GPUs. Doom (2016) comes to mind, but there are dozens. I think that quote by @doitsujin should be read in the context of Ashes specifically. |
I though something like that. I tried Paths of Exile's beta Vulkan and it worked fine. So I have to wonder, Is this something that's easier fixed from WINE's side or AotS? Stardock are really quite reasonable, and they even discussed a Linux native version of AotS during the dev cycle. If there is something they can easily do to make it compatible and they had some help from the community with understanding the problem and testing fixes this might get sorted. I assume that mapping from Windows Vulkan via WINE to the Linux native Vulkan is more efficient than DXVK... or is this entirely pointless? |
|
Be aware that the vulkan back end for Ashes is inferior to any DX back end regardless of OS. The developers could never get the efficiency to be anything like dx11/12. There is a dev response on the steam forums if iirc to back this up. I seem to remember it was in response to a question regarding Linux support. Personally I would stick with DXVK as it gives the best FPS for me (using NVIDIA) |
Yeah, ok...
On the upside, the GE editions of Proton support AotS from Proton-5.11-GE-2-MF onward, it seems. Maybe at some point the lighting inefficiency might get addressed. Or RDNA2/Big Navi will arrive and not be too expensive (crosses fingers) and the extra grunt will render my specific problem moot, assuming I don't get tripped up by DX11's ageing shader model. I am no expert. Maybe someone can set me straight? |
|
As I understand it, VKD3D is in Proton from 5 onward, but I might need to do something to enable it per game? OK, so I tried to set Is that all I need to do, or is there VKD3D configuration that needs to be done beyond just enabling it? I am using Proton-5.11-GE-3-MF now, as well. EDIT: EDIT2: EDIT3 Here is a quote: "Update: 9/29/2019: The difference based on the video card set up is pretty drastic too (not blaming any video card drivers here but the variance is pretty huge and would result in some unhappy people). The good news is that Ashes II (and our other new titles) should, in theory, ship with Linux support off the bat thanks to this effort. Those of you who are familiar with Stardock know we came from the OS/2 world back in the day so we are very much motivated to make our games work on Linux too. Just a matter of having enough resources to do it. Thank you for your support on this. The sign up sheet helped us push through getting budget to do the initial port which should have benefits long-term for all our games not being so tied to Windows in the future." It clearly indicates that Vulkan was an afterthought. This seems to pretty clearly indicate that if I want extra free FPS from a modern shader model (and threaded DX, etc) my only path is DX12/VKD3D. |
|
OK, given that Vulkan seems to be not a solution, DX12/VKD3D seems like my best path to those tasty extra frames Radeon gets with a modern API (from the modern shader model, superior threading etc).
The game loads this way with both Proton-5.9-GE-5-ST and Proton-5.11-GE-3-MF. It also loads with RADV or AMDVLK as the system Vulkan driver (yes I know I need to change the Launch Options)! But I don't see a DX12 option presented in-game. Any Radeon users out there interested in this? Or should I just give up and wait for Ashes 2, seeing as it will be native? At this point I am not even sure what to try next to get the game to see DX12 as an option to present. VKD3D seems to work really well for certain games, but I don't know if that's a function of the work GloriousEggroll does. Any suggestions for a next step? |
|
PROTON_USE_WINE_DXGI=1 and make sure win10 is set. |
No, you're right. In fact, it's even better than that because there isn't really such as a thing as "Windows Vulkan" that has to be translated. It's just native Vulkan, which does not need a translation layer because your GPU drivers understand that directly. You still need Wine to run the Windows game of course, but you don't need something like DXVK or VKD3D.
I'm not sure. IIRC VKD3D's performance is not nearly as good as DXVK's, which I think offsets any potential gains you got by using DX12 over DX11. |
What Proton build are you using? 5.0-9, 5.0-10 or 5.9-GE-5-ST or 5.11-GE-3-ST? OK, so my Launch Options now look like: And then use protontricks to set the Windows edition to 10?
But the issue is that I can't get the Vulkan version to launch. Have you had any success in getting Vulkan to work for AotS? |
|
OMG, @random2324 you are my Heathen God and I want to have your babies. This WORKS with 5.9-GE-5-ST. To confirm that this was the only step I deleted the old compatdata folder for AotS and started again. I didn't even need to protontricks it to Windows 10 because I think that Proton-5.9-GE actually takes care of that already. Even better than it working it also gave me a TONNE of extra FPS, as I had hoped. Each benchmark scene gave me 10+ extra FPS in DX12 over DX11, plus the quality of the lighting is far superior. |
|
I build Proton myself using TKG. You also dont need the Proton Log option set everytime. Except thats intentional. You wont get the Vulkan version to launch. Its not possible in the moment. The game seems to check for specific (Windows) driver versions. Faking those seems to be no trivial task. Also it's not like just because the vulkan renderer of the game runs now on Linux it maps its calls directly to the driver. There is still something necessary called winevulkan which mimicks Windows behavior. Anyway I wouldn't expect much of an improvement for this. Vkd3d and DXVK are already pretty good sometimes even outperform Windows. |
Hey, look, Vulkan or DX12 it's all good: anything with a modern shader model is going to be 10-20% faster on Vega. Stardock seem to indicate that the Vulkan support in AotS is very much an afterthought and no efficient anyway. VKD3D is working well and that's giving me better performance AND visuals. Can't ask for much more than that. I had a look into TKG and it's not quite as simple as GE. I am sure it's superior, but GE 'just works' with no more effort than downloading a tar.gz and expanding it into a folder. Yeah, yeah, lazy user... But... now I know what works to get DX12 going for AotS there are other DX12 games I can consider. |
|
I’ve downloaded Proton-GE and tried to use vkd3d but the game only lists DirectX 11 and Vulkan APIs in the settings, even though my video card (GTX 1650) does support DX12. |
Try using protontricks to set the OS to Windows 10 for AotS, @BabylonAS . I had assumed GE set it for me, but evidently I had changed it to Windows 10 at some point while I was tinkering. The invocation I am using is also for RADV Vulkan. If you didn't already, you will need to remove the
|
|
No, it doesn't work for me — the game hangs on the loading assets screen. |
|
PROTON_NO_ESYNC=1 doesn’t seem to make a difference. Looks like we’re back to where this whole issue begins... |
Bummer. I just tried another machine I have with an RX 580 in it and it worked fine on that, was even easier because I don't have both RADV and AMDVLK on that machine at the same time. I just don't have any nVidia cards to try it with. You're on what Linux distro? Proton-5.9-GE-5-ST? FSYNC capable Kernel? Shader pre-caching enabled? I have tried to keep much of my main system as close to the shipped versions from Manjaro to make it easier to help some friends that have made the move too, so I am not really running anything that out of the ordinary. |
|
Arch Linux, with 5.8.3-arch1-1 kernel. No idea about fsync or pre-caching. |
|
Kernel 5.8 has FSYNC patched-in by default. You'll want FSYNC and ESYNC enabled for the best performance (not much point in getting DX12 going if it does't run better). Shader pre-caching can be turned on in Steam: If you have a lot of games installed that can take a while to run. It will stop the background processing if you start a game in Steam, but you'll want to shut down Steam if you want to play a Lutris game and the background stuff hasn't settled down. Your best bet might be best to set it and then go to bed or do something else for a while and let it run. How long it takes is a function of your CPU performance and the number of games you have installed. Even if you can't get DX12 going, you're still better off on the GE Proton build. 5.0-9 doesn't run AotS at all, so at least with GE Proton and ESYNC and FSYNC your performance will be better than with the current recommendation on ProtonDB, Proton-4.2-9. |
|
Just a note: CPU AMD R7 3800XT (watercooled) steam launch parameters: VKD3D_VULKAN_DEVICE=1 PROTON_LOG=1 mangohud RADV_PERFTEST=aco %command% ive tested with /nolauncher and without it, the game starts in both instance. Game runs reasonably well on VKD3D (DX12), but about 20 percent less fps on Linux. win10benchmar output: Saw some fixme:err in proton log SIde note: i did checked the vulkan render too on win: about 20-25% less fps in gpu focused, but 1-2 fps more in cpu focused benchmark. |
|
I can not run this game Launch parameter Game gets to the launcher and after hitting play, it hangs forever. flatpak steam |
|
Hello @Fatmice, looks like Proton hit an access violation (c0000005) immediately after As a side note, your log also has |
|
Yeah, no dice with taskset |
|
Got AMD 6800XT, used a few proton versions and Vulkan API in options but the actual gameplay is mostly black screen with some UI elements. Not sure whats wrong. Can other people use vulkan api? I'd prefer that vs dx12. UPDATE: Running on low settings works, something is breaking with amdgpu on higher setting. Search mode activated.... It was temporal AA, turning it on blacks out 3d components of game basically. |
|
Vulkan reportedly performs badly even on Windows, no reason to think it would be better on Linux. I've only tried DX11 and DX12, the latter one works for me (finally) but I've had the game hang and crash some time into the skirmish. Using GloriousEggroll's 5.9-GE-ST-8 unofficial patch. |
|
Was testing with Proton GE 6.16-1 and noticed DX12 nor Vulkan would work (nasty crashes and freezes), only DX11 would work. ALSO the launcher did not render so I was forced to use /nolauncher to bypass it. Things seem to work in 5.9-GE-ST-5 (and probably some other versions) for dx11 and dx12 although it can be finicky at times. DX12 MAY offer some better minimal fps performance over DX11 but its negligible. Updating 5.9-GE-ST-5 with latest dxvk and vkd3d helped a little bit with performance and had no bad effects. I only used %command% /nolauncher for my launch options; nothing else needed. (for DX11 and DX12 options). Pretty sure Vulkan in this game is 100% borked so nobody should bother with that. UPDATE: I was wrong, it seems you just need to wait a good 10-30seconds when loading up under DX12, if you minimize beforehand, bad things happen. (proton-GE-6.16-1) |
|
@jarrard https://gitlab.freedesktop.org/mesa/mesa/-/issues/3862 Yes, Vulkan backend of this game known to be borked. On prop drivers such as AMD prop VLK and likely Nvidia it works due to tons of app specific workarounds. |
|
Version 3.11 introduced audio crackle, which wasnt present in the previous version. Choosing the previous version (3.10.191346) in the beta section allows me to launch the game without audio crackle. |
and others
Compatibility Report
System Information
I confirm:
steam-507490.log
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;
The text was updated successfully, but these errors were encountered: