Rimworld (Steam) is causing a kernel panic on my Mac, resulting in a restart. This only happens when Rimworld is running, and doesn't seem to have a noticeable trigger (however, notably it's happened when creating a caravan twice in the last hour). My computer is a MacBook Pro (2012). Sorry, but I can't really say what caused it or what I expected to happen, it just freezes for a second and the computer shows (attached) error message. I've also included my save game and log.
[attachment deleted by admin due to age]
Thank you for the bug report. Do you still have the log file for when this crash occurred? (if you have played the game since then the log fie will have been overwritten). If so then can you please post your log file as an attachment. Details on where to find the log file can be found in the following thread.
https://ludeon.com/forums/index.php?topic=513.0
If you don't have the log file (due to having played the game since), then it would be great if you could upload it should this crash happen again.
Quote from: Calahan on January 08, 2017, 06:15:19 AM
Thank you for the bug report. Do you still have the log file for when this crash occurred? (if you have played the game since then the log fie will have been overwritten). If so then can you please post your log file as an attachment. Details on where to find the log file can be found in the following thread.
https://ludeon.com/forums/index.php?topic=513.0
If you don't have the log file (due to having played the game since), then it would be great if you could upload it should this crash happen again.
The Player.log file is attached, which I assume is what you're asking for?
The log doesn't report any crash; it just cuts off.
This sort of thing can't really be caused by our code; RW runs in Unity on C#, which makes it categorically impossible for it to crash this way. There may be a bug in Unity, but it's more likely an issue with OS/graphics drivers, or possibly your hardware. For example, if you have some bad memory, it will crash when loading new worlds because the game uses a lot of memory in these cases.
In any case, there's no path for us to fix this on the RW side so I'm gonna close this now. Sorry I can't be of more help.