I forgot to mention, for anyone that is getting this error and has the game as well as their save game files on their primary internal SSD, the issue is that your in-game graphics settings are exceeding the ability of your SSD to keep up. The only thing you can do is decrease the graphics settings you are using until the error no longer occurs. I'd suggest going down one preset graphics settings step at a time until the error no longer occurs. Once you reach the point that the error no longer occurs that is the preset graphics setting that your system's SSD can handle. If you have already reached the "Low" preset graphics settings and the error is still occurring the only thing you can do at that point is lower the resolution that you are running the game at, and/or lowering and capping the frames per second (FPS) that you are running the game at. This will also help to reduce the amount of data that your SSD has to stream at any given moment to your GPU. You can also try lowering the resolution and FPS instead of reducing the graphics preset that you are using for the game as far as you need to in order to stop this error from occurring if you want to try and find the optimal possible combination of graphics fidelity, resolution, and FPS that your system can handle for the best gaming experience. However, lowering the resolution and/or FPS by themselves may not be enough to prevent this error from occuring so please keep in mind that you will likely also have to lower the graphics preset you have selected in order for this error to no longer appear.
Yeah, anyway, my game installed on a brand new SSD bought in September, running with a brand new 4070 Ti SUPER. I set the graphics all the way to "Low", etc etc, and the error still occurs.
So is there an actual solution, or am I just going to have to replay hours and hours? Because this error doesn't occur when I load a save from the Lighthouse, so it clearly has NOTHING to do with hardware settings or resolutions or where what is installed. It has to do with the maps it's loaded on, auto saves not working, and oh, it loads me in falling through maps when I do get into an auto save. So? Any actual solutions?
It was my best attempt to help people based on symptoms and presentation. It's unfortunate it was of no help to you. Obviously, the root of the problem is elsewhere in some cases.
Based on what you are saying it appears to be an error with map loading information, especially the "falling" symptom you are experiencing speaks very strongly to a fundamental asset that failed to load. However, in the "falling" instance, you should have just gotten a Load Error since the game should never attempt to start a gaming session with fundamental map data missing. This speaks to a very serious error occurring in such a way that the integrity checking is failing to even recognize there is a serious problem.
The why, however, is apparently something rather obscure or non-obvious since people have purged everything, re-installed, etc... with no success, so it doesn't seem to be a corruption of any kind. The failure to load due to a lack of speed leading to a timeout in the streaming resource loading system seems to be a source of the problem for many people as switching to internal SSD from external HDD helped many. However, External vs. Internal isn't the fundamental issue because I was playing the game installed to a quite generic external USB 3.2 NVMe enclosure housing a very mediocre NVMe drive connected to a Thunderbolt 4 port and I never ran into a single problem. If External vs. Internal was a major part of it my setup never should have worked. Also as your situation proves, it is not as simple as HDD vs. SSD for everyone either.
At this point, to me, it seems to actually be a fundamental flaw or critical bug in the resource streaming system that the game uses to load maps and other similar data into the GPU. Something is occurring that is causing the resource streaming to either corrupt the data in transit to the GPU or it is failing to read the data into the GPU correctly despite having intact resources to work from. Unfortunately, that means that short of a full understanding of where/how/why this bug is occurring, reproduction on the part of the team that needs to write the patch, and a patch for this issue from them, this problem will likely not be solved any time soon.
I wish I had better information for you.
