Linux74656 / SpaceEngineersLinuxPatches

A place to find some fixes to get Space Engineers running in Linux
140 stars 12 forks source link

problem loading objects. #43

Open Timyoshi opened 4 years ago

Timyoshi commented 4 years ago

So I am currently having issues getting SE (Space Engineers) to get back up and running. I used the script by just running it in the command line with the built in steam proton(5.13-1). I had this working for a few days till I got a warning about gpu drivers being out of date.

So... I just wiped the config and thought to start over. I was mostly playing online with friends and used single player to goof off so my saves weren't really important.

The SE patch script runs fine but when I try to start a new world I get this error or is stuck on the loading screen (see attached for error). I couldn't find any logs as well.

I have tried proton 5.0-9 , proton 5.13-1 in steam and used the dependencies for the patch script.

IMG_20201030_003417357

error text says "An error occurred while adding one or more objects. See log file for more details."

Unrelated: Also I can't seem to get the update gpu drivers error to happen again. But If I do encounter this again I will do a new issue.

Finally I am not too fimiliar with wine or the tricks tools and usually try to stick with official steam play supported titles or platinum titles according to protonDB. So any advice or lessons learned would be welcome.

Timyoshi commented 4 years ago

Sorry for the lighting on the image lol.

Linux74656 commented 4 years ago

I have not seen that error in a while. Could you post your log files, they are located by default at: /home/USERNAME/.steam/steam/steamapps/compatdata/244850/pfx/drive_c/users/steamuser/Application Data/SpaceEngineers/ There would be two logs SpaceEngineers_20201010_165028647.log and VRageRender-DirectX11_20200901_202121341.log (Note the numbers in the filename will be different for you)

Timyoshi commented 4 years ago

Sorry about the late response.

VRageRender log file VRageRender-DirectX11_20201030_004601965.log

Space engineer log SpaceEngineers_20201030_004600835.log

Linux74656 commented 4 years ago

Alright. Try verifying the integrity of your game files in steam.

Then delete your prefix folder, /home/twkj/.local/share/Steam/steamapps/compatdata/244850/pfx/ (Make sure you, if you have any, you make backups of the files like saves, and the like.)

Then run the Jar patcher again except this time only apply the patches, do not create the prefix yet. (So uncheck the first option, and make sure the middle three are checked, and leave the last one unchecked) After that is done, manually create your prefix with this command

WINEPREFIX="/home/twkj/.local/share/Steam/steamapps/compatdata/244850/pfx/" winetricks --force -q vcrun2015 faudio d3dcompiler_47 dotnet48

Timyoshi commented 4 years ago

Still get the same error when starting a game in SE.

The Jar patcher had this line in the console output. But the patcher reported that the run was good.

cp: cannot create regular file '/home/twkj/.local/share/Steam/steamapps/compatdata/244850/pfx/dosdevices/c:/windows/system32/x3daudio1_3.dll': Permission denieddaudio1_3.dll': Permission denied

Output of WHINEPREFIX command.

[twkj@desk ~]$ WINEPREFIX="/home/twkj/.local/share/Steam/steamapps/compatdata/244850/pfx/" winetricks --force -q vcrun2015 faudio d3dcompiler_47 dotnet48
Executing mkdir -p /home/twkj/.local/share/Steam/steamapps/compatdata/244850
------------------------------------------------------
You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Using winetricks 20200412 - sha256sum: 40ff4c67804584b73d4d36153e1f64ca426d739f1790bd748f5ded0865e8cc7f with wine-5.18 and WINEARCH=win64
Executing w_do_call vcrun2015
Executing mkdir -p /home/twkj/.local/share/Steam/steamapps/compatdata/244850
------------------------------------------------------
You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_vcrun2015 
------------------------------------------------------
Working around wine bug 37781 
------------------------------------------------------
------------------------------------------------------
This may fail in non-XP mode, see https://bugs.winehq.org/show_bug.cgi?id=37781
------------------------------------------------------
Using native,builtin override for following DLLs: api-ms-win-crt-private-l1-1-0 api-ms-win-crt-conio-l1-1-0 api-ms-win-crt-heap-l1-1-0 api-ms-win-crt-locale-l1-1-0 api-ms-win-crt-math-l1-1-0 api-ms-win-crt-runtime-l1-1-0 api-ms-win-crt-stdio-l1-1-0 api-ms-win-crt-time-l1-1-0 atl140 concrt140 msvcp140 msvcr140 ucrtbase vcomp140 vcruntime140
Executing wine regedit /S C:\windows\Temp\override-dll.reg
Executing wine64 regedit /S C:\windows\Temp\override-dll.reg
The operation completed successfully
Setting Windows version to winxp
Executing wine regedit /S C:\windows\Temp\set-winver.reg
Executing wine64 regedit /S C:\windows\Temp\set-winver.reg
------------------------------------------------------
Running /usr/bin/wineserver -w. This will hang until all wine processes in prefix=/home/twkj/.local/share/Steam/steamapps/compatdata/244850/pfx/ terminate
------------------------------------------------------
Executing cd /home/twkj/.cache/winetricks/vcrun2015
Executing wine vc_redist.x86.exe /q
0024:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
0024:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
0024:fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub
0100:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
0100:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub
0100:fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub
0100:fixme:advapi:DecryptFileW (L"C:\\users\\steamuser\\Temp\\{74d0e5db-b326-4dae-a6b2-445b9de1836e}\\", 00000000): stub
0024:fixme:ole:CoInitializeSecurity 0031F5F4, -1, 00000000, 00000000, 6, 2, 00000000, 12288, 00000000 stub
0110:fixme:shell:SHAutoComplete stub
------------------------------------------------------
Note: command wine vc_redist.x86.exe /q returned status 102. Aborting.
------------------------------------------------------
Timyoshi commented 4 years ago

