"Can't save just now. Try again shortly"

God damnit. :smiley:
I just closed the game to make a test if it is what causes it.

I did however delete like 10-15 saves but never got my ability to save back… but … I guess I should’ve deleted even more?

Oh well, anyway, here’s a video replicating that bug… going from being able to save, doing the quest -> not being able to save.

E-mailed this to the dev support address too.

Glad if deleting saves fixes it for others, even if I already lost my progress. (TBH despite being a couple of hours, it wasn’t a ton of progress - I can run it easily in 30 minutes if I just beeline it I think.)

pain in the backside to manage but i try to keep to under 10 total… as you play more, the size of each save will increase more and more.

Gotta get to the habit of clearing em out as I go :slight_smile: Thanks for the info!

you’re welcome

tbh, this happened to me on other PS4 games. just guessing it might help some with KCD

Lol I lost my progress too, because I accidentally loaded a save file while deleting :smiley: .Im very stupid, but at least I know now what the problem was. Do you guys know where the save files are located on your disk?

not exactly. sorry

Mine did that too and I was a few hours ahead, luckily on mine I remembered trying to do a archery contest in uzhitz that the NPC said he would find me some challengers but no one showed up and I left. I choose the beginner archery contest and it did that. So I went back and talked to the same guy but did a archery contest for slightly advanced and then it loaded people in and I finished the compitition and it let me save luckily. If you can remember where you think something might of happened try going back to the location

I have said this elsewhere but not saving at least once an hour in a game with a harsh save system and bugs is not smart.

The Bug appeared after starting an Bow-Tournament (Merhojed Camp), which broke. I paid the Archerymaster and no Opponents appeared.

Solution: Started another Tournament with other Skill-Ranking. Everything worked and i could save again.

I hope it will help you guys.

Got the same bug during The House of God quest. I ended up with Zmola carrying the Leshek body out of town. When I“ve asked him what he is doing, he attacked me, so I had to kill him. After that, I“ve finished that quest by informing Divis that it“s done and noticed that my game didn“t save. I was not able to save my game at all. But somehow I“ve managed to solve that (older saves).

But right now, I have the same bug with Charlatan (Miracles While You Wait quest).
When I gave him the stolen shroud and the angry villagers have arrived, while he has flown away. I had to persuade them (speech) to calm down, by this way I“ve finished that quest, but since that I was unable to save my game at all (Schnapps not working, same with save mod from Nexus, save game in menu is just greyed out).
The only solution I“ve found was to kill the charlatan (his quest will fail obviously) and then I was able to save my game as always, but I don“t want to do this by this way.

Cure for this problem was in my game to continue the main quest (that time it was fight at cuman/bandit camp in Prybislavitz - Nest of vipers). After next video of gameplay it saved it on it’s own after the video and now I can save games again. No progress lost :sunglasses::sunglasses::sunglasses::sunglasses:

1 Like

Maybe I should try that too. Have the same problem at the moment.

Thx

Thx worked for me too :raised_hands:t2:

I save about every 30 minutes. U could try that instead of waiting hours. Just saying.

One issue can prevent saving the game: bugged archery contest. When you talk to person to start archery contest, it may happen that no one arrives and contest ends immediately after the conversation before it starts and it’s impossible to save game after this moment, i believe it’s not finished in the inner game logic. Solution is to repeat contest, even if one (or both) NPC does not start shooting and you leave the area and get disqualified you can save the game. This bug was present at least in patch 1.2.5