Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Space Engineers - 244850 #1792

Open
MagicRB opened this issue Oct 20, 2018 · 463 comments

Comments

@MagicRB
Copy link

commented Oct 20, 2018

The latest version of Space Engineers from steam, with app id 244850 seems to require a patch which wine-staging has.

Yes, I did leave out my system specs as it's not important to this issue. (Proton 3.16)

I confirm:

  • that I haven't found an existing compatibility report for this game. (Not specifically for this game, and not specifically this error, though it can be seen as a fixme)
  • that I have checked whether there are updates for my system available.

Symptoms

Space Engineers uses the GetCurrentPackageId function. SE crashes with en error, which says that the function was invoked with an incorrect parameter. This is caused by a bug in wine which has been ignored, wine-staging does include a patch to solve this problem. I'm not experienced enough to submit a pull request, nor I'd be able to compile proton as I'm kind of incompetent.

Reproduction

Reproduction is really easy, download Space Engineers from steam, install .net 4.7 as described here. After a successful installation of .net and with transform feedback working, you should get an error message like this

Unhandled Exception: 00bb:fixme:ver:GetCurrentPackageId (0x53a800 (nil)): stub System.ArgumentException: Parameter is not valid. at System.Drawing.Image.get_Flags() at System.Windows.Forms.ControlPaint.IsImageTransparent(Image backgroundImage) at System.Windows.Forms.Control.set_BackgroundImageLayout(ImageLayout value) at Sandbox.MyMessageBoxCrashForm.InitializeComponent() at Sandbox.MyMessageBoxCrashForm..ctor(String gameName, String logPath) at Sandbox.MyErrorReporter.ReportGeneral(String logName, String gameName, String id) at Sandbox.MyCommonProgramStartup.PerformReporting() at SpaceEngineers.MyProgram.Main(String[] args) wine: Unhandled exception 0xe0434352 in thread bb at address 0x7b44b08c (thread 00bb), starting debugger... Unhandled exception: 0xe0434352 in 64-bit code (0x000000007b44b08c).

