Messages

And that it is something you can set in unity's player build settings. - which would fix needing any script at all on mac, and the old script would be fine for Linux (although I still suggest adding a $@ at the end of it)

Do you think this is something I should do?

(TL:DR -> +1 for player rebuild)
well in case it really doesn't has any impact on performance it looks like the best thing to do for now. Since you don't have to fiddle around with new scripts.

It doesn't sound like it hampers anything at the moment, "it should just be a matter of new features", so you may as well.  (I'm thinking it'd just be graphical features, but I may be wrong.) But for a fix, it'll solve the problem.

[11:36] <Tak> it _should_ only affect new features
[11:37] <Tak> well, the legacy renderer will go away in unity 5.5
[11:37] <Tak> at that point, people will need drivers that support core profile 3.2
[11:37] <Tak> (which even mesa on intel does now)

oh boy, hope amdgpu with CIK will get stable till that happens, otherwise my wine will work overtime ....

@ttoocs thanks for all your work!

[This should fix it launching with a black screen and immediately crashing with slightly older hardware.]

Here is a first-version of my script, that attempts to detect when it needs to run the game with -opengl-force.
This should fix it launching with a black screen and immediately crashing with slightly older hardware.

It does try to do it for mac as well, however, I do not know the structure of steam on a mac, and is hence very limited.

Put it in the directory where start_rimworld.sh is and it should work fine.

Here it is in a code block, but it is also an attachment.
[...]

Your script works fine for me. If it's working for mac, maybe Tynan could use it till unity gets it right. That said is there a bug report for unity?

I use the opensource "radeon" driver (3.0 Mesa 12.0.1) since the close source driver doesn't work with 4 monitors. (gfx driver are a mess, be it amd or nvidia)

Maybe thats the big difference here why it works for some and some not. Oddly enough i have no problems with starting other unity 5 games.

[Run the game with -force-opengl (A unity argument)]

Found, a working (for me), accelerated (not slow), fix.
Run the game with -force-opengl (A unity argument)
[...]

yeah -force-opengl did the trick for me as well, thanks a lot!

still it's odd that you have to "force" opengl since it should be the only mode available on linux 

@freedomischaos have you tried the following ?
https://community.unity.com/t5/Linux-Editor/OpenGL-Graphics/m-p/2473257

tried it on my end, no effect

Temp fix didn't work for me. The pref file isn't being generated, and the original pref file I had only had 3 settings: fullscreen, width, and height. No UnityGraphics stuff.

what is your distro and wine version? (cat /etc/issue , wine --version)
The "delete all config" fix seams to work for some but not all.

runs smooth as butter!

my System is a:
AMD Phenom(tm) II X6 1090T Processor (6x3,5Ghz)
Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] (multi-head with xrandr, 4x1920x1080 monitors)
16GB RAM
nearly endless hdd space 

( as a note here, i use wine-staging with CSMT enabled, witch can improve gfx performance but is potential unstable )

[UPDATE]

[...]
I'm tempted to think that Wine + Windows RimWorld will work, but you'd need a decent computer to handle all the underlying system translation calls - I think.  I have zero experience with Wine. 

well i'm out of it with running after pointers into the memory as well, but most unity games run fine with wine. I'll test it right away, thanks for the hint!

UPDATE: i got it working with »wine-1.9.13 (Staging)« and »winetricks tahoma corefonts« isn't nice but works for now.

[UPDATE]

SrSalem your log concludes with

"Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application."

I'm really kind of worried. I hope there's not some horrible Unity or Mono bug on Linux...

i hope it's not something in unity, but there seams to end somewhere in »libmono.so«, but on the other hand KSP(unity 5) works fine .... (always at [0x7f9c39e22772] btw.)

I could play Rimworld A13 before... and for some reasons launching the game detected 3 screens.

Code Select Expand

Set current directory to /home/sergio/.local/share/Steam/steamapps/common/RimWorld
Found path: /home/sergio/.local/share/Steam/steamapps/common/RimWorld/RimWorldLinux.x86_64
Mono path[0] = '/home/sergio/.local/share/Steam/steamapps/common/RimWorld/RimWorldLinux_Data/Managed'
Mono path[1] = '/home/sergio/.local/share/Steam/steamapps/common/RimWorld/RimWorldLinux_Data/Mono'
Mono config path = '/home/sergio/.local/share/Steam/steamapps/common/RimWorld/RimWorldLinux_Data/Mono/etc'
displaymanager : xrandr version warning. 1.5
client has 3 screens
displaymanager screen (0)(LVDS1): 1366 x 768
Using libudev for joystick management


By the way thanks for the attention milon and Tynan.

thats fine, mine reports 6 screens but got only 4 monitors. Guess the report ist about the connections you have not the connected ones.

UPDATE: little note since i got a workaround in case the linux version won't start whatsoever. You can play the windows version of rimworld with wine and "winetricks tahoma corefonts" since the fonts used missing otherwise.

seams to crash at libmono, every log says:

Code Select Expand

libmono.so(+0x91772) [0x7ffff352a772]
after that all the logs differ. No idea what that means but in my log there is a part that might help:

Code Select Expand

[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
RimWorldLinux.x86_64: xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
and the part about deleting the unity3d configs does nothing on my end. Is there maybe another dir to delete?

btw. running with:
AMD Phenom(tm) II X6 1090T Processor
[AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] (multi-head with xrandr)

same here, running arch