You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure this is a technical bug, but it's not documented why serialization would differ - I'm on Linux amd64, and a friend is on Windows using the same core, downloaded from inside RetroArch. I'm unsure if the serialization is supposed to be different ("[ERROR] CMD_LOAD_SAVESTATE received an unexpected save state size." happens), and whether it's a simple case of 'pointers being double-width because Windows builds are 32bit' or 'TGB Dual Windows code uses different data structures'
Could someone explain this to me?
The text was updated successfully, but these errors were encountered:
I'm not sure this is a technical bug, but it's not documented why serialization would differ - I'm on Linux amd64, and a friend is on Windows using the same core, downloaded from inside RetroArch. I'm unsure if the serialization is supposed to be different ("[ERROR] CMD_LOAD_SAVESTATE received an unexpected save state size." happens), and whether it's a simple case of 'pointers being double-width because Windows builds are 32bit' or 'TGB Dual Windows code uses different data structures'
Could someone explain this to me?
The text was updated successfully, but these errors were encountered: