For more information see here Bug Report Template Build:1.8.3 Mode: main menu Mode: N/A SERVER NAME: N/A SEED-ID: N/A If applicable: MODIFIED PLAYFIELDS: Reproducibility: unknown Severity: extreme Type: game breaking/disk write error Summary: Upon trying to make a new world the game crashed. After verifying files it attempted to get missing files and has maintained a disk write error status. Description: I tried to create a new world today and the game crashed out, refusing to relaunch. I tried to verify files and it said some were missing, so it began to download said missing files. After this it got a disk write error so I attempted to restart steam, my computer, clear download cache and many more fixes. I tried uninstalling it and installing it on a different drive to no avail. Both my SSD and NVME are in good health so I know it is not a disk health issue. This issue is only happening with Empyrion as I have installed other games in this same time frame to test if it was a problem for other games as well. I have plenty more space on both drives (100gb+ each) and have been troubleshooting this for awhile. I have no clue how to reproduce this, but I can not even install the game anymore as it always give disk write error. The content_log from steam is attached so it may give you a better idea of where the process is failing. Apologies if this is the wrong place for this, someone suggested I make a bug report out of my situation. Steps to Reproduce: Unsure as I can not get back into game. 1) 2) 3) Screenshots, Crash Logs, any other Relevant Information or Download links:
Check to make sure your antivirus program isn't blocking it. Disable it as a test, or just add an exception for the entire Empyrion folder within your AV program. After disabling or adding an exception then verify files through Steam/install.
Out of curiosity, how did you verify the health of the SSDs? Wouldnt be the first time I have heard of SSD reporting itself fine until you run a full diagnostic on it and then found out it is far from being in good health in the system it is installed in. If the above is the case, then you may find some file operations taking a very long time and eventually failing, but not seeing that in your log.
