msjpl

I'm pretty sure the bug is related to the amount of locations cached into the game. I first ran into the bug about 80 hours into the game. I had finished White March part 1 and had explored a good part of Twin Elms. I noticed the autosaves doing that weird thing when it brings up the save option. It saves normally, but the game won't visually show any new saves past the point where it starts doing that. I reloaded a save from an hour before and started doing other quests. I ended up playing longer than I did before, but the difference was I did not explore any new areas. As soon as I hit a new zone (one I had not been to), the bug started again. It didn't matter which zone (as I had two on my map I hadn't gone to yet), as both did the same thing, bug-wise. I made a save right before the bug started happening, so I was able to do some extensive testing. I can travel anywhere, no problem, except for "new" areas. Autosaves work though. Even if they don't show, they are still saving. If you close the application and relaunch it, it shows your most recent autosave (that wasn't appearing). I'm so far in the game that I might just push through and try to finish it, with the bug. I'm strong enough where I don't have to worry about party wipes for the most part, and I can still save when I want to. I just can't load. Its definitely game-breaking though if you are still at the point where you save after every encounter out of fear of a surprise tough encounter coming next. You'll end up with 50 save files (since you can't overwrite old files anymore). I guess that's not too bad though, because the next time you load up the game, you can just delete 49 of them. Its still pretty annoying though. But if any of the tech support people are reading this thread, I'm fairly certain the issue is related to zones, not inventory (like they were saying). Unless the issue is loading up future lootable inventory for the new zone and not being able to save all of it because of so many other areas being "open."

I created an account just to post this, fairly confident I unearthed a pretty nasty bug, while playing on Playstation 4. I'm not sure if anyone else has encountered this, or its just a crazy combinations of factors that caused this, but here it goes: So about 30 hours into the game, I casually quit after saving, like I had done many times in the past. When I tried to reload my game later, none of my save files would load. They would start loading, but about 2/3 of the way through (always at the same spot), they would stop loading and just load for infinite. The large "L" in Loading still had motion and the autosave icon was flashing, so the game wasn't frozen, it just simply couldn't load. It wasn't just the hard save though, as all of my autosaves did the same thing. Somehow, I managed to find a really old autosave from 6 hours back (not sure how that survived) that I was able to reload. I decided to experiment and see if I could recreate the bug. Originally, my game had the bug in Dyrford Crossing (both the field and the cave). I immediately went to Dyford Crossing and saved in the field, then tried to reload. It reloaded fine. Next, I had a hunch of the one variable that was different from prior saves. I had just purchased The Hours of St. Rumbalt from the weapons merchant in Dyford village. Luckiy, six hours behind, I still had enough gold, so I bought the sword and immediately went to Dyfrod Crossing and saved the game. When I tried to reload that save, I encountered the infinite loading screen again. That was the one variable, that weapon that I bought and equipped, "The Hours of St. Rumbalt" greatsword. I don't know if this is a known issue with the developers, or even a legit issue, but my troubleshooting led me to that conclusion. I'm not sure if its something fixable in an upcoming patch. But I wanted to let the developers know of that issue and maybe warn anyone else. Then again, maybe there are people that bought that sword and equipped it (I equipped it on Pellagina) and never had any issues. And to reiterate, I'm playing this on PS4. Not sure if the issue is the same on Xbox or PC.