Quote:
Originally Posted by jldjs
"When doing Saves such as you describe, are you exiting the game after the Save, and then re-starting it before trying to load the Save?" No
I usually proceed on the charted course for a while, many minutes, then "Esc", and Return to Main, select Load and choose one of the previous Saves.
Today, I start the game, and choose the last of the two Saves, it loads ok, showing the remaining charted course. So exiting the game does allow reloading a Save correctly, but, I've never had to do it that way with v1.7 or any other previous version before!
Is there something I should check with Win10 regarding this? And yes, my game is loaded on the SSD.
Thanks for your help.
|
s7rikeback has eliminated a lot of the ID conflicts of the different assets in the game, which allows for a "cleaner" Save, as well as what we think is better game play and more stability (which helps the Save situatioin). However, the game (in fact, the whole SH series) has never been good at "housekeeping", as far as a Windows program's memory management is concerned. When you play one part of the game, you cannot then play another part of the game, since the game does not properly clear or "release" its memory buffer areas. This is also why shelling out to Windows is not good in the SH series games on the 'modern' computer, because Windows is now "virtual" while the SH games are "literal" in their addressing, such that the game sometimes gets "lost" as to where to find its "parts" in memory when you come back in - Windows might change that "virtual" memory location. But the poor "housekeeping", in not properly clearing its buffers (I think) is what you encounter when you load a Saved game back in without exiting. For a preliminary glimpse at the problem, look at what Front Runner posted in "
The 'Quit/Start/Load/Reload' Issue (FOTRSU)", which is what led to the discoveries in "
Base Time 2018" (the most helpful stuff is on Page 5). Interesting stuff, though VERY boring subjects. The first link is a game thing. The 2nd was exacerbated by an FotRSU thing (but the game as the root cause), from having mis-configured Career menu choices. A player really should NOT have to deal with that in a game. It should WORK as intended - and it would sure be nice to have some "documentation" for a modder's interface... oh well. Thanks Ubi!
- but kudos to Front Runner and for digging into the details of those situations and helping us root them out!
