搜索结果: *

MasterCaruyn 说:

Why don't you just download it and see for yourself? But if you insist upon laziness, than yes you can play it as it is as far as I have played. Obviously people have been able to play the game if you look at some topics besides the bug section.

点击展开...

What a typical cowardly jackass internet forum reply. It's not laziness for the guy to not want to invest hours upon hours of his time on a mod that may or may not be in proper working condition.  He approached the forum in a friendly manner, asked a simple question, tried to save himself a lot of grief and time and for that he gets the tried-and-true "Go look for yourself" response.  I'm surprised you didn't point him to a cutesy little Let-Me-Google-That-For-You link. 

Real laziness is taking the time to answer a question but not answering it with anything substantial.  True laziness is giving someone a smart ass reply when all he wanted was a little nudge of advice.  So it is you who insists on being lazy---and acting stupidly to boot.

P.S. At this beginning of this I noted that it was a cowardly reply because like so many other internet heroes, I'm certain you'd never be so rude to someone to their face.  But on a forum?  You're superman, aren't you? (I however WOULD say all this to your face because jackasses should be called out wherever they hide)

Munchkin9,

Not a single crash so far in two days of extensive testing.  I hate to jinx myself, because it's always after I report no new crashes that I crash---but really, I tested the hell out of this.

To reiterate, the mod I'm using has a lot of new content, but it's mostly just retextures (meshes copied from the Warband resources directory, duplicated in OpenBRF, then given new skins).  Also Better Banners and the mod that makes the female faces more attractive.  Aside from those last two, NO new meshes.  NO content carried over from the original Mount&Blade. It's 95% Warband Native, and no crashes.

So....  I think it's pretty safe to say that anyone who's getting Runtime errors in the later patches (I myself am still using 1.127), if they're using a mod, they should check whether that mod adds any meshes to the game (you can check this by looking inside the mod's resource folder.  If there are files in there, then the mod has added new meshes).  I would then report the crashes in the mod's bug thread (most big mods have their own forums with a bug thread).  See if others are experiencing it.  There's a good chance it would've already been reported anyway.

Now ... how do we fix it?  That much, I have no idea.

Munchkin9, an update on my issue:

After fixing every mesh in my mod to have a "30000" flag, I went in to test and experienced a Runtime error within the first half hour of play.  This indicates two possibilities.  Either my system configuration is somehow incompatible with Warband (though I should note my actual system specs comfortably exceed the recommendd settings), or there's more to the incompatability of a mesh than just the flag setting.

So I played a game on Native.  No custom content.  I played for half a day, doing everything in my power to crash it.  I took castle after castle in an attempt to duplicate the Runtime error (I usually get it the moment I press "lead your men in the assault").  No crash.  No Runtime error.  Flawless.

It's very possible that had I kept playing, it might've crashed.  But considering the frequency of my castle attack crashes prior to playing on Native, and then considering I took the entire Sarranid Sultinate and half the Kingdom of Rhodoks, cities and castles and all, without a single crash on Native, I'm leaning toward a mesh incompatability seperate from just the flag setting.

I've redone my mod and removed all content that was carried over from the original Mount&Blade.  I've also removed a lot of Warband content created by the community.  Any custom mesh has been removed.  The only things I've kept are my own extensive collection of retextures and the content from Better Banners.  So far, no crashes, but I still have much testing to do.  If it continues to work without a problem, I'll slowly re-add some of the content I removed and hopefully, by this admitedly clunky and tedious process of elimination, I'll find the mesh(es) causing my problems.

1257 would be a much harder job and take more than one person to fix---at least using my method of in-game testing.  Better for someone to figure out once and for all what it is with some meshes that's causing Runtime errors so we can just go through all items in OpenBRF and either fix or remove the problems.  Then again, whatever it is, it might not even be detectable in OpenBRF and might be something done at the mesh creation level.

Anyway, there's my report.  If I have any news from my new "slimmed down" mod (i.e. a crash) I'll note it here, but so far so good.

TweakMB allows you to do this:

http://www.mbrepository.com/file.php?id=1751

Egbert, this is the post you're referring to:

FrisianDude 说:

