fatheroctopus

Hi @Yaswanth were mods running at the time? Just be aware that even if the game code doesn't detect a particular mod in the stack trace, that it very well might still be a mod that's responsible for the crash. Let us know if the crash occurs with all mods disabled

Hello everyone, A patch ago we added a feature to the modding system that allows you ship multiple versions of your mod in the same workshop package. Two common uses of this are to a) keep archived versions of the mod around in case someone chooses to not update their game, and b) develop an updated version of your mod during the Testing period while still making the Release version of your mod available. This is accomplished by putting old versions of your mod into a folder called archived_versions/<version>. (<version> can be anything you like, such as version_1, version_2, version_3, or 399348, 410209, 419840 etc.) Note: the most up-to-date version of the mod should always be in the top-level folder, as normal. Only move older versions into the archived_versions folder. Once you've done this, create a file in the top-level folder called archived_versions.yaml. The contents of that file look like this: archivedVersions: - relativePath: archived_versions/version_1 lastWorkingBuild: 399348 - relativePath: arvhived_version/version_2 lastWorkingBuild: 410209 note: This is YAML syntax, so the 'relativePath' lines have a hyphen as the first character on the line, followed by one space. The 'lastWorkingBuild' lines start with two spaces. When you start on a new version of your mod for Testing branch, put the current version into the archive, create a new entry in archived_versions.yaml and set lastWorkingBuild for that folder to the current Release version number. Then make your changes to the mod to get it working for Testing branch. Other players will then run the correct version of your mod depending on whether they're playing on Release or Testing. Once the game update goes live, everyone's game version will be updated, and they'll all start using the latest version of your mod automatically.

Changed Status to Fixed Fixed for the next update to the testing branch - thanks for the report!

Changed Status to Fixed Fixed for the next update on the testing branch, thanks for the report!

Changed Status to Fixed Fixed for the next update on the testing branch. Note that on loading the save with this fix, sweepers will drop all the contents in their storage.

Another idea: see if Options -> Graphics -> Low Resolution Textures helps the issue. It might also be worth playing around with different resolutions, or windowed mode. The fact that the game didn't freeze on another mac does suggest that there's some sort of hardware issue going on - double-check that your graphics drivers are up-to-date (I *think* the System Update handles that on mac books, but I'm not positive on that)

Hi @Nerokiwi, unfortunately there is nothing in the Player.log that looks suspicious, and my local tests couldn't reproduce any similar issues. Given the graphical artifacts you are seeing, and its impact on the Mac outside of the game (requiring a force-shutdown), I think there's a decent chance that you're experiencing a potential hardware failure in your GPU. It is possible that it only surfaces when the temperature gets high enough, which is why you're mainly seeing it on larger bases after 20-30 minutes. Some potential test cases that could isolate the problem further: - If there's another cpu-intensive game that you own - try running that for awhile and see if similar failures occur. - If you happen to have access to another macbook, even if it's less powerful, try running ONI with this same colony - it might be laggy, but it shouldn't freeze the machine completely or display those red artifacts. - See if there are any diagnostic tools that can be run on your machine that could verify that your GPU is functioning properly. Let us know how it goes - good luck!

Hi, could you attach your output_log.txt file? Instructions in the link below Also, try deleting the file ~/Library/Application Support/unity.Klei.Oxygen Not Included\mods\mods.json before the running the game. This will guarantee that no mods attempt to update or load during the startup process. Thanks for the report! https://support.klei.com/hc/en-us/articles/360029555392 (edit: changed file path for Mac)

Interesting! What prompted you to try to deleting that file?

Interesting, this is quite mysterious. Here are few other ideas: 1) If you haven't already, try a complete uninstall in Steam and reinstall the game 2) If that doesn't work, go to Steam -> Right-click on ONI -> Local Files -> Browse Local Files Then navigate to -> OxygenNotIncluded_Data\StreamingAssets\elements\ In this directory, there should be 4 .yaml files (you should see gas,solid,liquid, and special) Try deleting these files, I'd be curious to see if Windows complains when you attempt to delete them. After deleting these files, go back to Steam and re-do the "Verify Integrity of Local Files" (this will re-create those 4 files) 3) Finally, if the issue still persists, could you attach those 4 files here? Then I can take a look to see if there's an issue with the resource data (edit: additional instructions in 2)

Hi, no additional news - it still does appear to be a driver issue, as the game is failing very early on in the process. A few questions and ideas: Are other games on Steam working when you try to run them? Have you successfully run ONI before on this machine? Have you ensured that any and all programs that may interfere with Steam/ONI have been closed before running the game? https://support.steampowered.com/kb_article.php?ref=9828-SFLZ-9289 If you have any third-party graphics software such as ASUS Tweak, RIVATUNER or MSI Afterburner, etc running in the background, try disabling them before launching the game to see if that resolves the issue Be sure that you are updated to the latest version of Windows10. https://support.microsoft.com/en-ca/help/4027667/windows-10-update Double-check that your graphics drivers are up-to-date, especially if Windows has updated

Fixed hang when a Dupe enters a rocket while holding their breath Fixed issue preventing sandbox temperature slider from going below 0°C/F Also fixed issue with germ count slider having limited range Fixed crash when eating at a Mess Table with table salt Fixed crash when clicking on the skill tree of a Dupe while they're in a rocket Copying Auto-Bottle setting on the Bottle Emptier now properly refreshes chores to deliver to the Bottle Emptier Updated Chinese strings View full update

There was a bug introduced in the last update that causes an infinite hang if a dupe entered/left the game world while in various states ("Holding Breath" being a common one). Dupes enter/exit the game world when they die, but also when they enter and leave rockets. I don't recall offhand what was the case for your save, but I did verify that it no longer crashes with the fix.

Changed Status to Fixed Fixed for the next hotfix to the live branch, should go out early this week - thanks for the report!