Savedata: Respect IO timing method setting #14837
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this, configuring IO timing method = Host will probably dodge any stutters on scoped storage save/load, but may be more hazardous if there's some game that expects specific timing. See #13847.
The current timing (always completes in one frame) is definitely wrong, but this is a quick change to validate my assumption that changes here could be an improvement. We should improve it, but that seems a bit more dangerous right now than extending this setting (which already has possible instability) to savedata, which it really should've always included.
-[Unknown]