Ashes of the Singularity: Escalation (507490)

[ananace]

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.

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;

[andrebadaia]

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

[logan001]

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

[ananace]

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.

[logan001]

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

[logan001]

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

[HonkingGoose]

@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.

[flibitijibibo]

In addition to checking for xaudio2x, 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...

[7oxicshadow]

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/drivec/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

[7oxicshadow]

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%

[douglasg14b]

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.

[ananace]

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 <notifications@github.com 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 .

[douglasg14b]

@ananace So renaming the executable to StardockLauncher.exe overwriting it?

[7oxicshadow]

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%

[douglasg14b]

@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.

[7oxicshadow]

try renaming AshesEscalation_DX11.exe to StardockLauncher.exe instead

[douglasg14b]

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.

[7oxicshadow]

i assume you are using either the nvidia or amd binary drivers?

[douglasg14b]

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

[7oxicshadow]

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.

[ananace]

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 .

[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.

[iicurtis]

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.

[tatsujb]

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.

[douglasg14b]

A linux port will be great! Also funny seeing you here as well @tatsujb :smile_cat:

[tatsujb]

well.... RTS-ers are nothing if not devoted to the genre ;)

[logan001]

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

[7oxicshadow]

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

[douglasg14b]

@7oxicshadow How did you get proton 4.2-2? I don't see that option in my steam install.

[7oxicshadow]

I have seen that happen before. Force steam to check for updates (Steam > Check for steam client updates). It should find it.

[douglasg14b]

Got it.

Unfortunately Ashes still just crashes as soon as I hit play in the launcher 0n 4.2-2 :/

[7oxicshadow]

@douglasg14b I am assuming you have tried with and without PROTON_NO_ESYNC?

The only other place that will yield some possible information is the AshesEscalation_DX11_d3d11.log and the AshesEscalation_DX11_dxgi.log.

These are created by DXVK when launching the game. They are located in the same directory as the AshesEscalation executables. If you are having vulkan issues it will tell you the most likely cause in there.

[douglasg14b]

@7oxicshadow I'm running with PROTON_NO_ESYNC=1 yeah.

Here is what I see under `StardockLauncher_dxgi.log:

info:  Game: StardockLauncher.exe
info:  DXVK: v0.94-18-g3b3ccc8
warn:  OpenVR: Failed to initialize OpenVR
info:  Required Vulkan extension VK_KHR_get_physical_device_properties2 not supported
info:  Required Vulkan extension VK_KHR_surface not supported
info:  Required Vulkan extension VK_KHR_win32_surface not supported
err:   DxvkInstance: Failed to create instance

[kisak-valve]

Hello @douglasg14b, please verify you have vulkan drivers installed for your video card with something like apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386 and install them if they are not.

Also, looks like you've encountered https://github.com/ValveSoftware/steam-for-linux/issues/6093. Please opt into Steam's beta client and/or go to Steam -> Library dropdown -> Tools and install Proton 3.16 beta on the list.

[douglasg14b]

@kisak-valve

I didn't made mesa drivers installed, somehow. Installed them and it starts up! Doesn't look like Vulkan works though, only DX11.

Thanks!

[tatsujb]

@kisak-valve @douglasg14b @7oxicshadow stardock promissed a linux port of AOTS. trying to make it run on proton may be a waste of time :)

[ananace]

I was able to play a few hours with a Windows-using friend, so I think there's not actually all that much left to "make it run" so to speak.

And I can't imagine that work spent improving Ashes won't be useful for other applications, so I'm certainly all for it.

On Fri, 19 Apr 2019, 12:51 tatsujb, notifications@github.com wrote:

@kisak-valve https://github.com/kisak-valve @douglasg14b https://github.com/douglasg14b @7oxicshadow https://github.com/7oxicshadow stardock promissed a linux port of AOTS. trying to make it run on proton may be a waste of time :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/1479#issuecomment-484849974, or mute the thread https://github.com/notifications/unsubscribe-auth/AAECPPHDL5PE3SL6JRHKVL3PRGPZ5ANCNFSM4FVLEZLQ .

[tatsujb]

@ananace @d10sfan as you guys can see here : https://github.com/ValveSoftware/Proton/issues/1479#issuecomment-458227447 I ran it without much effort. it's just the performance is crap and I don't want the devs to get the impression that their port is "not needed"

[7oxicshadow]

@tatsujb If I run the benchmark on "crazy" I get 45 FPS as the average score which is really good under DX11. (That is with 6700k @ 4.5 with GTX 1070). It is pretty much perfect under Proton for me.

As for not wanting to put the devs off making a Linux port, you don't have to worry. They are not making the port for the home user, they are making it for Google stadia compatibility. On the steam discussion the devs mentioned that there was renewed interest in making a linux port but could not go into details, then Stadia was announced and the devs followed up with a statement effectively saying "now you can see why".

[7oxicshadow]

Just to clarify my statement above. Linux users will get support on home PC's because of Stadia. Not the other way round.

[tatsujb]

well to me it's worrysome stadia needs to be the reason why they're doing it rather than that they promised to in the first place.

I guess the positive attitude way of looking at it is at least now we have some sort of guarantee.

that being said if I understood correctly stadia is meant to use some form of proton/wine for non-ported games, is that correct?

[aufkrawall]

The game just works here in Proton 4.11-6 (also with fsync) and doesn't seem to show any issues with DXVK. However, when selecting the game's native Vulkan renderer, it complains about the driver not being compatible (refuses to start because of some silly driver version check?). This is the case with RX 570 8GB on radv, amdvlk-open and amdvlk-proprietary.

[Leopard1907]

Game regressed on Proton 4.11. It just doesn't work with 4.11. Tries to load the game then just hangs i think.

4.2 still works and even native vlk works but with a caveat. At least for once you have to use PROTON_USE_WINED3D=1 if you want to select native vlk from options and to be greeted with it. Without use wined3d option, it will always keep working on dx11.

rename StardockLauncher.exe to StardockLauncher.exe.bak rename AshesEscalation.exe to StardockLauncher.exe

Also have to be applied as noted on other messages. There are sound issues with the game as well ( workarounds exists on ProtonDB) but i just wanted to see if it does work with native vlk or not.

My launch options were like this after changing to native vlk and to be sure that is ( wined3d) needed for once:

PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 DXVK_HUD=version VK_INSTANCE_LAYERS=VK_LAYER_MESA_overlay

For changing native vlk at first you need this:

PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 DXVK_HUD=version VK_INSTANCE_LAYERS=VK_LAYER_MESA_overlay PROTON_USE_WINED3D=1

Once you have changed to native vlk , you won't need wined3d launch option anymore.

DXVK hud options are there because i just wanted to make sure i'm not on dxvk by any weird random nuisance caused by game.

Here are some logs:

steam-507490-tryingtochangevlk.log steam-507490-wined3d11.log

steam-507490-workswithnativevlk.log.tar.gz

My system info:

https://gist.github.com/Leopard1907/36697cb0a2e68465e648a9725c0a38a0

Screenshot of it when it does actually worked with native vlk , might not be possible on radv:

[kisak-valve]

Hello @Leopard1907, can you check if Proton 4.11-8 and the DirectX 11 backend behaves with WINEDLLOVERRIDES="dxgi=n" %command% in the game's launch options? If not, then re-add the no-esync/fsync options.

[Leopard1907]

Hi @kisak-valve , that is not a wine/dxvk dxgi regression. Simply game regressed on 4.11.

But i did what you've suggested anyway , game just silently dies.

Here are the logs:

steam-507490-dxvkdxgi.log steam-507490-nosync.log steam-507490-winedxgi.log

[green3g]

I'm running into similar issues I think. Here's my system info and logs:

https://pastebin.com/YiRUKCLb

Operating System: Manjaro Linux KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Kernel Version: 5.3.11-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4690K CPU @ 3.50GHz Memory: 15.5 GiB of RAM

Nvidia Graphics/GTX 970

``` [gregg@gregg-pc ~]$ inxi -Fx System: Host: gregg-pc Kernel: 5.3.11-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0 Desktop: KDE Plasma 5.17.3 Distro: Manjaro Linux Machine: Type: Desktop Mobo: Gigabyte model: Z97MX-Gaming 5 v: x.x serial: UEFI: American Megatrends v: F6 date: 09/18/2015 CPU: Topology: Quad Core model: Intel Core i5-4690K bits: 64 type: MCP arch: Haswell rev: 3 L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28009 Speed: 1304 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 2939 2: 2586 3: 3069 4: 2836 Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 Device-2: NVIDIA GM204 [GeForce GTX 970] vendor: Micro-Star MSI driver: nvidia v: 440.31 bus ID: 02:00.0 Display: x11 server: X.Org 1.20.5 driver: nvidia resolution: 2560x1080~60Hz OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 440.31 direct render: Yes Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Device-3: NVIDIA GM204 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 02:00.1 Device-4: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-6:3 Sound Server: ALSA v: k5.3.11-1-MANJARO Network: Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet vendor: Gigabyte driver: alx v: kernel port: d000 bus ID: 04:00.0 IF: enp4s0 state: down mac: fc:aa:14:96:7a:ea Device-2: Intel Wireless-AC 9260 driver: iwlwifi v: kernel port: d000 bus ID: 05:00.0 IF: wlp5s0 state: up mac: a4:c3:f0:85:c7:8a Drives: Local Storage: total: 2.15 TiB used: 1.74 TiB (81.1%) ID-1: /dev/sda vendor: OCZ model: ARC100 size: 223.57 GiB ID-2: /dev/sdb vendor: Western Digital model: WD20EZRZ-00Z5HB0 size: 1.82 TiB ID-3: /dev/sdc vendor: Kingston model: SV300S37A120G size: 111.79 GiB Partition: ID-1: / size: 100.58 GiB used: 79.52 GiB (79.1%) fs: ext4 dev: /dev/sdc2 ID-2: swap-1 size: 8.80 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdc3 Sensors: System Temperatures: cpu: 45.0 C mobo: 29.8 C gpu: nvidia temp: 53 C Fan Speeds (RPM): N/A gpu: nvidia fan: 0% Info: Processes: 211 Uptime: 1m Memory: 15.51 GiB used: 1.27 GiB (8.2%) Init: systemd Compilers: gcc: 9.2.0 Shell: bash v: 5.0.11 inxi: 3.0.36 ```

Steam log

``` >>> Adding process 2545 for game ID 507490 ERROR: ld.so: object '/home/gregg/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. >>> Adding process 2547 for game ID 507490 Game update: AppID 507490 "", ProcID 2545, IP 0.0.0.0:0 RecordSteamInterfaceCreation (PID 2545): SteamUser016 / User RecordSteamInterfaceCreation (PID 2545): SteamFriends013 / Friends RecordSteamInterfaceCreation (PID 2545): SteamUtils005 / Utils RecordSteamInterfaceCreation (PID 2545): SteamMatchMaking009 / Matchmaking RecordSteamInterfaceCreation (PID 2545): SteamMatchMakingServers002 / MatchmakingServers RecordSteamInterfaceCreation (PID 2545): STEAMUSERSTATS_INTERFACE_VERSION011 / UserStats RecordSteamInterfaceCreation (PID 2545): STEAMAPPS_INTERFACE_VERSION005 / Apps RecordSteamInterfaceCreation (PID 2545): SteamNetworking005 / Networking RecordSteamInterfaceCreation (PID 2545): STEAMREMOTESTORAGE_INTERFACE_VERSION010 / RemoteStorage RecordSteamInterfaceCreation (PID 2545): STEAMSCREENSHOTS_INTERFACE_VERSION001 / Screenshots RecordSteamInterfaceCreation (PID 2545): STEAMHTTP_INTERFACE_VERSION002 / HTTP ERROR: ld.so: object '/home/gregg/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. >>> Adding process 2552 for game ID 507490 RecordSteamInterfaceCreation (PID 2545): SteamUtils005 / Utils ERROR: ld.so: object '/home/gregg/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. >>> Adding process 2572 for game ID 507490 ERROR: ld.so: object '/home/gregg/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. >>> Adding process 2573 for game ID 507490 ERROR: ld.so: object '/home/gregg/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. >>> Adding process 2594 for game ID 507490 Setting breakpad minidump AppID = 507490 Steam_SetMinidumpSteamID: Caching Steam ID: 76561198080150525 [API loaded no] ERROR: ld.so: object '/home/gregg/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. >>> Adding process 2597 for game ID 507490 Game update: AppID 507490 "", ProcID 2597, IP 0.0.0.0:0 RecordSteamInterfaceCreation (PID 2597): SteamUtils007 / Utils RecordSteamInterfaceCreation (PID 2597): SteamUser017 / User RecordSteamInterfaceCreation (PID 2597): STEAMAPPTICKET_INTERFACE_VERSION001 / INTEL-MESA: warning: Haswell Vulkan support is incomplete wine: Unhandled page fault on read access to 00007F04E3527CB8 at address 00007F04E34D0000 (thread 005d), starting debugger... ERROR: ld.so: object '/home/gregg/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. >>> Adding process 2606 for game ID 507490 pid 2504 != 2503, skipping destruction (fork without exec?) Game removed: AppID 507490 "", ProcID 2597 Game 507490 created interface STEAMAPPTICKET_INTERFACE_VERSION001 / Game 507490 created interface SteamUser017 / User Game 507490 created interface SteamUtils007 / Utils Game 507490 method call count for IClientUser::GetAppOwnershipTicketExtendedData : 1 Game 507490 method call count for IClientUser::GetSteamID : 1 Game 507490 method call count for IClientUtils::GetAppID : 4 Game 507490 method call count for IClientUtils::GetConnectedUniverse : 1 Game 507490 method call count for IClientUtils::RecordSteamInterfaceCreation : 3 Uploaded AppInterfaceStats to Steam Exiting app 507490 No cached sticky mapping in ActivateActionSet.Installing breakpad exception handler for appid(steam)/version(1573780595) Installing breakpad exception handler for appid(steam)/version(1573780595) Installing breakpad exception handler for appid(steam)/version(1573780595) ```

