07-13-2021, 07:53 PM
(This post was last modified: 07-13-2021, 08:02 PM by Jesse Johannesen.)
I totally understand the frustration at this, but to explain a little bit why this occurs, the issue stems from the fact that for every new feature there are a new set of bits that are added to the Save Slots, so in the case that an older version of a save is attempting to load, one of the bits may not be in the correct place, or missing altogether causing it to behave erratically in the best case, or refusing to boot in the worst case, requiring a memory re-flash. It may be possible to solve this issue, and I believe that is one of the goals I've heard mentioned, but I am still a little unclear on the method and timeline. Next time me and Steve talk I'll be sure to ask. In the mean time, another totally viable option is just use it as is and don't update until something comes around that is worth the extra bit of work it takes to get your setup back how you like it. (edit: I just re-read the post and realized this last suggestion doesn't apply here as in this case it solved the exclusive issue, sorry if that came off as tone-deaf.)
Jesse
Jesse