Messages

Unfortunately, as this bug wasn't immediately evident as it takes 15 minutes to kick in each time, and I was then attempting to work it out as a possible setting or install corruption issue, Valve have refused my refund as it went past 2 hours.  I'm not happy about this.  I have a lot of hours in Rimworld over the years but I resent paying extra for a DLC only to find out that it has been broken on Linux for a while now and has no fix in place.  Rimworld needs its Verified status on Steam Deck revoked until this is resolved else others may be tricked into paying out then discovering these issues.

Ah, so this would explain why I only get mouse hover over info for about 15 minutes into a game, then it stops working.  I haven't played Rimworld for a while and if I had known about this bug I honestly wouldn't have bought Biotech as it is incredibly frustrating.  Can you refund recently purchased DLC on the basis that the game itself is broken?

I have tried using Proton, on the Steam Deck, and anything new than 4.11-13 does not even load (just goes to a black screen) and 4.11-13 reports that Rimworld cannot talk to the Steam API, hence anything Steam related i.e. mods is not working.  I am sorry to say this, as I have played Rimworld for years and love it, but if Rimworld does not operate correctly on Linux and hence the Steam Deck due to this long standing set of issues, then it should not have Verified status.

Ah, so this would explain why I only get mouse hover over info for about 15 minutes into a game, then it stops working.  I haven't played Rimworld for a while and if I had known about this bug I honestly wouldn't have bought Biotech as it is incredibly frustrating.  Can you refund recently purchased DLC on the basis that the game itself is broken?

Thank you for this!  I'd been speaking to the Show me Where developer about this and we weren't sure what caused it.  If you haven't already, I'll let them know.

I have Path Avoid running and no issue.  I also have over 130 mods or so, and still no issue, so long as run in windowed mode under i3wm.  Could you try installing i3 with a default config file and seeing if Rimworld works fine for you that way as well?  My PC is also ancient, a CPU/mobo nearly 11 years old with only 8GB RAM and a 2011 Nvidia 560Ti.  So I don't think it is system capability/performance related, particularly as now my colony is large I am seeing it slow down performance wise yet now with no crash, whereas a handful of mods and no more than a few rooms built with 3 colonists was crashing constantly.

I've continued playing for up to 3 hours at a time with no crash still. I am using i3wm on Arch in a very minimal setup. I don't know if my specific config avoids the fault by setting to windowed mode, but it seems to work. I tried going back to full screen and it crashed not long in, so definitely something going on with that.

Damn, that's a shame. Maybe I just haven't had it glitch yet then. I played for a couple of hours last night and again this morning with no crash, which is the longest I've been able to.

Are you running any mods?

I may have a workaround.  I had the crash again and again reloading my autosave resulted in an almost immediate crash.  I took a punt on that Unity bug report mentioning resolution, but bear in mind I have absolutely no Unity experience and that could mean display resolution or resolution of an activity in the code or something else entirely.  I set Rimworld to not be Fullscreen and my autosave has loaded and has been running for a while now without any issue.  I'll see how it goes and report back.  Please tell me if I am just talking bollocks though!

EDIT: Have been running for a while now with not a single crash.  Off to bed now and will try again tomorrow, but looking good so far.

I posted it under the below link.  Kept it brief as already a load of stuff here and I assume if it is confirmed as a basegame/Unity fault this thread till be moved to the main Forum and the new post deleted anyway.

https://ludeon.com/forums/index.php?topic=37471.0

I hope it is ok to post this here.  A few of us have been discussing in the Mod Bugs Forum, but we think that it is actually a basegame fault and likely with Unity itself.  We weren't sure if devs looked in the Mod Bugs Forum often or at all though, so thought best to post here to bring it to your attention.

The fault only appears to affect Linux 64bit as others have tried Windows and Linux 32bit and the fault does not seem to occur in those.  It so far seems to only happen with a mod running, but it doesn't seem to matter which mod is running, as I have tested and had it with as few as 1-3 and as many as 130 with the same result.  The details are all in the thread in that forum along with a link to the Unity bugtracker showing the fault we are experiencing.  If it is Unity, we are aware that you may not be able to do anything, but it is likely why it has only shown up now in B18 if Rimworld is now on a newer and affected Unity version.  There is mention of a workaround in the Unity bugtracker, so I'm hoping you might be able to cobble something together in the meantime, as it is murdering our games at the moment!

https://ludeon.com/forums/index.php?topic=37241.0

I have no idea and would also like to know whether any of the devs are looking into this or at least have seen this bug report, or not. It doesn't seem to be on the Bugtracker, but other than that: 乁| ･ 〰 ･ |ㄏ.

I'm definitely not expecting some kind of immediate miracle fix, but it would be nice to know what the status of this is, i.e. is it a Rimworld bug, or a Unity bug, or something else entirely. If it's a Unity bug, this is probably out of their hands, anyway. 

That is very true, I didn't think of that and should have.  If this is purely Unity then not much they can do, but at least they would be aware and that it badly breaks their Linux 64bit users, though possibly only when using mods.  At least we seem to have confirmed that it doesn't affect Windows, or Linux 32bit, which makes it less likely to be due to any particular mod and more likely to be a basegame fault.  I may chuck up a post in the main bugs area to link to this one and see if it grabs their attention.

Do the Devs pick up on bugs reported here in the mod specific forum? If this is believed to be a fault with the base game Unity code in Linux 64bit which only occurs when a mod is installed, should we get this moved to the main bugs forum instead?

I just tried playing again, and this time it happend before even a single shot was fired, almost immediately after unpausing (during a raid, saved and paused where raiders just entered the map)...

rimworld_log:

Code Select Expand

<Some stuff from Centralized Climate Control?>

Receiving unhandled NULL exception
#0  0x007fff05d2f840 in funlockfile
#1  0x007fff05d2fdf8 in (Unknown)
EOF


From my repeat reloading and new game starting, it seems that once the bug has first hit at a seemingly random time into the game, even loading from an autosave prior to the bug occurring results in the reload dying seconds in.  I have no idea why this would be happening as the reloaded autosave has none of the same events occurring yet still dies in the same manner and is basically unrecoverable after that point.

Here is the section from my error log which relates.

Code Select Expand

Receiving unhandled NULL exception
#0  0x007fff37d34dc0 in funlockfile
#1  0x007fff37d35208 in std::vector<core::basic_string<char, core::StringStorageDefault<char> >, std::allocator<core::basic_string<char, core::StringStorageDefault<char> > > >::~vector()
#2  0x007fff37d35218 in operator new(unsigned long)
#3  0x007fff37d35238 in operator new(unsigned long)
#4  0x007fff37d35248 in __run_exit_handlers
#5  0x007fff37d35278 in exit
#6  0x007fff37d35288 in mono_thread_exit
#7  0x007fff37d35298 in mono_method_marked_as_wrapperless
#8  0x007fff37d35558 in mono_amd64_throw_exception
#9  0x007fff37d35718 in (Unknown)