Patch Notes e1.0.3

[NOTHING_IS_NOT]

I HAVE FOUND A SOLUTION... there is a hidden folder called game saves that was clashing with my system deleted it and game works great now

Yeah can you please elaborate on where you found these files and how you fixed this?

 

[Jhaerik]

Cool

Right now they prolly will patch critical issues like save corruption, hard crashes and startup issues. Balance and tweaks comes later, (I think) so don't get your hopes up.

What's the point in fixing saves if you can't get far enough into a game to reach that limit before the snowballing ends it?

 

[ErrorMcJigg]

What's the point in fixing saves if you can't get far enough into a game to reach that limit before the snowballing ends it?

What's the point of fixing snowballing if your save will just become corrupt? Chicken or the egg, except even if 1 faction owns the map you can continue to run around, join tournaments and test, where as corrupt saves give a hard end point to the character.

 

[alnaviba]

After this hotfix, my game runs horribly on the lowest settings. For some reason it doesn't properly read my cpu capacity correctly anymore.

 

[Jhaerik]

What's the point of fixing snowballing if your save will just become corrupt? Chicken or the egg, except even if 1 faction owns the map you can continue to run around, join tournaments and test, where as corrupt saves give a hard end point to the character.

That's just limbo. Worse than hell.

 

[LoKken]

After this hotfix, my game runs horribly on the lowest settings. For some reason it doesn't properly read my cpu capacity correctly anymore.

EXACT SAME issue here.
Since yesterday, its like my CPU memory is not enough and i am runing the game between 1 and 15 fps.
I dunno what happend...

I must inform you that its only happening since yesterday patch, before I was runing more than 30 fps wich is more than enough for me to rule multiplayer games i'm in

Best regards, Taleworlds !

EDIT : PROBLEM FIXED : The last patch has changed my video settings : It has switched from the big Geforce GTX 1050 ti to lame Intel graphic 600 thing

 

[Xerx Um]

Unfortunately, it's seems that problem is not fixed Has a save just before joining the tournament. It's always loading without any issues. One/two saves after-- and it's not. It's doesn't matter if I join tournament (win/loose) or just sell the loot -- any attempt to load saves made after will end up with crash screen. No active quests are taken. Except for the artifact "xxxx folly".

 

[Iwanikus]

Looks like the problem is not fixed at all. Never had problem with saved games. Now after i updated to 1.0.3 all my saves are broken ...... Its sad that i cant play my main campaign anymore after 450 days gametime...... I hope that will be fixed. After all its just stupid to beginn every day a new campaign.

 

[lncomplete]

To explain, what happened,this 1.0.3 update increased the save cap to 46 instead of 45 before corrupting the save file(only applies to older saves 1.0.2 and below)
FYI : Creating a new save file with "Save As" does not reset the cap to 0, it counts as 1 save , so if you were on 45 before , clicking the "Save As" option to create a new save file will only increase your save count to 46 and thus corrupting your file again.
I've heard from other players that creating a new game on 1.0.3 has a save cap of around 54 instead. This 1.0.3 hotfix is a short-term measure to fix this bug , hopefully TaleWorlds will have a more stable fix to this corrupting save bug.
Let's not forget that this game is still in Early Access and we players are here to help find bugs so that the game can be improved on. Hopefully in a month's time or so , this game can become polished to being a timeless masterpiece as Warband is.

 

[stevehoos]

To explain, what happened,this 1.0.3 update increased the save cap to 46 instead of 45 before corrupting the save file(only applies to older saves 1.0.2 and below)
FYI : Creating a new save file with "Save As" does not reset the cap to 0, it counts as 1 save , so if you were on 45 before , clicking the "Save As" option to create a new save file will only increase your save count to 46 and thus corrupting your file again.
I've heard from other players that creating a new game on 1.0.3 has a save cap of around 54 instead. This 1.0.3 hotfix is a short-term measure to fix this bug , hopefully TaleWorlds will have a more stable fix to this corrupting save bug.
Let's not forget that this game is still in Early Access and we players are here to help find bugs so that the game can be improved on. Hopefully in a month's time or so , this game can become polished to being a timeless masterpiece as Warband is.

Going to be much longer than a month.

 

[Nordmann]

What I'd like to know, is why there's a save cap in the first place. I've never seen this in any other game I've played to date.

 

[Lucinious]

What I'd like to know, is why there's a save cap in the first place. I've never seen this in any other game I've played to date.

It isn't intentional, I'm sure. More than likely it's just the way they format saves and it's becoming to large a file size to load but eh

 

[Nordmann]

It isn't intentional, I'm sure. More than likely it's just the way they format saves and it's becoming to large a file size to load but eh

Well, it's a pretty big screw up whatever the reason. At least the community caught it, they obviously haven't done much saving and loading themselves!

 

[Lucinious]

I said the same thing in the post I made lmao. Bugs, glitches, visual issues...all fine. Whole parts of the game not even working? Not okay.

 

[Zahari]

MP patch pls

 

[Marcquez]

Well, it's a pretty big screw up whatever the reason. At least the community caught it, they obviously haven't done much saving and loading themselves!

Well, that is why they have this EA, right? Best user acceptance testing you can have.
They probably do not have the ressources to test everything. With this EA, they will find those issues a lot sooner.

 

[Xerx Um]

To explain, what happened,this 1.0.3 update increased the save cap to 46 instead of 45 before corrupting the save file(only applies to older saves 1.0.2 and below)
FYI : Creating a new save file with "Save As" does not reset the cap to 0, it counts as 1 save , so if you were on 45 before , clicking the "Save As" option to create a new save file will only increase your save count to 46 and thus corrupting your file again.
I've heard from other players that creating a new game on 1.0.3 has a save cap of around 54 instead. This 1.0.3 hotfix is a short-term measure to fix this bug , hopefully TaleWorlds will have a more stable fix to this corrupting save bug.
Let's not forget that this game is still in Early Access and we players are here to help find bugs so that the game can be improved on. Hopefully in a month's time or so , this game can become polished to being a timeless masterpiece as Warband is.

Maybe it's what was intended by the fix, but it's not how it behaves for my saves. Have a save that is always loading without any issues and from version 1.0.2
0. Load it.
1. Save As ->newSaveToTestCap
2. F5 3 times.
3. Attempt to load newSaveToTestCap
Result:Crash

 

[Mordred of Dublin]

8 years in development and you ca't save without corrupting. I know it's ealry access and all, I get that, but how did this bug make it past the devs? you can't have an early access game if you can't even ****ing play the game AT ALL. Third time I've restarted everything, no more. when it's patched I'll go back.

 

[bestguy]

Fix: Don't save/load. Keep the game running.

 

[MArdA TaleWorlds]

I have been informed that our developers fixed a crucial bug on this save corruption issue. The fix is now on testing stage and if everything is alright, we will push the patch as soon as possible! Sorry for the inconvenience.