Starfield is far from the perfect game, and, as in any other Bethesda game, it has several mistakes. One of them, however, is especially strange: the longer you play, the more failures. Given that the role -playing game is designed for hundreds of hours, this can become a problem for those who devote so much time to the game.

Two modders drew attention to this detail: Dylan Thomas (known for Skyrim Audio Overhaul) and WSKEEVER (which, among other things, added crying angels from Skyrim from "Doctors who"). WSKEEVER wrote on Sabredta Starfield Mods: "I will explore the problem that I and many other people have encountered when preserving a large duration without NG+ more and more often paint during the game".

The reason is apparently how Starfield generates dynamic identifiers. These are codes that every unique object or place has, and which Starfield uses to track their current state. If you throw the first -aid kit, the game will remember where you left it, thanks to dynamic identifiers. The more of them, the more and more unstable the saving file becomes. So that this does not happen, they usually disappear after a certain time. Some containers remember what you put in them, while others eventually re -use identifiers of what is in them.

Obviously, this is a simplified explanation of the Starfield system, but it will give you an idea of ​​the situation. As SpareDifficult9987 said: "Inevitably, the fact that the ID generation will begin to end with the numbers that it can use to designate ID. This will lead to malfunctions in the game, and the more you play, the shorter the intervals between the failures will be, which will make the saving file practically non -grave".

At the moment, the only way to solve the problem is to launch a new game+ which will drop each individual identifier, but, of course, even in this case, after a certain number of hours and generated identifiers, failures will begin to become more and more frequent.

In addition, the Bethesda community manager answered complaints, saying that the patch that corrects the problem of memory leakage will be released next week, and that "Developers are investigating a separate problem associated with dynamic identifiers of modules, which prevents people from properly loading their preservations, and they hope to fix it in one of the subsequent updates. They are also actively dealing with the problem of long loading in Steam, and I handed them a couple of preservations of the community for verification".