This can easily be solved by either getting the patch upstream to wine (there might be a good reason why it's not upstream) or we could apply the patch directly to proton.

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 20, 2018

BTW I can confirm that Space Engineers does, in fact, work with wine, as I was able to start SE with wine-staging 3.18 without dxvk. It does crash as the wined3d11 API was not capable of running SE for long enough to actually play, it seemed to crash at random points in time, but this does indicate to me that SE should be functional, once we patch proton.

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 21, 2018

I tried locating the patch that makes it work under wine-staging, but I was not able to do so. I'm either completely blind or it doesn't exist. It may be that the function not working is a bi-product of some other bug. I'll continue searching

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 21, 2018

Now I have figured out that SE does crash because of something different, and that function is broken on both wine versions, now I shall figure why does it crash in the first place.

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 21, 2018

I have decompiled SE and I have figured out where is the problematic code path, it seems that SE thinks that '-report' was passed as a command line argument, but from what I understand from the decompiled source, there should not be a reason for SE to think that.

@PeacheyMcKeitch

This comment has been minimized.

Copy link

commented Oct 22, 2018

Ive posted a link to this thread onto the official Space Engineers support page. Will see if anyone over there has any ideas.

Also go upvote that thread on there forum to try get there attention incase its a SE and not a wine issue!

https://support.keenswh.com/spaceengineers/general/topic/improve-compatibility-with-steam-play-and-proton-linux-mac

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 23, 2018

No, you misunderstood me, let me explain a bit more. SE uses .NET 4.7.1 which IS broken in wine, but it can be made to run with a workaround and a bit of luck. Here is the workaround needed. Then, SE uses Stream Output / Transform Feedback, which is a deprecated feature in DX11, and was probably carried over from the DX9 renderer, which SE has used in the past. Now, Vulkan has recently received this extension "VK_EXT_transform_feedback", which allows Stream Output to work in Vulkan, therefor DXVK now supports Transform Feedback, therefor SE should work in wine, but wine still needs patches to expose this extension. Proton has these patches already, I think, I'm not sure, don't quote me. Mainline wine will get at the next release at it has been already staged which means wine-staging will get it too. Now wine-staging has a patch in place which enables SE to start under opengl, it still crashes as opengl is not capable of sustaining the graphics engine. The problem in proton is not related to Transform Feedback. I can't identify the patch that is responsible for this, as I actually do not know what's the problem. I have decompiled SE and looked at the code which is causing the crash, based on the stacktrace provided by the .net runtime and do not see a clear reason why it crashes. I'll post the relevant functions later.

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 23, 2018

I know, it tries to notify the user that they should update their graphics drivers. That's why it tries to report something. But still, it does work in wine-staging, so we still need to find the relevant patch.

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 23, 2018

Can someone help? I'm not sure what to look for in those patches.

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 23, 2018

https://stackoverflow.com/questions/11796082/invalid-parameter-when-setting-an-image and this seems to be related, I'm not any closer to figuring this out tho.

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 23, 2018

line 914 seems to be the problem, that's the only thing that i can see, the GdiPlus.dll is a wine native dll as can be seen here

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 23, 2018

GetGdiImageFlags returns invalid parameter if image or flags are empty, as can be seen here, line 5219, so it's probably getting nullified either somewhere in .net or when being passed to the native library from wine.

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 23, 2018

I think I found it, if I'm understanding this correctly,

GpStatus WINGDIPAPI GdipGetImageFlags(GpImage *image, UINT *flags)
{
    TRACE("%p %p\n", image, flags);

    if(!image || !flags)
        return InvalidParameter;

    *flags = image->flags;

    return Ok;
}

this function should not check if flags is 0, as flags is the output variable, which can be whatever.

@MagicRB

This comment has been minimized.

Copy link
Author

commented Oct 23, 2018

I am completely wrong in my last comment, I hate pointers. Anyways, I'm going back up the stacktrace trying to find out why image is null.

@SpookySkeletons

This comment has been minimized.

Copy link

commented Oct 26, 2018

I am not sure on the legal ramifications but Space Engineers provides a visible/ open EULA of their source code on github, if you can look through, so you don't have to decompile.
Might be worth a look through if it's kosher, to figure out what is blowing up and commit to wine.

https://github.com/KeenSoftwareHouse/SpaceEngineers/blob/master/EULA.txt

Edit:
They do have an intertoperability clause which wine falls under as 'compatibility'

@aaronfranke

This comment has been minimized.

Copy link

commented Oct 28, 2018

Please wait a few months until Valve updates the version of Wine that Proton uses. Valve has some patches on top of Wine and needs to test for stability, so there are reasons that Valve does not immediately update the version of Wine that Proton uses.

@SpookySkeletons That source code has not been updated since 2016.

@SpookySkeletons

This comment has been minimized.

Copy link

commented Nov 1, 2018

@aaronfranke
This affects Vanilla wine as well as Proton, whichever arrives first can upstream it to the other.
Space Engineers has been a major pain for years in any sort of wrapper, even when it did work it was stable as a two legged stool.

Perhaps I just don't know how any of this works but this might be something to look into.

6421.401:0031:0032:trace:module:load_dll Loaded module L"C:\windows\assembly\NativeImages_v4.0.30319_64\mscorlib\386b8793866138dad77588a7399d11c3\mscorlib.ni.dll" (native) at 0x64478000000
The library loads up at 0x64478000000
Some kind of function turns and burns here, sharing a very close trailing memory space with mscorlib.ni.dll:

6421.486:0031:0032:trace:seh:RtlVirtualUnwind type 0 rip 64478454d69 rsp 53b5d0
6421.486:0031:0032:trace:seh:dump_unwind_info **** func 454cf0-454da3
6421.486:0031:0032:trace:seh:dump_unwind_info unwind info at 0x644785364bc flags 3 prolog 0x10 bytes function 0x64478454cf0-0x64478454da3
6421.486:0031:0032:trace:seh:dump_unwind_info 0x10: subq $0x68,%rsp
6421.486:0031:0032:trace:seh:dump_unwind_info 0xc: pushq %rbx
6421.486:0031:0032:trace:seh:dump_unwind_info 0xb: pushq %rsi
6421.486:0031:0032:trace:seh:dump_unwind_info 0xa: pushq %rdi
6421.486:0031:0032:trace:seh:dump_unwind_info 0x9: pushq %r12
6421.486:0031:0032:trace:seh:dump_unwind_info 0x7: pushq %r13
6421.486:0031:0032:trace:seh:dump_unwind_info 0x5: pushq %r14
6421.486:0031:0032:trace:seh:dump_unwind_info 0x3: pushq %r15
6421.486:0031:0032:trace:seh:dump_unwind_info 0x1: pushq %rbp
6421.486:0031:0032:trace:seh:dump_unwind_info handler 0x644783da000 data at 0x644785364d8

@Guy1524

This comment has been minimized.

Copy link

commented Nov 1, 2018

It looks like mscorlib.ni.dll is a component for the .NET framework, which is known for being unstable under wine. You might have luck using winetricks to fiddle around with dotnet, but hopefully Ethan Lee will devise a better solution in the future.

@kisak-valve kisak-valve added the .NET label Dec 13, 2018
@FurretUber

This comment has been minimized.

Copy link

commented Dec 17, 2018

With Mesa 18.3.1 with patches applied from here applied to support Transform Feedback and using winetricks to install .NET 4.7.2 I got very close of having the game working using DXVK. The game reached the main menu, running at 120 FPS, and the mouse cursor loads. However, the game crashes before the background video and the menu buttons appear.

The log messages seem to be pretty relevant on this case. The DXVK warn seems closely related to what happened with Wine:

SpaceEngineers_dxgi.log

SpaceEngineers_d3d11.log

steam-244850.log.gz

SpaceEngineers.log

VRageRender-DirectX11.log

My system information. Please note this is showing a different Mesa version because the 32-bit and the 64-bit Mesa builds are distinct right now.

@MagicRB

This comment has been minimized.

Copy link
Author

commented Dec 17, 2018

I've managed to get to gameplay with wine-staging, dxvk, proprietary nvidia drivers. All voxels were horribly malformed and i haven't managed to reproduce it since wine updated.

@SpookySkeletons

This comment has been minimized.

Copy link

commented Dec 18, 2018

@FurretUber
The latest version of the game locks up after a minute or more. Opt down to the multiplayer overhaul in the beta tab and it will work.

@steve7233

This comment has been minimized.

Copy link

commented Mar 5, 2019

I just upgraded my GC to NVIDIA GeForce GTX 1060 and all my steam games work via steamplay except SE. I press play and SE tries to start then stops. No error message, no sound, and no game window. I have tried all the proton versions that steamplay will run. After reading this thread I at least know that many people are trying to figure it out. Sounds like a new version of proton and wine are needed. I was hoping I could use wintricks or something but it might be more complicated. That's a bummer. Maybe a lib or several libs with winecfg?

@Maltahl

This comment has been minimized.

Copy link

commented Mar 16, 2019

This game can launch with wine 4.3 and DXVK 1.0 - But you will need .NET 4.7.2 as additional installation.
Lutris installer for the game works flawlessly for new installations.
If you have a current installation of space engineer it might not work, i have yet to figure out why that is the case.
After that you can play the game but minor errors will still be there such as:

  • Crashing when you fly crafts into other crafts or rocks at 20+m/s (report tool for SE appears)
  • After splash screen you have to click the mouse a couple of times to get to the main menu since the cinematic wont play else you just have a black screen.
  • Minor audio stutters which was mostly fixed with wine 4.3 but will get better as faudio gets futher development.
  • Slow loading screens in the beginning due to new shaders need to be cached.

Pastebin here of logs when running and crashing into a planet that crashes the game.
https://pastebin.com/tPC8y3tK

@jarrard

This comment has been minimized.

Copy link

commented Mar 20, 2019

I take it that the latest proton beta isn't wine4.3 yet? which is why it won't work via steam directly?

@FurretUber

This comment has been minimized.

Copy link

commented Mar 20, 2019

I managed to make Space Engineers working. It is definitively not on a good shape, but it works. I had to:

  1. Install dotnet472 on Space Engineers WINEPREFIX;
  2. Build FAudio with xWMA support and libraries on non-default directories. This FAudio build must work with Megadimension Neptunia VIIR;
  3. Make the built libFAudio.so be used for Space Engineers, be replacing the Proton one from lib64 or LD_PRELOAD;
  4. Make sure video drivers support Transform Feedback, as Mesa 19.1.0-devel for Intel Gen9;
  5. Be sure the built FAudio library built WILL NOT work! It can't find the needed libraries when starting Space Engineers;
  6. Space Engineers should work but with no sound.

There are a few bugs related to graphics as opening video that does not load, on edges that effect because of helmet is buggy, even then it is great considering the GPU is an Intel HD Graphics 520 and had bugs on Windows 10 until very recently.

A lot of bugs regarding terrain generation are happening, all planets and moons are hellish landscapes.

Images:

Captura de tela_2019-03-17_23-00-38

Captura de tela_2019-03-17_22-16-08

unknown (4)

@jarrard

This comment has been minimized.

Copy link

commented Mar 20, 2019

I sort of got it working but fps was real slow at menu (never bothered to play) and audio is crackling. I used https://github.com/Kron4ek/FAudio-Builds but perhaps it failed to install correctly.

EDIT: Didn't install faudio this time around, and no sound so I must have installed it correctly. Perhaps the main menu just does that because it works but as you point out, the terrain generation is completely messed up.

@Maltahl

This comment has been minimized.

Copy link

commented Mar 24, 2019

@MagicRB

This comment has been minimized.

Copy link
Author

commented Mar 24, 2019

@jarrard

This comment has been minimized.

Copy link

commented Mar 24, 2019

Copied wine4.4 faudio protonified into my custom steam compat folder, reinstalled game and dotnet472, loaded up, no audio.
Game looks like it might run better but it has this stuttering going on, maybe the non functional audio is to blame.
Anyway didn't seem to fix my audio issue, probably need to install precompiled bins from somewhere into the custom proton folder, I'm on arch so likely ones compiled on other distros won't work.

EDIT: I built custom faudio with ffmpeg support, still no luck with sound, probably doing something wrong, shrug. Anyway game is unplayable IMO, all planet bases maps don't work/broken, has stuttering & crashing.. Maybe one day.

@CrafterSvK

This comment has been minimized.

Copy link

commented Oct 7, 2019

Well, steam shouldn't run on nvidia graphics when bumblebee is used. I installed nvidia-xrun everything works fine and stable. 70 fps at lowest settings with 950M

@Linux74656

This comment has been minimized.

Copy link

commented Oct 7, 2019

@CrafterSvK Good to hear! Glad it works well!

@cpw

This comment has been minimized.

Copy link

commented Oct 9, 2019

Everything runs nice and smooth, visually, however there is a very perceptible audio crackle, and it's quite distracting - both the music and the ingame sfx have the problem..

@jarrard

This comment has been minimized.

Copy link

commented Oct 9, 2019

The audio problems have been discussed extensively in this discussion and there are solutions to reduce the problem. Just need to read above your post! for the most part using faudio for many works, sometimes you need to fiddle with pulse audio sync timings also.

@InflexCZE

This comment has been minimized.

Copy link

commented Oct 9, 2019

@Linux74656 Prolly should be added to the guide too

@Linux74656

This comment has been minimized.

Copy link

commented Oct 9, 2019

Got it! The issues section of the guide has been updated!

@cpw

This comment has been minimized.

Copy link

commented Oct 9, 2019

Update: The PULSE MSEC thing didn't work for me. It looks like I have an older sound card that doesn't properly support the glitchless pulse playback (TIL!). I found alternative instructions here: https://www.reddit.com/r/wine_gaming/comments/83j0mh/wine_and_pulse_audio_latency/dvk60mp/

Basically, change the pulseaudio config to load with tsched=0 and smaller (apparent) fragments makes the audio sound perfect. This now gets a gold rating on proton. Brilliant stuffs. 6 months ago I tried and it couldn't even start. 👍

@roothorick

This comment has been minimized.

Copy link

commented Oct 10, 2019

There are issues with keyboard focus when in fullscreen (even in "windowed fullscreen"). If I try to switch to another window/app, the game immediately reclaims keyboard focus. This is a bit of an issue when copy/pasting ingame scripts from an outside editor. The workaround I found is to temporarily switch to a window when I need to get out of the game.

However, the clipboard DOES work, and it does look like ingame scripts are 100%.

@InflexCZE

This comment has been minimized.

Copy link

commented Oct 10, 2019

As requested earlier, we now have special channel dedicated to SE on Linux on our official KSH Discord. Feel free to join us there:
https://discord.gg/keenswh

@LtSich

This comment has been minimized.

Copy link

commented Oct 10, 2019

Just for information, I have far better result with xact against faudio.
On the last test I have installed xact and xact_64.
And I have made the change mentionned here : https://www.reddit.com/r/wine_gaming/comments/83j0mh/wine_and_pulse_audio_latency/dvk60mp/

And honestly the game run very very well.
Few audio bug when I start the game, and after few minutes all is running fine.

With faudio I have some strang audio lag, it's very annoying.
And it seem to impact performance.

Maybe this depend on the hardware or the system, I don't know...
But people who have trouble with faudio should try with xact.

@Gwindalmir

This comment has been minimized.

Copy link

commented Oct 10, 2019

There are issues with keyboard focus when in fullscreen (even in "windowed fullscreen"). If I try to switch to another window/app, the game immediately reclaims keyboard focus. This is a bit of an issue when copy/pasting ingame scripts from an outside editor. The workaround I found is to temporarily switch to a window when I need to get out of the game.

However, the clipboard DOES work, and it does look like ingame scripts are 100%.

That's actually a problem on Windows too, so nothing Wine/Proton/Linux specific.
There's a few bug reports floating around somewhere on that problem.
It's very nice when I switch to notepad or discord to type something, and the game starts triggering a bunch of actions too. /s

@InflexCZE

This comment has been minimized.

Copy link

commented Oct 10, 2019

We've found the issue on Windows and it'll ship with next patch of the game.
Hopefully it'll fix the issue on Linux as well.

@Linux74656

This comment has been minimized.

Copy link

commented Oct 10, 2019

I modified the guide and wrote a new(heavily modified the old one) autopatcher to fulfill a different purpose, it will now patch the config file for you, then (try to) create the prefix. It should be at least mostly functional. Hopefully this will help reduce confusion on prefix creation for some of the newer or inexperienced users.

@matty-r

This comment has been minimized.

Copy link

commented Oct 11, 2019

After using the autopatcher i'm able to launch and play - however it hitches every 2 seconds or so. Using the full DXVK hud it shows a red line in the graph every time it hitches. Other than that, I get around 70-90 fps on Earth.

i7 6700k, 1080ti, 32gb DDR4 3200mhz

@StripedMonkey

This comment has been minimized.

Copy link

commented Oct 11, 2019

Did it look like This?

@matty-r

This comment has been minimized.

Copy link

commented Oct 11, 2019

Did it look like This?

Yea it does, where do you set that?

@jarrard

This comment has been minimized.

Copy link

commented Oct 11, 2019

its mentioned how, just read down a few posts. you use the steam launch command thing.

@matty-r

This comment has been minimized.

Copy link

commented Oct 11, 2019

its mentioned how, just read down a few posts. you use the steam launch command thing.

Yea sorry, it was hidden (#1792 (comment))

@matty-r

This comment has been minimized.

Copy link

commented Oct 11, 2019

Set my launch options to: MONO_GC_PARAMS=nursery-size=32m,minor=simple-par DXVK_HUD=full PULSE_LATENCY_MSEC=60 %command%

Still getting it, here is what the graph looks like:

image

@LtSich

This comment has been minimized.

Copy link

commented Oct 11, 2019

I think this is only usefull with mono : MONO_GC_PARAMS=nursery-size=32m,minor=simple-par
Did you try to build your prefix with xact instead of faudio ?
I have far better performance with xact... Faudio I have the exact same issue that you...

@InflexCZE

This comment has been minimized.

Copy link

commented Oct 11, 2019

Yes, it's only for mono.

@matty-r please check if autopatcher executed steps 3&4 correctly (e.g. the GC server is present in your config) https://github.com/Linux74656/SpaceEngineersLinuxPatches/blob/master/README.md#step-3

@matty-r

This comment has been minimized.

Copy link

commented Oct 12, 2019

Yes, it's only for mono.

@matty-r please check if autopatcher executed steps 3&4 correctly (e.g. the GC server is present in your config) https://github.com/Linux74656/SpaceEngineersLinuxPatches/blob/master/README.md#step-3

That's what did it. Just needed to add gcServer enabled="true" to the .config file. Works perfectly now. Amazing.

Thanks.

@InflexCZE

This comment has been minimized.

Copy link

commented Oct 12, 2019

@matty-r If autopatcher failed for some reason it would be good to know why so it can be fixed for others. Any error messages when you applied it? Also, can you tell us full path to the config file on your system? Apparently the path differs on some systems.

@matty-r

This comment has been minimized.

Copy link

commented Oct 13, 2019

@matty-r If autopatcher failed for some reason it would be good to know why so it can be fixed for others. Any error messages when you applied it? Also, can you tell us full path to the config file on your system? Apparently the path differs on some systems.

I tried re-running it, but it looks like it applies the gcServer setting now - bit odd. It did however stop working completely after I re-ran it and would just show the crash report dialog after the splash screen. I had to manually re-add gcServer, and deleted KSH.wmv .

So not really sure why it broke the first time around - the path matches the concatenated string in the Python script file.

@duckinator

This comment has been minimized.

Copy link

commented Oct 13, 2019

I just successfully got Space Engineers working pretty easily on Linux, using a little bash script based on @Linux74656's Python script.

I'm running Fedora 30 on a system with an AMD RX 580 GPU.

Of note is that I actually couldn't get it to work unless I didn't install vcrun2015.

Here's what you do:

  1. In your Steam library, right click Space Engineers -> properties -> check "Force the use of a specific Steam Play compatibility tool" and choose "Proton 4.11-7", then click close.
  2. Install SE.
  3. Start SE, wait for the error about an outdated library, click OK. SE should create a wine prefix when it does this.
  4. Go to a Bash shell, and run the command below.
  5. If everything in step 3 succeeds, start SE. It should work now.

Bash command for step 3:

export WINEPREFIX=~/.steam/steam/steamapps/compatdata/244850/pfx && winetricks --force -q d3dcompiler_47 && winetricks --force -q faudio && winetricks --force -q dotnet48 && winetricks --force -q winxp && sed -i 's/<runtime>\r\?$/<runtime> <gcServer enabled = "true"\/>/' ~/.local/share/Steam/steamapps/common/SpaceEngineers/Bin64/SpaceEngineers.exe.config && mv ~/.local/share/Steam/steamapps/common/SpaceEngineers/Content/Videos/KSH.wmv{,.bak}
@roothorick

This comment has been minimized.

Copy link

commented Oct 13, 2019

That seems overkill. All I really had to do is launch game and let it error (to generate the initial prefix), protontricks 244850 -q dotnet472 xact, manually edit SpaceEngineers.exe.config, and it Just Works(TM).

Of note this didn't seem to work with Proton 4.2, but I wanted to use 4.11 by default anyway.

Hold on, you're specifically trying to use FAudio, aren't you? I missed that. d3dcompiler_47 or winxp shouldn't be necessary, though. (I'm surprised winxp doesn't break the game, to be honest.)

@StripedMonkey

This comment has been minimized.

Copy link

commented Oct 13, 2019

Windows XP is required to get the game to run. I've been unable to get it to work on Windows 7 or above.

@InflexCZE

This comment has been minimized.

Copy link

commented Oct 13, 2019

Hello @duckinator, I'm glad that the game runs well for you.

Currently we have another user over on our Discord that's having problems with winetricks on Fedora (Line 443):
https://pastebin.com/5Y1s7xjG

Can you share with us what version of winetricks you use?

@duckinator

This comment has been minimized.

Copy link

commented Oct 13, 2019

@roothorick based on your comment, I deleted the wine prefix so I could try again.

Turns out, this is enough to make it work for me:

WINEPREFIX=~/.steam/steam/steamapps/compatdata/244850/pfx winetricks -q dotnet48 xact && sed -i 's/<runtime>\r\?$/<runtime> <gcServer enabled = "true"\/>/' ~/.local/share/Steam/steamapps/common/SpaceEngineers/Bin64/SpaceEngineers.exe.config

Adding the -skipintro launch option to Space Engineers isn't required, but makes it so it skips the startup video which doesn't play. If you don't set that option, it plops you at a black screen and you need to click or press a key to continue.


@InflexCZE here's wine + winetricks version info:

~$ wine --version
wine-4.17 (Staging)
~$ winetricks --version
20190912 - sha256sum: 31d37bf18f1503ec46cedf8889e447901e746454e9c3de465f9cc57193e0c90b
~$

My simplified one above may work better, just due to doing fewer things. Also, they'll probably want to run rm -rf ~/.steam/steam/steamapps/compatdata/244850/ and then re-run the game once (to get it to regenerate the wine prefix) before trying again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.