[mfp20]

I'm having similar issues on "Code Vein" and "Ashes of the singularity":

• system information
• steam log

Any idea?

EDIT: it works, using Proton 4.2-9. No need of any extra env var, lib, parameter.

[iicurtis]

As with everyone else, my logs are similar and the game silently crashes on newer proton versions.

After looking into this, Proton 4.11-6 is the last working version. Specifically commit 46f1a6c is good while 526279b does not launch. This indicates either an update to wine mono 4.9.3 is the issue or there is a regression in wine between commit c2511e5a1a5b7f0937e60c879a5ef791c962f21b and commit 41c7d676d89d3aa3a4add4bedb1ec89c8a4d89f8.

I'm going to start bisecting those wine commits to see if I can pinpoint the regression.

Edit: Verified to be commit 526279b causing the problems. I'll have to start looking into what wine commit caused the regression.

2nd Edit: Compiling the latest Proton 5.0-2 with Wine at commit c2511e5a1a5 allows the game to run fine. Wine commit 93d2d86 crashes. The issue is somewhere between c2511e5a1a5 - 93d2d86.

Broken wine commit is somewhere between 1d72700 - 7510969.

[iicurtis]

The guilty commit is wine/242e003.

advapi32: Move registry functions to kernelbase.

Signed-off-by: Alexandre Julliard <julliard@winehq.org>
(cherry picked from commit c7548d6)

[7oxicshadow]

Nice. Now all you need to do is start bisecting down to the actual line that broke it :) (joke)

I was kind hoping that all of the functions that were moved from dlls/advapi32/registry.c to dlls/kernelbase/registry.c would all line up so that a diff tool would spot any obvious differences. This is not the case.

It looks like there is considerable changes between both implementations.

It might be possible to make an assumption that the problem lies with reading registry keys as if the keys were created using an old (working prefix) and then no longer work when moving to a newer prefix i am guessing that it is probably doing read processes during start-up.

[7oxicshadow]

For fun I had a go at launching the game with WINEDEBUG=+all turned on.

The game actually gets to the full screen image showing the ashes picture where it says "initialising assets" or whatever at the bottom of the screen. In the end I had to alt+f4 because the logfile was 17GB and i was rapidly running out of space!

The interesting thing is that the image doesn't show without WINEDEBUG. This either means that the crash happens that quick that the image doesn't have time to show normally or there is a genuine timing problem.