-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USIO: Save Game Settings - Full Implementation (Supplement to #12686) #12714
Conversation
I suppose it should be written to file immediately once any changes are made |
Wouldn't this cause performance compromise during the game? |
You could just compare size and content and if it changes write to file? |
@RipleyTom The sizes of backup_memory(0xB8) and last_game_status(0x28) are constant, so the total size is always 0xE0(0xB8 + 0x28). As for the content, since a timestamp is included, the game changes the content and writes it to the endpoints frequently. |
Hmm, perhaps a memory mapped file can be used as an alternative. |
@Nekotekina Could you suggest an example? Thank you. |
File writes can be async if this function changes content so frequently. |
Actually nevermind, it would need quite a bit of work. I can implement it later. PR can be merged as is. |
@Nekotekina Thanks! |
This PR implemented permanent USIO game data saving, serving as a supplement to #12686.