Vornne said:Nonsense: the 1.158 patch is tiny and has almost no chance of messing up a single player save file, and the 1.157 patch likely fully compatible with 1.153 saves as well.
Very unlikely to be caused by version 1.157 or 1.158: the last time two scenes were added was in 1.153, and before that some were added in 1.130 and 1.123. Your error message would make sense if your saves were years old, or if you made tweaks to the Native module.valent69 said:I can't load up any of my SP characters. My game closes and I get this error message everytime for any of my 9 characters. "Load error: Number of scenes in file: 579, exceeds 553"
Vornne said:Very unlikely to be caused by version 1.157 or 1.158: the last time two scenes were added was in 1.153, and before that some were added in 1.130 and 1.123. Your error message would make sense if your saves were years old, or if you made tweaks to the Native module.valent69 said:I can't load up any of my SP characters. My game closes and I get this error message everytime for any of my 9 characters. "Load error: Number of scenes in file: 579, exceeds 553"
It seems likely you have corrupted the Native module somehow: the correct number of scenes in both 1.153 and 1.157 / 1.158 is 553, not 579; it has not changed. My old single player saves work fine in the latest version.valent69 said:It's not like I even have to touch anything to patch it up and I haven't touched my Native folder in a while.
John7 said:Gotta update those aimbots
John7 said:Gotta update those aimbots
The Bowman said:Send me the DL just as soon as you're finished.
valent69 said:I can't load up any of my SP characters. My game closes and I get this error message everytime for any of my 9 characters. "Load error: Number of scenes in file: 579, exceeds 553"
Understandable I've spend just a week on my previous savegame, so it was easy to trash it awayvalent69 said:
But I made so many fwends, I can't just leave them behind and create a new character.
Thanks for the replies , you are right, I checked it ... I was testing some new version of 1257 AD ( one of the final ) and I had to be sure that I was not reporting bugs related to native version update status ....WuTaNiSt said:Jason L. said:As I said the last update is the one of 6 Sep. 2012 and to be correct it's the 1.154 !!!!!!MaHuD said:Steam should auto-update. The download on taleworlds.com is for non-steam version.
That's the last one steam bothered to document. The steam version should still be patched up to date (mine is anyway), they're just not telling you about it. Ignore steam & check the version number shown on the launcher or the main menu.
That's a bug? Hm I always called it jamming... Haha It is rather annoying, but I don't see any instant fix for it. Unfortunately we have to wait until the next patch, or find a simple quick fix patch.Osviux said:The crossbow not firing bug is still there ;/
valent69 said:
But I made so many fwends, I can't just leave them behind and create a new character.
Zenithars said:That's a bug? Hm I always called it jamming... Haha It is rather annoying, but I don't see any instant fix for it. Unfortunately we have to wait until the next patch, or find a simple quick fix patch.Osviux said:The crossbow not firing bug is still there ;/
sotamursu123 said:If your crossbow gets jammed, it's jammed until next round. There's no fix to it.
Cradoc said:2. drop xbow and sword, pick up sword first then xbow
Noob sota.sotamursu123 said:If your crossbow gets jammed, it's jammed until next round. There's no fix to it.
Le Roux said:Noob sota.