Patcher output if this is relevant.

patcherOutput.txt

Linux74656 commented 4 years ago

Alright. According to the patcherOutput.txt, vcrun2015 is installed correctly, you can ignore the log given by winetricks this time. I've seen this error before... i am just having difficulty remember how I fixed it. I think it has somthing to do with mono, but your logs indicates dotnet48 is installed and loading.

First you can try running WINEPREFIX="/home/twkj/.local/share/Steam/steamapps/compatdata/244850/pfx/" winetricks win7 and see if that has any affect. I have noticed that your prefix is set to winxp. usually that works, but some userse had issses and had to set it to win7, so it may help.

If not, I did notice your log file says it can not find your config file. Try placing this one into your prefix folder located here, /home/twkj/.steam/steam/steamapps/compatdata/244850/pfx/drive_c/users/steamuser/Application Data/SpaceEngineers/SpaceEngineers.cfg then run the game without changing any settings. SpaceEngineers.cfg.zip

Timyoshi commented 4 years ago

Same error happens.

Linux74656 commented 4 years ago

Could you post your new log files, they may have changed, and it may give me an inclination on if anything changed.

Timyoshi commented 4 years ago

Space Engineers Log SpaceEngineers_20201031_212735514.log

VRage log VRageRender-DirectX11_20201031_212736918.log

Linux74656 commented 4 years ago

Ok. The new log has a larger 'VRage.Native.dll' error report, that points to the voxels. It may be related to the voxel quality settings that plague the rx5700/rx5700xt cards, and causing hard lockups. (Logs indicate you have a RTX 2080, but this still might be an issue.)

So try starting a 'Empty World'. If you get into the game then that is the issue, and you can try lowering all of the in game settings as low as they will go. make sure you get voxel quality to low, and the grass density slider as far to the left as it will go as well.

If it does not work, could you provide the version number for your graphics drivers?

Timyoshi commented 4 years ago

Yeah I do have a weird config. (Vega VII and RTX2080 super)

[twkj@desk etc]$ mhwd --pci -li
> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2018.05.04                true            PCI
    video-nvidia-450xx            2020.10.04               false            PCI

Also... It seems to be stuck in the loading screen.

Linux74656 commented 4 years ago

I see. This may be our problem. See if you can run the game using only the AMD graphics card. If that does not work you could try removing the AMD card and starting the computer, with only the nvidia card installed, then try running the game. If it works that means there is some sort of issue with the dual graphics setup you have.

Timyoshi commented 4 years ago

So I am not getting a option to use the AMD card. So I am going to check using only one card.

That would make sense... I did get a bad update a month back that messed with my gpus.

Timyoshi commented 4 years ago

So I removed my AMD gpu and it seems to have the same issue.

I could try removing my Nvidia gpu but I would have to do some more work geting it out. (My cpu cooler makes removing anything on the top gpu slot a pain in the ...).

Linux74656 commented 4 years ago

It may not be necessary to remove the card. You could try using prime, and the steam launch options. Though I have never tested this and have little experience on how it works, I have found some resources that may help you. https://support.steampowered.com/kb_article.php?ref=6316-GJKC-7437 https://wiki.archlinux.org/index.php/PRIME https://download.nvidia.com/XFree86/Linux-x86_64/450.57/README/primerenderoffload.html