Pillars of Eternity II: Deadfire

Pillars of Eternity II: Deadfire

View Stats:
Conlan Oct 21, 2018 @ 3:05am
There was an error loading the next map.
"There was an error loading the next map. Returned to main menu to prevent save corruption."

I got this error and returned to main menu. What is this? I've never encountered major bugs in my first playthrough, and now after hoards of patches, i got this...

Definitely my interest is lost...
< >
Showing 1-15 of 18 comments
It's nothing new. It's just rare and could have hit you much earlier, but very rarely.

It's "a feature" they've added while continueing to hunt some bugs that cause bad side-effects they want to prevent - such as corrupting savegame data.

Typically it is not reproducible, if reloading the last quicksave/autosave, so it seems to be something that cannot be tracked down easily so far.
Lampros Oct 21, 2018 @ 6:24pm 
I have this quite often. Almost all the time if I play longer than three hours or four hours? Also FPS degrades rapidly at the same time. So might be some sort of memory leak issue.
ofrejoles Nov 2, 2018 @ 6:31am 
How is this fixed? Im having same problem. Kahanga Palace. can't get out.
Originally posted by ofrejoles:
How is this fixed?
It hasn't been fixed yet as explained in comment #1.

Edit: There is no specific 100% reproducible bug in Kahanga Palace, though. The problem can occur in random places.
Last edited by D'amarr from Darshiva; Nov 2, 2018 @ 6:52am
GuJiaXian Nov 2, 2018 @ 8:40pm 
This hit me this evening after 40+ hours of play. I verified my game files, and that didn't fix the issue. Unfortunately, all of my saves seem to be affected. [Spoilers!] I just started "The City Lost to Time," and I just have the vision/dream with the gods. I have saves right before the vision/dream and right after. The ones from before won't load at all, and the ones after (just my main character in the hold of my ship) will load, but I cannot "leave" the ship and return to the Deadfire map screen.

I'm currently reinstalling from scratch, so we'll see if that helps. If it doesn't, I think I'm done with this game. As a working adult with a family, I simply don't have the time (or, frankly, interest) to replay this from scratch knowing that I'll likely just run into this error again.

I'm extremely disappointed with Obsidian's reaction to this issue. Searching online, this error has been reported since 2015 for PoE1 and since early this year for PoE2. But...still no fix.
Originally posted by GuJiaXian:
Searching online, this error has been reported since 2015 for PoE1
Huh? PoE 1 is not affected by any such error. Temporarily, but only during the v1 or v2 series, it could corrupt savegames due to autosaving and manually saving conflicting with eachother, but that has been fixed.

It's is new in PoE 2, and comment #1 in this forum applies.
tranks Nov 3, 2018 @ 2:57pm 
ive bought this game and after reading in this forum, actually never played it because i fear to loose my time on some game breaking bug. though i will negatively rate the game just because i can
Last edited by tranks; Nov 3, 2018 @ 2:58pm
As far as I understand the issue and according to how I've experienced the bug myself - a very few times only since release - it doesn't invalidate any of your savegame files retroactively. It's always possible to reload the last savegame file and older ones and continue there.

Also, let's not forget that in some cases the culprit is a damaged installation, and repairing the game with the Steam app's verification feature for game installations fixes it.
GuJiaXian Nov 3, 2018 @ 6:59pm 
Originally posted by D'amarr from Darshiva:
As far as I understand the issue and according to how I've experienced the bug myself - a very few times only since release - it doesn't invalidate any of your savegame files retroactively. It's always possible to reload the last savegame file and older ones and continue there.

Also, let's not forget that in some cases the culprit is a damaged installation, and repairing the game with the Steam app's verification feature for game installations fixes it.

I've both verified my installation and reinstalled from scratch—neither made any difference. I do have one (presumably) unaffected file: the one the game auto-creates when you begin the Beast of Winter DLC. I could reload from there, but I'd lose 20–30 hours of play. Frankly I don't relish replaying that much of the game just for the "privilege" of beating the final quest.
Well, if the game really crashes reproducibly with a savegame file, then you want to send that file to tech support. As why you don't have any other working savegame file within those 20-30 hours, sounds odd.
GuJiaXian Nov 5, 2018 @ 7:04pm 
Originally posted by D'amarr from Darshiva:
Well, if the game really crashes reproducibly with a savegame file, then you want to send that file to tech support. As why you don't have any other working savegame file within those 20-30 hours, sounds odd.

I did just send the save game files and other information to tech support; hopefully that helps them diagnose the issue not just for me, but also for others experiencing this issue.

In the meantime, though, it occured to me that I really just want to see the ending to the game (without having to replay it from scratch or risk running into this same issue again). Would anyone be willing to send me some save game files from right at the beginning of the final main story quest? (Preferably one in which the PC has been upstanding and nice—I focused on diplomatic and benevolent responses).
tranks Nov 5, 2018 @ 10:31pm 
watch it on youtube?
GuJiaXian Nov 6, 2018 @ 7:48pm 
I'm working with tech support to see if we can narrow down the issue. At their recommendation, I enabled cheats (yes, I know that that disables achievements for that save) and teleported to Queen's Berth. However, as soon as I try to leave Nekataka by sea, I'm hit with the "error loading the next map" issue. I provided new saves and output logs; here's to hoping they can figure it out.
In the worst case they only find that the savegame data are damaged, which is what they are trying to counter with the sudden quit to main menu. The culprit seems to be a nasty bug that can affect a random area spontaneously, as it seems, depending on what happens during combat.
josh.tjz Jul 5, 2019 @ 9:48am 
I'm having the same problem! I can't leave my ship to go to the world map and I can't find any solution so far. All posts regarding this problem doesn't seem to have been solved.
< >
Showing 1-15 of 18 comments
Per page: 1530 50

Date Posted: Oct 21, 2018 @ 3:05am
Posts: 18