Endless Space 2 (392110)

[luisXoliveira]

Compatibility Report

• Name of the game with compatibility issues: Endless space 2
• Steam AppID of the game: 392110

System Information

• GPU: RX480

• Driver/LLVM version: Mesa 18.2.4

• Kernel version: 4.15

• Link to full system information report as Gist: steam-392110.log

• Proton version:3.16.4

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 game crashes when I try to start it.

Reproduction

every time at i try to launching the game he stuck in the load screen

[Jimmy1500]

Issue:

• Endless space 2 crashes on start

System Information:

• GPU: Nvidia GTX 1070
• Driver Version: 410.78
• OS: Ubuntu 18.04 LTS
• Kernel: 4.15.0
• Proton version: 3.16-5 beta

Symptoms:

• Game crashes when one tries to play using steam play, error log is attached. 2018-12-15_121124.zip

I can confirm that:

• [x] I have verified that all available updates for my system and steam are applied before attempting to start the game.

[zzhiyi]

GPU: Intel UHD 630.

I haven't had any crashes. Although it took longer than I expected to load.(a few minutes)

[igo95862]

DXVK causes the amdgpu driver to crash.

Using WINE3D11 will NOT crash driver

Proton version: 3.16-6

Gist with system information.

Gist journalctl log

I have not tested it with mesa-git or llvm-svn

[kisak-valve]

Hello @igo95862, it may be worthwhile to mention your issue to your video driver vendor if it has not been already.

[hakzsam]

Can't be reproduced with latest mesa/llvm (git) on my RX480. Can you try to upgrade ?

[vmatare]

So to clarify what @igo95862 wrote:

I get the following e.g. in ~/.local/share/Steam/steamapps/common/Endless Space 2/2019-02-03_155122/output_log.txt:

Initialize engine version: 5.5.1p4 (70301f5c2872)
GfxDevice: creating device client; threaded=1
d3d11: failed to create D3D11 device (0x80004005)
GfxDevice: creating device client; threaded=1
Crash!!!
[...]

And that is fixed by putting the following in the game's launch options: PROTON_USE_WINED3D11=1 %command%

[kisak-valve]

Hello @vmatare, just to check, does any vulkan application like vulkaninfo work?

[vmatare]

Huh... This is interesting. So I had disabled vulkan support throughout my system, i.e. mesa was built without it. Now that I enabled it, EL2 does start up without the PROTON_USE_WINED3D11=1, but then it freezes the GPU on completion of the loading screen. After that, the kernel remains responsive, i.e. I can use SysRQ to emergency-sync and to soft-reset the system, but the display remains frozen. I have a Radeon RX 480 with the opensource amdgpu driver 18.1.0, mesa 18.3.1, running Linux 4.20.5 currently. I'll play around with the configuration of the vulkan-related stack a bit and see if I can't get it to run with vulkan support. The graphics did feel slightly sluggish with D3D11 now that I think back ;-)

[asazernik]

I seem to be hitting the same error as @luisXoliveira, judging from my PROTON_LOG. @luisXoliveira inserted the PROTON_LOG instead of the system information report, so here's mine

I believe the relevant lines from the proton log are:

156747.329:0023:002b:trace:module:MODULE_InitDLL (0x7a850000 L"opengl32.dll",THREAD_ATTACH,(nil)) - CALL
156747.329:0023:002b:trace:module:MODULE_InitDLL (0x7a850000,THREAD_ATTACH,(nil)) - RETURN 1
156747.329:0023:002b:trace:module:MODULE_InitDLL (0x7fb0e29f0000 L"ws2_32.dll",THREAD_ATTACH,(nil)) - CALL
156747.329:0023:002b:trace:module:MODULE_InitDLL (0x7fb0e29f0000,THREAD_ATTACH,(nil)) - RETURN 1
156747.329:0023:002b:trace:module:MODULE_InitDLL (0x180000000 L"mono.dll",THREAD_ATTACH,(nil)) - CALL
156747.329:0023:002b:trace:module:MODULE_InitDLL (0x180000000,THREAD_ATTACH,(nil)) - RETURN 1
156747.329:0023:002b:trace:seh:NtRaiseException code=406d1388 flags=0 addr=0x7b44af1c ip=7b44af1c tid=002b
156747.329:0023:002b:trace:seh:NtRaiseException  info[0]=0000000000001000
156747.329:0023:002b:trace:seh:NtRaiseException  info[1]=000000014108f680
156747.329:0023:002b:trace:seh:NtRaiseException  info[2]=000000000000002b
156747.329:0023:002b:trace:seh:NtRaiseException  rax=000000000311fca0 rbx=0000000000000000 rcx=000000000311fca0 rdx=000000000311fcc0
156747.329:0023:002b:trace:seh:NtRaiseException  rsi=000000000311fd98 rdi=000000000311fcd8 rbp=000000000311fd50 rsp=000000000311fc80
156747.329:0023:002b:trace:seh:NtRaiseException   r8=0000000000000003  r9=000000000311fd80 r10=0000000000000008 r11=0000000000000246
156747.329:0023:002b:trace:seh:NtRaiseException  r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000
156747.329:0023:002b:trace:seh:call_vectored_handlers calling handler at 0x180133600 code=406d1388 flags=0
156747.329:0023:002b:trace:seh:call_vectored_handlers handler at 0x180133600 returned 0
156747.329:0023:002b:trace:seh:dwarf_virtual_unwind function 7b44af1c base 0x7b44aeb0 cie 0x7b6356b8 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aeb0: DW_CFA_def_cfa %rsp, 8
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aeb0: DW_CFA_offset %rip, -8
156747.329:0023:002b:trace:seh:dwarf_virtual_unwind fde 0x7b644330 len 34 personality (nil) lsda (nil) code 7b44aeb0-7b44af45
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aeb0: DW_CFA_advance_loc 1
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aeb1: DW_CFA_def_cfa_offset 16
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aeb1: DW_CFA_offset %rbp, -16
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aeb1: DW_CFA_advance_loc 6
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aeb7: DW_CFA_def_cfa_register %rbp
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aeb7: DW_CFA_advance_loc 13
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aec4: DW_CFA_offset %rdi, -24
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aec4: DW_CFA_offset %rsi, -32
156747.329:0023:002b:trace:seh:execute_cfa_instructions 7b44aec4: DW_CFA_advance_loc1 93
156747.329:0023:002b:trace:seh:dwarf_virtual_unwind next function rip=000000014028d218
156747.329:0023:002b:trace:seh:dwarf_virtual_unwind   rax=000000000311fca0 rbx=0000000000000000 rcx=000000000311fca0 rdx=000000000311fcc0
156747.329:0023:002b:trace:seh:dwarf_virtual_unwind   rsi=0000000000000000 rdi=000000000137c9e0 rbp=000000000311ffd0 rsp=000000000311fd60
156747.329:0023:002b:trace:seh:dwarf_virtual_unwind    r8=0000000000000003  r9=000000000311fd80 r10=0000000000000008 r11=0000000000000246
156747.329:0023:002b:trace:seh:dwarf_virtual_unwind   r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000
156747.329:0023:002b:trace:seh:RtlVirtualUnwind type 1 rip 14028d218 rsp 311fd60
1

[vmatare]

Some updates later the game now runs stable for me, with vulkan support. I.e. I have no special launch options and I can play without crashes so far.

Current versions: xf86-video-amdgpu 19.0.1 mesa 19.0.1 proton 4.2 vulkan 1.1.101 Endless Space 2 V1.4.13

I can keep 3D accel enabled in my window manager, I can safely alt+tab out of the game, switch desktops and so on. Everything seems very stable.

[kisak-valve]

Hello, is anyone still seeing crashes with this game, Proton 4.2, and mesa 19.0+?

[hologhost]

Everything but videos work for me with proton 4.2, mesa 19.0 and a rx570.

[mvdstam]

@kisak-valve Just wanted to mention that although the game runs smoothly with the latest Proton version at the time of writing (4.11), there still are some issues that hopefully can by looked at:

• In-game videos don't work
• Many in-game screens such as the research screen, military screen and quests and evens screen seem to have completely black backgrounds (see example below)

Aside from these issues, the game seems to work perfectly for me.

[mvdstam]

@kisak-valve Since the new Steam UI release, Endless Space 2 doesn't seem to start at all. Also reported on ProtonDB.

[kisak-valve]

Hello @mvdstam, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

[mvdstam]

Hi @kisak-valve,

This is all that is logged:

======================
Proton: 1576654630 4.21-GE-2-8-geab983d
SteamGameId: 392110
Command: ['/home/max/.local/share/Steam/steamapps/common/Endless Space 2/EndlessSpace2.exe']
Options: set()
======================

That's it. The game simply exits immediately without further information. As you can see, I've tried it with the 4.21-GE-2 Proton version in this attempt, but the same result happens with any other Proton version.

[mvdstam]

Hi @kisak-valve, have you been able to determine the cause of the problem? Can I do anything else to help you fix this?

[rfliam]

I also see that this is unable to launch. The proton log is attached:

steam-208140.log

Endless Space (1) and a few others work. I am using nvidia OPTIMUS.

akmod-nvidia-440.44-1.fc31.x86_64

PROTON_LOG=1 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%

for launch options

[roypen]

The game runs on Fedora32, Flatpak version, Proton 5.0.7, Intel HD4000 but only with: PROTON_USE_WINED3D=1 %command% Without it, black background on Xorg or resolution change error on Wayland occur. Cinematics still don't work.

