搜索结果: *

Still going strong, I see. A lot of us have been struggling with this issue for a while now, there's a number of threads about it here where you'll find more information. But no solution. And thus quite a few of us also have simply shelved the game until this is fixed.

DrunkenPanda2000 说:

Just make a github acount and properly submit your bugs over there these people of the community are putting their time in to fix your issues you might as well take the 3 extra seconds to make a githubacount and submit your bugs over there like they ask in the description.

点击展开...

I see you didn't understand a single word I wrote. Like the fact it doesn't matter whether I am (or we are) or not on Github (I am, btw), but the very fact Github isn't a community board and the vast majority of the community isn't and never will be there whether we like it or not. But that's all right, it happens.

What's more concerning - and definitely more in topic - is the report by @Forteverum. I had the impression something similar might have happened to me as well at least in a few occasions, but other times I could go back to an earlier save relatively fine. And, just like several others, I found the issue way too annoying to simply be bothered to keep playing at all until it's fixed, so I couldn't really aggregate more data.

@Forteverum, you still have those saves? Have you checked in the windows browser the file timestamp? I'd be very curious to know if their last modification date corresponds with when the save was created in game, or if they actually got modified (when they bloated, basically) later on.

Also, I wouldn't hold too much my breath for a progress update from the devs about an issue that's not even officially been recognized yet.

DrunkenPanda2000 说:

lol don't say the community patch isent sharing with the community they just dont want chaos on their propperly managed channels they just want to force people to submit thei bug reports on github.

点击展开...

Which doesn't make closing the Nexus thread any less unusual and, yes, community unfriendly, by definition. As only a microscopic percentage of the playerbase uses Github: this doesn't just mean much less people will contribute with bug reports (but that's their business: indeed getting them only from people who bother to use Github may very well make it more orderly and avoid excessive inaccurate feedback, so there's advantages too indeed), but also that players lose the Nexus platform as the hub in which to discuss the mod and, for instance, help one another with their issues, compatibility troubles between mods etc, nor they have - as it happens with most other mods - the Nexus as a hub to get infos and updates by the modders about what they are working on etc. Which is a disadvantage for the players themselves: so, again by definition, "not very sharing with the community".

Anyway, this is OT so whatever.

EternalHeathen 说:

Need some clarification, when this happens do you have to delete the bloated save in order for other saves to work again?

Also, when you say without mods, do you mean mods disabled or no mods ever on a fresh install?

I ran into this problem a while back, confirmed not antivirus, but couldnt find solid sounding info like this at the time.

点击展开...