Unrelated; a heads-up rather than a question;  many folk have had problems with the Warband Resource .brf type and  many people have had problems of the game simply not starting if you have meshes with 0 flags. If you save as Warband Resource you have to make sure everything has the 'standard' 30000 (or 30001 as used by buildings, it seems) flags, but if you save as M&B Resource it can work with 0 flags. But that might have been found out already.

点击展开...

The thing is, I'm not sure I understand it.  Could someone explain this in a different way or dumb it down some more for me?  This offers hope, as it might point to the idea that it's not the quantity of new items in our games, but perhaps one or two bad apples.

The thing is, with the vast majority of my own added content (and many of 1257's, judging from the limited play time I gave it) we have native Warband meshes with custom textures.  Whenever I added one of these new items, I was sure to copy all the flag numbers and proper shaders, bumpmaps, etc., just as it was with the original item.  But I also confess I've added some of my favorite modded items from the original Mount&Blade, items with non-native meshes which forced me to have to guess what numbers to use when applying them to Warband.  All these new spears, helmets and swords, again, taken from the M&B modding community, look and work perfectly in game.  I've wielded them.  I've been in battles where dozens of them are being used.  Is it possible that they're still causing problems ... occasionally?  Even these dreaded runtime errors?

EDIT: Nevermind.  Looking at the native Warband buildings I see the flags as 30000.  So I suppose the issue at hand is when non-native structures are added to the game without the proper flag. 

But along the lines of what I was saying above, is it possible that these runtime errors could indeed be because of a faulty numerical entry for a mesh---but, a faulty entry which causes the crashes some of the time but not all of the time?

EDIT #2: Okay, I just went through one of my .brf files and found it PACKED with items (some from the original M&B, some made specifically for Warband) that had "0" under flags.  So I changed each one to 30000.  But I'm really skeptical that this will work.  Again, why wouldn't it be crashing every time I entered a new scene which had these items (which would've been just about every time, as these items have been added to every troop).

Also, I'm using the Female face model and textures replacer (http://www.mbrepository.com/file.php?id=1953) and noticed that most of the faces have numbers other than 30000.  Crosschecking these with the Native files, I noticed those too had nonstandard numbers, so I left these modded faces alone.  However, I did notice the jewelry added to that mod had "0" for the flags.  Should I just leave them at 0, or change to 30000? (I figure the modder knew what he was doing). 

Thanks for any help you guys can give.

EDIT #3: In my own Better Banners mod, three .brf files have been added: std_banners, std_banners_default, and std_flags_vertical.  In the first one, std_banners, all entries have flags set at 30000.  But the other two have all entries at 0.  As I only made the textures, and YellowMosquito made or edited the meshes, I'm not sure if these too should be corrected to say 30000.  In fact, comparing these to the native meshes, those Warband banners and poles (which use a completely different convention from YellowMosquito's, hence my reluctance) have either 30000 or 30001.  So I'd venture to change the Better Banner's assets (and upload a corrected version), but at this point I'm at a loss whether I should change YellowMosquito's meshes to 30000, 30001 or just leave them as is.

I play using my own custom mod which has a lot of new content, retextures and tweaks.  So when it loads, it loads much slower than Native.  Not nearly as slow as 1257, which has about ten times more content than mine, but slow enough.  I was getting the runtime error 1 out of every 3 times I entered a siege battle.  Then I enable "force single threading" in the Warband spash screen advanced options.  The number of runtime errors has gone down dramatically, but they still happen---as you say, Mrr.Phil---usually after an extended play session but sometimes sooner.  I'd like to test Native to see if it happens as well, but I can't stomach the Native campaign long enough to give it a good run, and am therefore kind of stuck with the theory that too much added content produces these errors.  Then again, I'm hoping someone who plays Native or at the very least an extremely light, non-intrustive mod, can post here and verify that they get frequent runtime errors as well.  If that's the case, then it's a legitimate (i.e. nothing to do with mods) issue, and maybe one day we'll see it fixed.

Ljas 说:

Wait patiently for the next patch.

点击展开...

And when that one comes out, wait patiently for the one after that.  And the one after that.  Rinse and repeat.

I think he means time passes too quickly when camped, meaning enemy lords can run up on us with very little warning.

Sure, in real life you'd have scouts on the lookout.  But how quickly could you get a camp full of sleeping men equipped and mounted and ready for battle?  I think it works well the way it is.  It forces us to be careful where we camp, just like we would be in real life.

Alhanalem, some people will understand my POV, some won't.  It really doesn't matter to me.  I'm not running for office., LOL.

The original snarky comment on this thread was made by ejnomad07, so maybe you should offer your advice to him instead.  I don't care either way.  The OP had a problem, I tried to help him, he got my POV just fine, thanked me, replied that he wasn't playing Warband and that would've been it, if it weren't for the hateboi over there trying to cause disruption.

Alhanalem, take another look at this thread.  This time be objective and don't drag our personal disagreement into it.

The OP said he was crashing.  Look at my first reply.  Did it in any way adhere to the description you made of me as someone who is only here to disrupt or cause trouble?  He then said he was playing the original M&B, to which I pointed out that this was the Warband tech forum, but noted my surprise that he was crashing in that game, which is very stable compared to Warband.  In response to this, ejnomad07 fires an incredibly rude, uncalled for broadside at me (and *I'm* the one being "watched," LOL).  To which I merely replied that yes, I already am playing the original game, followed by a flismy "save-face" style broadside of my own that was so weak it barely deserves comment.

If I'm just here to cause trouble, what is ejnomad07 here for?  To bring everyone together in brotherly love?  Sure, I can see that! And what are you here for, now that we're at it?  To help get some of these bugs fixed, as you can clearly see I did when I pointed the OP to the Bugtracker (before realizing he wasn't playing Wabrand), or just to comment on what you feel are the merits or lack of merits of other forum members?  Because that ain't too productive, either, my friend.

ejnomad07 说:

For the sake of everyone. Please go back and play that one then.

点击展开...

Already do.  But since you're so unnerved by my suggestions that a broken game is broken, I think I'll stick around and unnerve you some more.

Wow Vornne, I guess you told us. 

Okay, I'm gonna go back to my Warband and crash every ten minutes, along with many other users, and be happy that the devs refreshed themselves by adding some ivy to the walls of Veluca.  Thank you for helping us see this so much more clearly.

I agree with you Katorn, the new textures make it even more difficult to bare not being able to play properly.  I've been very excited about the new armor textures, but I guess I won't be seeing them for a while (unless this beta patch really isn't indicative of the real thing).

Do you also suffer from crashes, Katorn?

nood 说:

The archers still line up facing cavalry, you do get horses as loot though.

点击展开...

You mean they're facing the enemy incorrectly, still?  Unbelievable.  Please let us know when you get your first crash, as I'm confident that's going to happen as well.

Two more months of the original Mount&Blade for me, then, I guess.  I feel like QQing all over the place.

Please Nood don't forget about us watching this thread.  If you playtest at all, let us know your findings.  Please be sure to recruit a ton of archers too and see if they line up right, and push your system hard to see if you can get it to crash. 

Hmm, sorry.  This is the Warband Tech Support forum though.

Strange you're getting crashes in M&B.  It's a hundred times more stable than Warband, from my experience.

Stephan, I can't answer any of your questions because these are the same kinds of problems I have.  I'm also using a mod made from new items I've collected from the community (Enhanced landscapes is out for Warband???  Great!).  But please make sure to post these problems at the bugtracker forum.  Just use your Taleworlds forum username and pass. 

Here's the link: http://bugs.taleworlds.com/bugs.aspx?

Although we're on the verge of getting version 1.120, and hopefully these crashing issues will be solved, I'm not holding out any hope because I've hoped they'd be fixed with each new patch, and if anything the problem is getting worse for me.

I fear crash reports (especially these crazy crashes that can't be duplicated and just happen randomly) are under-reported at the Bugtracker forum.

I would imagine the export features aren't compatible either, wouldn't you think?  If not, the best thing to do would be to make a new export file for Warband (just make a level 1 character) then open up both and copy/paste the important lines from your M&B file to the Warband one.

Moss 说:

I'm afraid they aren't compatible.

All I can suggest is exporting your character, enabling cheats to regain your former renown and lands then disabling them again.

点击展开...