Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
@DavidM I'm just including these stack traces in case it's useful to anyone.
If the game runs better under Proton anyway, then Proton it is for me.
As long as it runs I don't care if it's native or not :D
I dev right in Linux and TBH I might release my own game without native Linux support because the Proton way is less of a headache.
Cheers.
----------------
I logged two native attempts, one with nVidia driver 415.27 and one with driver 435.21 both crashed somewhere in the nVidia drivers trying to create a texture.
Could be a driver bug, could be the engine is trying to hand over a bad pointer to the driver when creating textures.
This game doesn't seem to use loose files so it's unlikely it's a case-sensitivity issue.
System is a TR 1950X, 32GB, GTX 1050 2GB, kernel 4.15.0-99-generic #100-Ubuntu SMP. Xubuntu/Ubuntu 18.04.4 LTS
Maybe I should not release for Linux at all, if the windows version works better under Linux anyway. And it's less work.
Okay, so I tried it with Proton and it crashed as well, so I updated to driver 440.82 and it's running fine in Proton now.
nVidia driver 415 + native: crash
nVidia driver 435 + native: crash
nVidia driver 435 + proton: crash
nVidia driver 440 + proton: runs fine (only tried 5 minutes), played over an hour now
Edit:
nVidia driver 440 + native: crash
It's very much looking like it's entirely a driver issue so far.
I'm re-downloading (I regret not backing up the directory now...) the native Linux version and I'm going to test driver 440 + native.
Ubuntu 18.04 does not yet recommend driver version 440 so it's likely a lot of users are still on version 435.
I'll test 440+native as soon as it finishes downloading.
On my main machine so far only nvidia proprietary driver version 440 with Proton (5.0-7) works.
Just spent 60+ minutes playing it.
Performance-wise it's very playable on my GTX1050 2GB if I drop all the settings at lowest (50% scale-up, everything on low) I'm happy with that. It gives a GameCube retro charm to it.
If I move up any sliders the frame rate becomes inconsistent. Feels like what Unreal does when it tries to auto-adjusts and enters a loop of "smooth? raise it! oh no, it's slow! drop it!" (and repeat).
I think Unreal tries to be "too smart" about the quality adjustment and the timing on Linux causes periodic hiccups but I haven't worked with Unreal in years so I can't help on that front.
I hope those data-points help. I can't tell if it's a driver issue or an Unreal-on-Linux issue, or something particular to pre-20xx-series nvidia cards, or all of those things together.
All the crashes I have seen on my machine have happened inside the nvidia drivers, I don't think it's anything you @DavidM can fix on your end at all.
Unreal, Steam/Proton & nVidia all have been working hard on Vulkan support so things change fast.
Proton has improved so much in the last couple years that it feels like the most practical way now for a small studio (esp a one-man operation) to "support" Linux.
My advice to anyone finding this thread is try with Proton 5.0-7 AND nvidia driver 440 or later for now.
Cheers,
* Kubuntu 20.04
* i7-4790K
* 16 GB RAM
* GTX 1080 with Nvidia 440.64
1) I dropped the resolution down to 1280x720 and set shadows and anti-aliasing to medium. Same result.
2) Switched to the "testing" beta without success.
./Supraland.sh
4.21.2-4753647+++UE4+Release-4.21 517 0
Disabling core dumps.
[S_API FAIL] SteamAPI_Init() failed; no appID found.
Either launch the game from Steam, or put the file steam_appid.txt containing the correct appID in your game folder.
Failed to find symbol file, expected location:
"/home/aclark/.steam/steamapps/common/Supraland/Supraland/Binaries/Linux/Supraland-Linux-Shipping.sym"
LowLevelFatalError [File:Unknown] [Line: 1670]
Failed to find shader map for default material WorldGridMaterial(/Engine/EngineMaterials/WorldGridMaterial.WorldGridMaterial)! Please make sure cooking was successful (No inline shaders, null GTSM)
Signal 11 caught.
Malloc Size=65538 LargeMemoryPoolOffset=65554
CommonUnixCrashHandler: Signal=11
Malloc Size=65535 LargeMemoryPoolOffset=131119
Malloc Size=68112 LargeMemoryPoolOffset=199248
Malloc Size=145512 LargeMemoryPoolOffset=344776
Realloc PtrSize=68112 NewSize=145512 PooledPtr=0x00007fb450490040
Malloc Size=123824 LargeMemoryPoolOffset=468624
Engine crash handling finished; re-raising signal 11 for the default handler. Good bye.
Segmentation fault (core dumped)
3) Trying proton version next...
For anyone else that hasn't tried forcing a game to use Proton...
1. Right click on the game in your library
2. Select Properties
3. General Tab
4. Check "Force the user of a specific Steam Play compatibility tool"
5. Select "Proton 5.0-7"
it is nice that the dev does support linux. but only press "export to linux" and hope for the best is not the best way to publish a game. You say you know nothing about linux. how will you give your linux custumers support? they have paid the same price.
again, it is nice, taht you want support linux but it is not nice to give them no support and an not optimised game. many devs acting like this and that is the reason for many bad, buggy or not well working linux ports.
the best way here would be.
1. end the official native linux support
2. people who already own the game can use the latest known working branch
3. refunds for people who only want use native port
4. support proton
But we don't have control over refunding. That's not in our hands.
I could of course create a branch with the linux version, as legacy support.
I'll soon make those decision. Gog and Linux support are both more work than gain for us and we need to be honest about it and drop support in a responsible way.