安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题




If you've not started playing a game since your last scan--or haven't updated the database--you can opt to skip the second scan.
You can disable this behaviour too via Program Settings. The "Remind me to rescan once per session" option (from within Task Specific -> Backup Settings) controls the prompt you're referring to and the "Save detection results for faster detection in future" option (from within Detection Configuration) will force GameSave Manager to perform a full scan each time. Just be aware that full scans can take several minutes to complete.
GSM makes a Recall on startup, then – when the user wants to make a backup – recommends to do a Full.
Ist that correct?
In that case, I prefer GSM to do a full scan, whenever I am about to make a backup.
»Just be aware that full scans can take several minutes to complete.«
Indeed both scans take their time. So I want to reduce it to one scan. The bottleneck in my case are the screenshots done via Steam.
What I do not understand is:
»whenever you ... update the database«
When do I do this? This does not appear familiar to me. Is the database automatically updated via an update of the software?
»rulesets«
I also do not understand this and therefore do not grasp the difference between the two types. Is this explained somewhere? It is not that important though.
The prompt you're seeing is just a way to warn the user that the Recall scan was performed, thus a Full scan should be run if they've started playing something new since the last scan.
As mentioned before, you can modify this behaviour in Program Settings.
The Full scan will take longer as it's scanning for over seven thousand supported games / gaming apps (many of which have several paths too).
Updates are reported in-app when they're available (assuming your Program Settings are configured accordingly).
You can always manually check for updates via Help -> Check for Updates too.
Rulesets are merely the 'rules' that GameSave Manager follows when trying to find supported data to backup.
These are specified in the databases and are automatically parsed whenever needed.
So, if I understand correctly, it is not possible to set GSM, that he aborts the Recallscan on startup (I may be able to abort it, if I am quick enough). Or at least, that he performs a Full instead.
The option, which you recommended to me, would only disable the prompt to do a Full, when I am inside GSM after the Recall, would it not?
If desired, you can stop the scan from occurring at program startup too.
Check out the Program Settings, there's quite a few options you can tinker with.
Disabling a scan on startup in general just made GSM to move the Recall, when attempting to backup something, and then immediately wanting to make a Full.
Thank you for your time and patience. And thank you for GSM. I am pleased to see software made here in the EU and not only in the US.