The other (older) saves will work, it's the bloated save that's irremediably borked (even if it actually loads, you won't be able to save anymore, even on new files). You can delete it, overwrite it, whatever: you just won't be able to continue that savegame anymore.

Usually, if the previous save is still fine (and with the normal size of about ~35mb) the issue usually won't reappear at the same time even if you more or less try to retrace your steps (although sooner or later it likely will reappear): but there have been a few people who reported saves that could still be resaved just after being loaded, and that repeatedly would then give the error in a reproducible way just a few steps into it: this could either mean they had an already borked and bloated save that still managed to resave just once or so, or that they happened to save just before one of the things that cause this bloat, whatever it might be that's borked in the code. So close to it, actually, that they couldn't avoid it anymore: those saves would be very useful to the devs to better identify the cause, but alas I don't know if anyone who happened to encounter such a "perfect spot" bothered to upload their save for investigation.

This is why it's important to keep a healthy number of separate saves on rotation: because a save from 2 minutes before might not be enough to recover the game for the long term.

As for mods: yep, AFAIK even games with no mods whatsoever, I've seen plenty of people reporting this issue while never having gone to the beta branch or installed any mods. It just seems to be definitely less frequent in unmodded games, which however can be just a biased perspective for various reasons: the playstile thing mentioned before, or the fact some mods can give similar errors for very different reasons, which often tend to overlap in the feedback. And, last but definitely not least, the very fact there's A LOT more communication about game issues among players active in the modding community (which, at the moment, is focused more on fixing the game rather than expanding it, for obvious reasons) than elsewhere, so the issue gets reported and talked about much more there than here, which could lead to make it seem the problem has a strong correlation with mods when that correlation doesn't necessarily mean causation.
There also have been reports about the Community Patch guys having supposedly identified a likely cause for it and being investigating the issue for a fix, but... heh, that's third party information, as the Community Patch project is, quite baffling I dare say, not very sharing with the community (they even closed the comment thread on the Nexus, for some reason). So take it with a grain of salt.

It's been reported times and times again that the issue is related to sudden savegame bloating. Just keep an eye on your save files: sooner or later your latest one (likely an autosave) will suddenly go from ~35/40mb to ~65/75mb, which quite evidently shows something got corrupted. Once that happens, you won't be able to save anymore. At the moment the only solution is to keep several savefiles on rotation, so as soon as you see the issue coming up, you have a previous save to revert to without losing too much progress.

This happens with or without mods, although some mods can possibly make it more frequent (not even necessarily for any specific technical reason: the main one why for instance the Tournament mod was wrongly accused - apart from a different problem it caused when it still saved data in the game in its older iterations - is likely because by its very nature it encourages savescumming playstiles: and guess what happens more often if savescumming when you have a random chance of the game corrupting each time you save it?).

Of course the game just gives the same error message for every possible issue that causes the save to fail, so the usual silly oversights such as messed up antivirus softwares, folder permissions or lack of disk space end up being reported in the same topics, but the two things *are not correlated*: proof of that is you can perfectly fine load and save the same campaign from 20 minutes before the issue came up. Until, once again, a new save bloats (and likely corrupts) the file again, and the issue is back.

Ehanoc 说:

Just as a note. Saves take a lot of space and... if you configured in Steam a different installation drive rather than C: , the game will go into that drive but the game saves will ALWAYS go into C: . It seems to be hardcoded ....

This happened to me as well because the C: folder was full

点击展开...

There's a lot of silly possible oversights like that that can happen, but what we're talking about is another thing that's inherently part of how the save system works, it just gives the same message as when a save can't be created because of disk space, folder authorizations, antivirus softwares etc. We can freely load and save other or new campaigns, which completely rules out any of these system related issues, it's that specific playthrough and its latest saves that get borked.

BTW, @Mama Luke, now that I think of it, quitting the game might really have a part in this. As stated my playstyle involves quite a bit of reloads, and I've noticed that (just like in Warband... come on, TW!) reloading saves seems to cause what looks like a pretty serious memory leak. By the 8-10th reload (more or less, at least with my specs, I guess mileage may vary), performance begins to get noticeably worse (up to the point of garbling the music on the loading screen), and that's when I quit and restart the game. I've had the bug happen with no restarts whatsoever (suddenly it starts popping out when an autosave begins to fail, and that's when there's no turning back), so it can't be the *only* cause, but indeed the last time I had it the game saved fine (or at least apparently so, quite obviously something got corrupted), then I immediately quit because the game needed a restart, and since then that game cannot be saved anymore, even if immediately after having been loaded, without moving or doing anything else.

In any case, the new version of the Community Patch just came out a few hours ago, and no news in the save system department. So heh, still waiting for some good news ¯\_(ツ)_/¯

Yup, my saves start giving that problem at around 65mb+ too. I also had the feeling (but it could be just a coincidence) that savescumming might be a part of what causes the bloat (and would further explain why several people first linked the issue to the tournament mod): in the first weeks of the game I usually go on a tournament spree to quickly make some cash, which implies quite a bit of reloads when the matches don't go my way. Perhaps reloading the game without going back to the menu/quitting the game altogether (or, again, saving and loading a game inside a city instead than on the general map) fails to clean everything it should from the "cache", which gets incrementally added to the next saves. That could explain why I tend to get to those sizes so quickly in a fresh campaign.

It's just speculation though, but judging by the very different feedback from people there could be a playstyle variable like this one in play (and "cleaning up saves" does indeed sound possibly related). I seriously hope a fix isn't too far, 'cause as it stands now I've just shelved the game waiting for when I can finally invest in a long running campaign.

It seems (emphasis on *seems*) a save bug perhaps related to save bloating. As the size of the save file increases, so does the risk of encountering the save bug, and this would be why the frequency of this bug increases with the number of mods you are running. It happens in unmodded games too, just more rarely (and usually, on average, much later in the campaign). In my case, it always - always - begins to appear after a week or two, but I do indeed play (I honestly couldn't otherwise, given the state the game is in) with quite a high number of mods.

Apparently though, the Community Patch guys have identified it and are working on a fix (at least this has been reported by the Tournament Xpanded mod author, whose work has for quite a while been wrongly blamed for the issue), so IF they manage to solve it we'll both have a solution and TW will be informed of what they have to fix on their side as well. Of course, if someone encounters it in a vanilla game without mods (and it's not any silly antivirus issue blocking the save folder), yes, please send it to the devs so they can work on it.

For the time being we can only wait.

Just adding another report that sometimes "forcing" the dependencies on a mod could cause some other bugs. The very same player that discovered this load order behaviour also reported a short while ago that by doing that on a smithing mod, somehow it caused his character to become invisible on some scenes.

Can't imagine why, as the whole thing is just supposed to "force load" vanilla "mods" that the game loads anyway, with the only difference of ensuring they load before custom made mods (as they should), but the game (and its launcher) are in such an early development stage that... well, who knows.

I have myself done this to the half a dozen mods I'm running right now and haven't noticed anything out of the ordinary, but just be advised there's a possibility even this might not be a 100% solution for compatibility until Taleworlds themselves sort the launcher issues.

In the meanwhile I did a little more testing, as I was having some more CTDs in different battles, and indeed it seems they were caused by the Twilight Horse (I'm a dirty cheater and had given one to a companion ). As in older threads about this issue it was mentioned - if I understood correctly - that the likely cause was when the horse gets killed, I hope it might be helpful to remark how in my testing the cause wasn't that, but rather when the horse model was being loaded at long distances. IE: I turn to my companion at the beginning of the battle and have no issues, but if get far and then turn back looking at him, I tend to CTD very consistently. As soon as I took the horse away the issue seemed to disappear.

Something wrong with one of the LOD meshes, maybe?

I just came back to Perisno after quite a while (the mod is growing very nicely, kudos!), did a fresh install of MelsPerisno 0.75 and I too have some CTD issues in battles against demon worshippers, even in the early game against a small roaming party.  By searching around it looks like a known bug from vanilla Perisno rather than something Mel's specific, so I'm mentioning it here, just in case. 

habeo123 说:

Kadath, it's not mirrored, it's real items. There are over 2000 items in the game, and we planned on adding more. Ofcourse that explained why the mod is 1.2 GB. But in return, the variation in every shop is great that you can't really find identical items in 2 shop.

点击展开...

I was mentioning all those (~200 or so) _noswing_ weapons, which indeed are "normal" weapons mirrored (same stats, same models, same textures), only without the swinging attribute, which are not even sold in shops (or even viewable with the cheat menu) as they haven't the merchandise tag. I'm sure they are there for a reason, but still they contribute to the high item count (though hopefully the engine is smart enough to recognize their assets are already loaded so they don't weight as much).
Regardless of the variety of the items (which I'd say could be debatable here and there: ~100 lookalike - both in stats and actual looks - "peasant" leather armors? Were so many really needed from a balancing perspective?), anyway, PoP that has "only" a little more than 1.000 items is obviously less demanding in that department, for better or worse.

Many of the items in Perisno are beautiful (which explains why I ripped an hundred or so from it to use them for myself in Pendor too ), but the huge number comes at a price, and for someone who already struggles with performance in PoP that has half as many it can be a relevant detail.

I personally found it more demanding than PoP. Maybe because of the staggering number of items loaded (some of which - weapons mostly - even have a mirrored entry in the .txt for whatever reason, bringing the total amount to more than 2.000), not sure, but it is one of the very few mods that force me to load textures on demand to even start (which, in turn, slows down a little every ingame transition).
Battles themselves, though, do run more or less at the same fps as my PoP "custom" installation (PoP + a couple of relatively light graphical mods like the cinematic compilation), so it's not too bad (PoP is quite smooth for being such a big mod, actually). With an old computer sporting a 512MB ATI HD5750, 3GHZ dual core, and 3GB RAM (4GB really, but the OS is still 32 bit, so even when messed with it cannot dedicate more than 3GB), I can play it very well with a battle size of 200 and all the graphic settings at max.

Ehy phlpp, don't know if you already noticed, but since last week the Shogun mod is officially discontinued and gone OSP. There might be something useful for you to salvage in the brfs: a couple of weapons and armors do look good indeed, and might save you a bit of time

I don't know about 3.6, but it definitely works with 3.611 and the latest version of TweakMB.

He probably wasn't in the battle at all since he was at 10% HP, so he couldn't be wounded and thus captured. When going after named spawns, always check if the leader is at full health (actually I believe it'd work as long as he's at least at 30% HP, but better safe than sorry).

Volja 说:

1. does my surgery skill effect garrisoned troops or other troops belonging to lords in a battle? or just my own party troops?

点击展开...

It does affect your allies too.

Volja 说:

2. ive seen my reinforcements always arrive quite later than the enemy's both in the field and the sieges. is it because they are losing troops faster than us and the AI tries to equal the troop amount?

点击展开...

Reinforcement waves kick in once a team's number of living units has got down to a certain threshold (a base value modified by the battle size and advantage values too). Thus yep, the side which is taking the most casualties will obviously be reinforced more and sooner. Plus, the defender has a slightly higher base threshold (meaning they do receive reinforcements even sooner). Defenders in sieges also have more waves available than the attacker.

Volja 说:

3. if i rebel from empire do i get to keep the villages belonging to other castles/cities and vice versa

点击展开...

The villages tied to cities/castles you do not own should be lost in the process, even if you rebel the "soft way". At the same time you should get those you do not own which are tied to a castle/city of yours. Not totally sure myself as I never rebelled that way, but I don't see how it could be any different.

Volja 说:

4. i have 46 RtR is it enough?

点击展开...

Depends on how strong your army is. You will be attacked anyway by the kingdom you rebel from, but an higher RtR (I'd say 60+ at least) might help delaying the gangbang from other kingdoms.

Volja 说:

5. is there a good way to position archers in a defending siege? (i can seperately group diffrent kinds of and put em in a good position where they can shoot but they like to stay behind each other)

点击展开...

No, I'd say not really. Sieges are messy stuff, and the game control mechanics are rather dumb. Obviously, the higher the battle size the messier it gets: truth be told, past 200/250 battle size you end up trading off game perfomance for worse gameplay in most sieges. I myself prefer increasing the number of reinforcement waves rather than increasing the battle size for longer, more epic but still manageable sieges.

So, I'm just back from a quest to gain 290 renown for the Eventide, thus I had lots of battles with an army of lancers in a row, which gave me the chance to sit down and look at how they behave. And, to tell the truth, I didn't really notice such a great improvement with the lancer fix (I used the one without bodyguards: regardless of balance matters, I find it supremely annoying to be swarmed by my companions every time I enter somewhere ). A couple of knights do switch to their backup weapons in close quarters, but most still go around poking with lances, often even when on foot after they've been dehorsed. All in all I guess they do fare a bit better, but to be honest I expected a little more difference. Oh well, still better than nothing I guess 

The Radiant Cross tweak works flawlessly btw, they do spawn patrols and offer quests as intended.

MadVader 说:

2. CKHO upgrade times halved
This makes all the other Orders obsolete. Quite a change for the worse in terms of Order use and balance.

点击展开...

Hmm, if I can butt in, while I agree it's indeed sort of cheaty by its very nature, I do believe the wait time for equipping the CKHO is a bit too high. I don't mind having to wait a lot to equip them with the very best items, but even outfitting them with a first mediocre setup tends to take eons (and as such it's an even less viable option if you want to actually play with the CHKO in your lifetime, as you are kinda forced to immediatly go for the best choices to save as much time as possible). Once the Custom Knights have equipment on the same tier of the other orders (and have been trained enough, which takes time too) these do become obsolete, true, but in the LONG meantime you have no other sensible choice but to keep the custom knights parked in their city/castle just looking silly.
But this also comes from the perspective of someone who already played through several PoP campaigns in the past few years, so I indeed have less patience than what should be "normal" when it comes to play and experiment with the shiny stuff a new version introduces.

Personally, I halved the upgrading time while doubling the cost, so it should feel a little less of an exploit. I'd lower the upgrading time for mid to low tier items only if could.