1.112 - Save often

正在查看此主题的用户

scratch my earlier comment about playing 1.111. I guess 1.112 changed my savegames to a different file format and now I am forced to play 1.112 until they release a new patch, which makes it about impossible to fight any battles in which there are multiple waves due to the chance of the game crashing. Which, in turn, limits me to very, VERY limited gameplay.  :cry:
 
As a product, Warband is stable. Surely it is buggy, but in this the developers should take it slow in releasing fixes. Taking another day or two will not cause any discontent in their customer base, and taking time to get it right will improve their relationship with their customers :lol:
 
Knil 说:
Ya because coding is so easy  :roll:
They've been working on the same engine for YEARS, how it works is probably burned into their brains, they could probably fix every bug in the game in their sleep.
 
Maybe they know the engine but it's not so easy to predict exactly how it will react to certain line of code. There is no one who knows everything.

P.S. even when you write letter or some other "normal" text you sometimes make mistakes so why somone writing code can't make a mistake??
 
I'm getting the WARNING INVALID ENTITY!!! whenever someone is routed from a battle..

never crashed yet though..

I always have it on autosave anyway, so if it did crash i would only lose a few minutes at most
 
I've been coding in another language for several years and if it's one thing I've learned, it's that bugs rarely make sense. Most of the time it's a matter of a trial and error process, even for experienced coders. They've got my full support and I know I won't die if I've got to wait another week for a patch. I mean, what's the most we've waited anyway? Five days? Come on.
 
Well I learned along time ago that any patch released by any company can cause issues.

Suggestion for you folks.

Make a module call it home. Make this your primary playing game.

Then use the native module to patch and see if you have issues if you don't have issues then update your home module. You can use the same saved games for both modules but you lose nothing by spending a little time with the new patch and see if any has any issues. How many games give you this ability to have different setups so that you don't lose things?

Coding is not an easy thing. You always do your best to ensure that you don't have bugs but sometimes silly and unrelated things cause issues. I know this because I have coded in the past myself. The more code you have the more chances you have for it to have unintended issues.
 
If they had checked the patch they would have found this problem and been able to fix it prior to releasing it. I mean it's not really that hard to update your own version and test it before you let everybody have it. So it is indeed like we are beta testing their patches because apparently they don't.
 
Korz 说:
Coding is not an easy thing. You always do your best to ensure that you don't have bugs but sometimes silly and unrelated things cause issues. I know this because I have coded in the past myself. The more code you have the more chances you have for it to have unintended issues.

Shouldn't they at least bother to test it after it got through compilation though? A bit harsh maybe but I m annoyed I keep running into bugs preventing me from playing properly.

Korz 说:
Suggestion for you folks.

Make a module call it home. Make this your primary playing game.

Then use the native module to patch and see if you have issues if you don't have issues then update your home module. You can use the same saved games for both modules but you lose nothing by spending a little time with the new patch and see if any has any issues. How many games give you this ability to have different setups so that you don't lose things?

Awesome idea. Now if only I had a stable version to begin with, steam likes to update asap.
 
As widespread as this enemy routing bug is it really begs the question if the devs even tried testing their code before releasing it. 
 
It's nice they were able to get a patch out within a day, but the fact stands that a bug so glaring shouldn't have been released. 
 
Diavolo 说:
Noone should complain. Warband has given me much less bugs and problems than Bad Company 2. However, one should always save often.  :mrgreen:

If you don't speak, how will your problems get solved?  Responsible criticism is absolutely necessary, especially with a game that is not stable.  An excellent, innovative game, which, with the amount of money they should now have, should be both stable & more streamlined, the long list of things that need to be streamlined I will not get into.

No one is saying the game is garbage, it is not.  But it DOES need a good amount of work, making everything other than combat as cool as combat.  If you find yourself getting mad because someone is saying the game is not great, you should realize that you are being unreasonable, especially when you say to just sit and do nothing...allot of freedom won that way...

PS:  They do do an excellent job of keeping patches comming out.
 
wadedidit! 说:
Anyone bagging M&B Warband is an idiot, this is a fantastic game and once the Mod package is released the Mods will be released thick and fast!

Criticism against something you like is easy to lash out at, it attacks something you like, part of your group. 

That does not change the fact that it is often true, and worth hearing, and should cause a healthy change.

 
Bratislav 说:
hmm is it safe to update to 113?
I mean... i dont want to start a new game again xD
Just played the same battle the crashed on me before.  Ran just fine with 1.113 :grin:
 
Kittenhuffer 说:
I've been coding in another language for several years and if it's one thing I've learned, it's that bugs rarely make sense. Most of the time it's a matter of a trial and error process, even for experienced coders. They've got my full support and I know I won't die if I've got to wait another week for a patch. I mean, what's the most we've waited anyway? Five days? Come on.

So true.

Nordic War Sword + 1 for you, Sir.
 
后退
顶部 底部