Messages

1

Suggestions / Re: Technical stuff : make Underrail more Dropbox/btsync/whatever-friendly

« on: March 27, 2016, 05:50:04 pm »

Semi-offtopic : And thus I switched to SyncThing. It lacks a decent installer on Windows, so you have to be eager to do a bit of administration but it certainly is nicer regarding to locking files and folders. And fewer problems with Underrail. But it's mostly because enumerating is done less frequently.

2

Suggestions / Re: Technical stuff : make Underrail more Dropbox/btsync/whatever-friendly

« on: March 07, 2016, 08:25:47 am »

Hi, I didn't try SyncThing, I'm using btsync.
I quite agree that the cleaner thing (in the sense it is orthogonal to any external stuff we're doing) to do would be a abort/retry/ignore dialog.
Coupled with fact that an ignore for an autosave failure should load the next level
Cheers

Edit: And SyncThing is supported on FreeBSD too! I might switch.
I found a log of the autosave problem :
Game Version: 1.0.1.4
Error: System.Exception: Failed to save game 'autosave'. Exception: System.IO.IOException: Le r

3

Suggestions / Technical stuff : make Underrail more Dropbox/btsync/whatever-friendly

« on: March 06, 2016, 03:11:35 pm »

Hello and thanks for the gorgeous game (discovered on the Codex and preordered a whiiiile back).
I cloud manually my saves and I'm having a little trouble with quicksave and autosave.
When I press F5, procmon tells me that you rename "quicksave" to "quicksave (previous)" and then create a new quick save folder.
Except it often fails because my clouding tool is locking the folder to synchronize it (because a) I'm a save scummer b) my upload is low).
It's even worse with the autosave because when it fails, the game quits !
I suggest a few tiny changes to help player with this scenarios.
* When doing any save, set a max retry count and loop trying to save while it fails, sleeping maybe 1sec between tries. If it fails 10 times, for instance, you can consider it a real fail
* Use more previous slots (4? 8?), and destroy/rename to the least recently used one (it allows the player to have more backups and leaves more time to the clouding tool to do its job)
* Failing the autosave should report but not prevent going to the next map
These are not perfect solutions but they would help very much with my setup (and probably with other people's )
Hope you'll have the time and energy to consider this
Cheers and thanks for the good work,
Tramboi