[DanMan]

Game generally works here, too, with Proton 5.0-10 and 5.13-6 but unfortunately it also freezes occasionally with both. I think it didn't freeze the first time I played it, which went for about 5h. Only ever after resuming from a savegame it started freezing IIRC. They're getting more frequent all the time, sometimes it just takes a few minutes. :-(

The cinematics work with ProtonGE 5.21-1, the mouse wheel sometimes doesn't work with Proton 5.10.

Edit: found out that using the -force-opengl parameter fixes the freezing.

[zaggynl]

When I probe a planet I used to get a short video about the planet, now I'm getting what appears to be a TV test screen? Proton 6.3-6

[kisak-valve]

Hello @zaggynl, what was the most recent Proton version you know rendered the video correctly?

Please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, 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.

[zaggynl]

Appears resolved after restarting Steam, sorry about that.

Edit: still shows now and then for some cutscenes, not sure what causes this?

[zaggynl]

Endless Space 2 appears to crash when using F12 for screenshots via Steam: Files as mentioned in dialog: crash.zip (dump file) error.log output_log.txt

System Information: https://gist.githubusercontent.com/zaggynl/cc0eb5cf0665164d972707b9be4d4fdf/raw/9788b8870635e2b70ab6c5edd378b0f0c1032c1c/gistfile1.txt

Proton log: steam-392110.log

[gerazov]

Awesome work guys :sunglasses:

I'm having issues with the cutscene playback as well. The videos were generally upside down and mirrored, and some were substituted with the color Test Screen. This subtracts from the game experience (and hurts the neck a bit :sweat_smile: ), but the game is fully playable.

However, after a recent upgrade (maybe the NVIDIA driver changed from 495.44 to 495.46) no cutscene plays at all, i.e. all are substituted for the color test screen. This is a major issue since there is a video that plays in the GUI in the empire/tech/military screens, and with the test color screen they're rendered useless:

This happens with Proton Experimental. With Proton 6.3-8 and 5.13-6 no videos play and the background in the UI is black like in @mvdstam case (usable but aesthetically unpleasing)

Here are my hardware specs:

Operating System Version:
    "Manjaro Linux" (64 bit)
    Kernel Version:  5.10.93-1-MANJARO
    X Server Release:  12101003
    X Window Manager:  KWin
    Steam Runtime Version:  steam-runtime_0.20211207.0

Video Card:
    Driver:  NVIDIA Corporation NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
    Driver Version:  4.6.0 NVIDIA 495.46
    OpenGL Version: 4.6

And the steam log: steam-392110.log

[KhamilloKing]

Aside from the already reported issue of test screens replacing all videos, the game crashes after a few turns on Proton 7.0-1, showing a window with "Error in gc" title and "Too many threads" message. Issue does not appear in Proton 6.3-8.

System info from neofetch Update with steam log, both issues reproduced with Proton 7.0-1: steam-392110.log

[KhamilloKing]

Aside from the already reported issue of test screens replacing all videos, the game crashes after a few turns on Proton 7.0-1, showing a window with "Error in gc" title and "Too many threads" message. Issue does not appear in Proton 6.3-8.

System info from neofetch Update with steam log, both issues reproduced with Proton 7.0-1: steam-392110.log

Both issues are now fixed in the bleeding-edge version of Proton Experimental. Cutscenes, however, are vertically mirrored. A trip to Australia, anyone?

Proton log: steam-392110.log

[DanMan]

The SEGA video on launch is all black for me here on Fedora 35 (newly created prefix, Proton 7 and Exp.), but I do hear its sound playing. wine64-preloader crashes on exit though, which is new compared to ProtonGE I mentioned above.

Sysinfo (Newer kernel and Nvidia driver by now though)

Funny thing is that videos keep working as they should, if I switch from ProntonGE (5.12 for example) to vanilla Proton 7 without deleting the prefix. Anyone know why?

[KhamilloKing]

Replying to https://github.com/ValveSoftware/Proton/issues/2014#issuecomment-1059850636

I believe that's because GE-Proton downloads and installs the codecs that Valve can't include directly to the separate prefix of the game. I've had an issue where running GE-Proton AFTER running the game with a vanilla version of Proton makes the game crash and the prefix unusable. That being said, make sure you have the bleeding-edge version of Proton Experimental (available by clicking the setting of Proton Experimental and selecting the bleeding-edge beta branch) and a clean prefix to test compatibility, as Valve can't offer support for GE-Proton issues.

[KhamilloKing]

Issue of vertically mirrored cutscenes persists as of today, with the bleeding-edge version of Proton and after a reinstall. I wouldn't know it, but I wonder if this could be a driver issue like gerazov mentioned (Currently using amdgpu open source driver) Gist with system info pulled from Steam Proton log: steam-392110.log