Crash when reading/writing save files (Windows 10)

[MercuryViper]

TIS-100's game save location appears to be a sub-folder off of my default Documents folder.

Problem for me is that for other games and apps I own, my default save location is actually a cloud storage-backed folder and if TIS-100 tries to read or write to the save files whilst the background storage system is doing its thing, TIS-100 CTD's with an IOException due to a file-sharing violation.

I had a look for a config file that I might be able to set the save file path in, but nothing jumped out at me.

Anyone else had a similar issue and found a way around?

[Category Theory]

I have had issues like this, and my workaround has always been "don't make any save dirs cloud dirs as well." (I sync back and forth between the save dirs and the cloud-backed dirs using Git, but there are other ways of doing this as well, including a specialized game save backup program whose name I forget.)

I was going to say, if you want to continue to have Documents a cloud-sync'd directory, you could try moving the save dir out of Documents and then using a symlink or a junction point where it used to be, pointing to the new location, but I think most cloud drive services will follow that and still lock the actual files. But you could give it a try.

[MercuryViper]

Actually, the game's author contacted me offline about this, and he fixed this issue in the app for me by applying retry logic to the save file process. If the Onedrive app has the file locked for replication to the cloud, the game doesn't fall over now.

[stonelance]

I'm getting an extremely frequent crash that seems likely to be the same issue. Was the change an actual update to the game? Sounds like I should submit one of these error reports...

CALL STACK:
IOException: Sharing violation on path D:\OneDrive\Documents\My Games\TIS-100\76561197975885130\save\60099.1.txt
System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options)
System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share)
System.IO.StreamWriter..ctor (System.String path, Boolean append, System.Text.Encoding encoding, Int32 bufferSize)
System.IO.StreamWriter..ctor (System.String path)
System.IO.File.WriteAllLines (System.String path, System.String[] contents)
SimulationWidget.#=qSiYjBUncoDQUKUA2MUZrEA== ()
SimulationWidget.Update ()

[MercuryViper]

It's been a while since I had that issue, but the stack trace looks similar and the save path being in your OneDrive folder also helps. Zach patched the game itself, adding in retry code around the file save process.

I wasn't aware of any patches for the game in a while so I'm not sure how that could have crept back in, so it's probably best to drop him a stack trace and some details about how your machine is set up, see what he says.

[KestrelPi]

Also seeing this issue at the moment. Tried disabling onedrive for saves to see if it improves things

[krispykrem]

This issue should be fixed in today's update.

[River Sol]

This crash started happening to me today, oddly after a full day of gameplay. I paused my Google Drive Sync and the issue so far has gone away. Odd to store data automatically in the default Document folder rather than a discreet TIS-100 folder....or maybe this glitch is a clue to the TIS-100 inner workings. (Great game so far, though I do wish for an Infinifactory sequel!)